./skimread
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| runA | Run a shell command and return a short, lossless digest of its output (errors, failures and summaries kept; noise folded). The digest ends with an id; use |
| showB | Show the full output of a previous |
| outlineA | Structural outline of a file: symbols/headings/keys with line ranges, so you can read only the slice you need. Use before reading any file longer than ~300 lines. |
| readC | Read a line range of a file with line numbers ('start' and 'end' are 1-based, inclusive). |
| listC | List recent runs stored by skimread (id, command, exit code, size). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct action: run executes commands, list shows past runs, show retrieves run output, read reads file line ranges, and outline provides file structure. There is no functional overlap; show and read differ by source (run output vs. file), and descriptions make this clear.
All tool names are single, lowercase verbs (show, outline, read, run, list) following a consistent and predictable pattern throughout the set. There is no mixing of conventions like camelCase or noun-based names.
Five tools is well-scoped for a skimreading utility: run, list, show, read, and outline cover the essential workflow without redundancy or bloat. Each tool earns its place and the set is easy to navigate.
The surface covers executing commands, browsing runs, retrieving outputs, and inspecting files structurally or by line range, forming a nearly complete lifecycle for the stated purpose. A minor gap is the lack of direct in-file content search (e.g., grep), though this can be worked around by running a shell command via run.