Fetch the full SKILL.md content of one skill, by the slug returned from search_skills. Write the returned markdown to .claude/skills//SKILL.md (or the equivalent for the user's agent) and it is installed — no other step is needed.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | The skill's slug, e.g. 'AgriciDaniel/claude-seo/seo-google'. Comes from search_skills. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It transparently explains the output (full SKILL.md content), the installation side effect (writing to .claude/skills/<name>/SKILL.md), and that no further steps are required. It does not cover error conditions or authentication, but the behavior is straightforward and well-described.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences that are front-loaded with the purpose, then followed by actionable installation guidance. Every phrase earns its place: the source of the slug, the destination for writing, and the note that no other step is needed. No filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema, the description is complete. It explains the input source, the output content, and the exact post-processing step required, making the agent aware of the full workflow. The sibling tools are contextually relevant, and this description fills all functional gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description already provides full coverage (100%) for the slug parameter, including an example and reference to search_skills. The tool description reinforces the same information ('slug returned from search_skills') without adding new semantic detail beyond what the schema already states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Fetch') and resource ('full SKILL.md content of one skill'), and distinguishes it from sibling tools by referencing the slug returned from search_skills. This makes it obvious how get_skill differs from list_bundles, search_skills, etc.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: use the slug from search_skills, and after fetching, write the file to the specified path to install. It implies the workflow (search → get → install) and provides a 'no other step is needed' assurance. However, it does not explicitly mention when not to use this tool or name alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct: get_bundle vs get_skill differ by granularity, list_bundles/list_categories/list_models list different entity types, and search_skills is the discovery tool. Minor overlap exists between list_bundles and list_categories as both support browsing, but descriptions clarify their purposes.
All tool names follow a consistent verb_noun snake_case pattern: get_* for fetches, list_* for enumerations, and search_* for querying. The naming is uniform and predictable.
Six tools is well-scoped for a skills catalog server. Each tool serves a clear purpose in the discovery/installation workflow, and the count is within the ideal range.
The tool surface covers the core workflow: search, browse categories/bundles, and fetch content for installation. A minor gap is the lack of a direct 'list all skills' endpoint, but categories and search compensate adequately.
