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.

Quality

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

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 CLI commands for fetching API documentation. Its main weakness is some repetitive hedging about deferring to 'chub --help' output (stated twice) and the lack of explicit validation checkpoints between steps (e.g., verifying search results before fetching). The workflow is logical and the commands are concrete and executable.

Suggestions

Remove the duplicated 'follow chub --help if there is a conflict' caveat — state it once at the top rather than repeating in Steps 2 and 3.

Add a brief validation checkpoint after Step 2, e.g., 'If no results match, broaden keywords or try chub list to browse available docs before proceeding.'

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary hedging and repetition. Phrases like 'If there is a conflict, follow the instructions from the output of chub --help since that will be the latest guidance' appear twice, and some explanatory text could be trimmed. The description of annotations and feedback is somewhat verbose.	2 / 3
Actionability	Every step includes concrete, copy-paste-ready bash commands (chub search, chub get, chub annotate, npm install). The examples include realistic arguments (--lang py, --json flags, example IDs like openai/chat). The fallback installation command is also specific and executable.	3 / 3
Workflow Clarity	The four steps are clearly sequenced and logically ordered (install → search → fetch → use/annotate). However, there are no explicit validation checkpoints — e.g., no step to verify the search results returned something useful before proceeding to 'chub get', and no verification that the fetched docs are complete or relevant before writing code.	2 / 3
Progressive Disclosure	For a skill of this size and scope (single-purpose, under 80 lines, no bundle files needed), the content is well-organized into clear sequential sections. There's no need for external reference files, and the structure is easy to scan and navigate.	3 / 3
	Total	10 / 12 Passed

Description

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

Validation

100%

Warnings & errors only

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: 67dcbeb

Reviewed: 21 days ago

Table of Contents

Discovery Implementation Validation

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.