skill-mcp
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 | {
"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. Mutating: call it once without confirm to see exactly what would run, then again with confirm: true. |
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 has a clearly distinct role: listing skills, loading a skill's instructions, reading bundled files, and executing declared scripts. No two tools overlap in purpose, and the descriptions reinforce the boundaries.
All tools share the skill_ prefix and use lowercase_snake_case, which is predictable. However, skill_file uses a noun suffix while the others use action verbs, creating a minor pattern deviation.
Four tools is a tight, well-scoped set for a skill management server. Each tool covers a necessary part of the workflow without redundancy or bloat.
The tool surface covers the full skill lifecycle from an agent's perspective: discover skills, load instructions, read referenced files, and execute runnable scripts. No obvious dead ends or missing operations are apparent.