get-api-docs
Use this skill to get documentation for third-party APIs, SDKs or libraries before writing code that uses them to ensure you have the latest, most accurate documentation. This is a better way to find documentation than doing web search. This includes when a user asks for tasks like "use the OpenAI API", "call the Stripe API", "use the Anthropic SDK", "query Pinecone", or any other time the user asks you to write code against an external service and you need current API reference. Fetch the docs with chub before answering, rather than relying on your pre-trained knowledge, which may be outdated because of recent changes to these APIs. Be sure to use this skill when the user asks for the latest docs, latest API behavior, or explicitly mentions chub or Context Hub. Ensure `chub` is available, run `chub --help`, then follow the instructions there.
68
81%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent trigger term coverage and clear completeness, explicitly stating both what the skill does and when to use it with concrete examples. The main weakness is that it uses second person voice ('you') and imperative instructions directed at Claude rather than third-person declarative statements, and it's somewhat verbose/repetitive in conveying what is essentially a single action (fetch documentation). The specificity could be improved by listing more distinct capabilities beyond just 'fetch docs.'
Suggestions
Rewrite in third person voice (e.g., 'Fetches documentation for third-party APIs...' instead of 'Use this skill to get documentation...'). The current second-person/imperative style should reduce the specificity score per rubric guidelines.
Reduce verbosity by consolidating the repeated emphasis on fetching docs before answering into a single concise statement, keeping the trigger examples but trimming redundant phrasing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (third-party API/SDK documentation) and the core action (fetching docs with chub before writing code), but it doesn't list multiple distinct concrete actions—it's essentially one action (fetch documentation) described repeatedly in different ways. | 2 / 3 |
Completeness | Clearly answers both 'what' (fetch third-party API/SDK documentation using chub before writing code) and 'when' (when user asks to write code against external services, asks for latest docs, mentions chub or Context Hub). Explicit trigger guidance is provided with multiple examples. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'use the OpenAI API', 'call the Stripe API', 'use the Anthropic SDK', 'query Pinecone', 'latest docs', 'latest API behavior', 'chub', 'Context Hub'. These are realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | The skill has a clear niche—fetching third-party API documentation via the 'chub' tool—and explicitly distinguishes itself from web search. The specific tool name 'chub'/'Context Hub' and the focus on API/SDK docs make it unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill that provides clear step-by-step guidance for using the chub CLI to fetch API documentation. Its main weaknesses are some verbosity from repeated 'follow chub --help if there's a conflict' disclaimers and a lack of explicit validation/error-handling checkpoints between steps. The concrete commands and realistic examples make it immediately usable.
Suggestions
Remove the repeated 'follow chub --help if there is a conflict' disclaimers from Steps 2 and 3 — state this once at the top or in Step 1 to improve conciseness.
Add a brief validation checkpoint after Step 3, e.g., 'Verify the fetched docs contain the relevant API methods before proceeding to write code.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary hedging and repetition, such as repeatedly saying 'follow the instructions from chub --help if there is a conflict' in multiple steps. Some phrasing could be tightened (e.g., the installation paragraph and the feedback section are somewhat verbose). | 2 / 3 |
Actionability | Every step includes concrete, copy-paste-ready bash commands (chub --help, chub search, chub get, chub annotate). The examples include realistic IDs and flags (--lang py, --json), making the guidance fully executable. | 3 / 3 |
Workflow Clarity | The four steps are clearly sequenced and logically ordered. However, there are no explicit validation checkpoints — for example, no guidance on what to do if 'chub search' returns no results beyond 'try broader terms,' and no verification that 'chub get' returned useful content before proceeding to write code. | 2 / 3 |
Progressive Disclosure | For a skill with no bundle files and a relatively simple single-tool workflow, the content is well-organized into clear sequential sections. The skill appropriately delegates detailed usage instructions to 'chub --help' rather than duplicating them, which is a good progressive disclosure pattern. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- andrewyng/context-hub
- Commit
04c149c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.