get_skillReturn the full SKILL.md content for a skill by slug. Free skills return content; premium skills return a purchase URL unless a valid access code is supplied.
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Optional access code to unlock a premium skill. | |
| slug | Yes | Skill slug, e.g. "cold-email". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses key behaviors: free vs. premium content handling and the role of the access code. However, it omits error cases (e.g., invalid slug) and any authentication or rate limits.
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?
Two concise sentences with no extraneous detail. The first sentence states the primary action, the second adds critical nuance, making it front-loaded and efficient.
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?
Given the tool's simplicity (2 params, no output schema), the description covers the essential behavior. It is missing some details like error handling, but is reasonably complete for its complexity.
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?
Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining the dual behavior for premium skills, which clarifies the purpose of the 'code' parameter.
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 specifies a clear verb ('Return') and resource ('full SKILL.md content'), and distinguishes behavior for free vs. premium skills, differentiating it from sibling tools like list_skills.
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 implies when to use (to get full content for a specific skill) but does not explicitly mention alternatives or when not to use it. Sibling names are provided but no direct comparison is made.
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.
Each tool serves a distinct purpose: retrieving sets, skills, categories, sets list, skill list, recommendation, and search. No overlapping functionality.
All tools use consistent snake_case with verb_noun pattern (e.g., get_set, list_categories, search_skills). No mixing of styles.
Seven tools is well-scoped for a skills directory, covering browsing, search, recommendation, and detailed retrieval without overburdening the agent.
Covers core operations: listing categories, skills, sets; searching; recommending; retrieving details. Minor gap: no direct category detail tool, but list_categories provides counts.