skills-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SKILLS_MCP_UI_PORT | No | Override the management UI port; use 0 for an ephemeral port. | |
| SKILLS_MCP_DATA_DIR | No | Override the data directory where configuration is persisted. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsA | List all available skills and their canonical IDs. |
| read_skillA | Read the complete SKILL.md content for a skill ID. |
| list_skill_resourcesA | List resource files such as references, scripts, and assets for a skill. |
| read_skill_resourceC | Read one resource file belonging to a skill. |
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 4 tools
Each tool targets a distinct action and resource type: listing vs reading, and skills vs resources. No overlap or ambiguity between the four tools.
All tool names follow a consistent verb_noun pattern (list_skills, read_skill, list_skill_resources, read_skill_resource), with clear and predictable conventions.
Four tools perfectly cover the read-only skills management scope without redundancy or excessive granularity, making the set well-scoped.
The tool surface fully covers the apparent domain: listing and reading skills and their resources. For a read-only server, there are no gaps or missing operations.