agentskills-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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_skillsA | Return the catalog of all registered skills. Use this first when you don't know which skill applies to the user's request. Each entry includes skill_id, name, version, description, and tags — enough to decide whether to call get_skill_body next. |
| search_skillsA | Keyword search across skill_id, name, tags, and description. Returns ranked matches with relevance scores. Use this when the user's request names a specific intent and you want to find skills whose metadata matches — without scanning the whole catalog. |
| get_skill_metadataA | Return lightweight metadata for a single skill (frontmatter only — name, version, description, tags). Cheaper than get_skill_body when you only need the catalog entry for a known skill_id. |
| get_skill_bodyA | Return the full SKILL.md content for a skill (frontmatter + markdown body). Call this when you're ready to follow the skill's instructions. Cached by file mtime — repeated calls are cheap. |
| list_skill_referencesB | List files in a skill's references/ directory. |
| get_skill_referenceB | Read a specific reference file from a skill's references/ directory. |
| list_skill_scriptsB | List files in a skill's scripts/ directory. |
| get_skill_scriptA | Read a specific script file from a skill's scripts/ directory. |
| list_skill_assetsB | List files in a skill's assets/ directory. |
| get_skill_assetB | Read a specific asset file from a skill's assets/ directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Skill Catalog (Markdown) | Human-readable catalog of all skills. One section per skill. |
| Skill Catalog (XML) | Machine-readable catalog of all skills. |
| Tools Usage Instructions | Condensed guidance for the LLM on when to call which tool. |
TDQS
Scored across 10 tools
Most tools are clearly separated by resource (skill body, references, scripts, assets) and by action (list vs get vs search). The only soft overlap is between list_skills, search_skills, and get_skill_metadata, which all return catalog-level metadata, but the descriptions give explicit guidance on when to use each.
Every tool follows a strict verb_noun snake_case pattern (list_/get_/search_ + resource). The per-directory resource names (skill_references, skill_scripts, skill_assets) are parallel and predictable, so an agent can infer unlisted tools.
Ten tools is well within the ideal range and each earns its place: three discovery tools, one body reader, and a symmetric list/get pair for each of the three sub-directories. No redundant or filler tools.
The read/lifecycle surface for consuming a skill is fully covered: discover, inspect metadata, read body, and traverse references, scripts, and assets. Gaps are minor and likely intentional — there is no way to create, update, or delete skills, and no tool to execute a script rather than just read it.