skill-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILLS_DIR | No | Same as MCP_SKILLS_PATH for local use. Read only when MCP_SKILLS_PATH is unset. | |
| MCP_SKILL_RUN | No | Optional JSON array of {skill, script, env?} - the owner's grant. Narrow-only. | |
| MCP_SKILLS_PATH | No | Colon-separated slot roots, injected by mcp-host's runner. Wins over everything. |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| skill_listA | List every Agent Skill this server found: name, description, when to use it, how many files it bundles, and the exact scripts (if any) that may be executed with skill_run. Also reports anything that could not be read, so an empty list is never a mystery. |
| skill_loadA | Load one skill's SKILL.md instructions verbatim, plus a manifest of the files it bundles. Referenced files are NOT inlined — read them by name with skill_file. |
| skill_fileA | Read files a skill bundles. Paths are relative to that skill's own directory; text comes back as text, anything else as base64 with its media type. Ask for every file you need in ONE call — a SKILL.md usually points at several. |
| skill_runA | Execute a script the skill DECLARES as runnable, with an argument array. Returns the exit code and the captured output; a non-zero exit is a normal, reported outcome. Asks the user to confirm first: a confirmation prompt where the client supports one (unless MCP_CONFIRM_ELICITATION=off); otherwise the first call returns a preview of exactly what would run and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| skill-mcp-demo | The example skill shipped with skill-mcp — shows the SKILL.md shape, a bundled reference file, and a declared runnable script. When checking that skill-mcp is wired up, or when writing a skill's own mcp-host declaration block. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| skill://skill-mcp-demo/references/declaration.md | |
| skill://skill-mcp-demo/scripts/report.js | |
| skill://skill-mcp-demo/SKILL.md |
TDQS
Scored across 4 tools
Each tool targets a distinct stage of the skill lifecycle: listing skills, loading a SKILL.md, reading bundled files, and executing declared scripts. There is no overlap—file reading and script execution are clearly separated, and descriptions reinforce the boundaries.
All four tools use a uniform skill_<verb> pattern (skill_list, skill_load, skill_file, skill_run). The convention is predictable and readable throughout.
Four tools is well-scoped for a skill-discovery and execution server. Each tool earns its place with no redundant or filler operations.
The surface covers the full lifecycle: enumerate skills, load instructions, read bundled files, and run declared scripts, with clear guidance on chaining (e.g. read files after load). No obvious gaps or dead ends for the stated purpose.