context7-docs
Fetches authoritative, current, version-specific documentation and official code examples via Context7 for a named external library, framework, SDK, CLI, or cloud product. Use when the user needs exact API behavior, setup, configuration, integration, migration, or version-specific guidance rather than general web research or real-world repository patterns.
75
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that clearly articulates what the skill does (fetches official documentation and code examples via Context7), when to use it (for exact API behavior, setup, configuration, migration, version-specific guidance), and when NOT to use it (general web research or repository patterns). The description is specific, uses natural trigger terms, and establishes clear boundaries to minimize conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Fetches authoritative, current, version-specific documentation and official code examples' and specifies the domains: 'library, framework, SDK, CLI, or cloud product'. Also enumerates specific use cases: 'exact API behavior, setup, configuration, integration, migration, or version-specific guidance'. | 3 / 3 |
Completeness | Clearly answers both 'what' (fetches authoritative documentation and code examples via Context7 for named external libraries/frameworks) and 'when' (explicit 'Use when' clause specifying exact API behavior, setup, configuration, integration, migration, or version-specific guidance, and distinguishing from general web research or repository patterns). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'documentation', 'code examples', 'library', 'framework', 'SDK', 'CLI', 'API behavior', 'setup', 'configuration', 'integration', 'migration', 'version-specific'. Also names the tool 'Context7' which is a useful trigger. These cover a wide range of natural user queries. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly carves out a distinct niche: official documentation lookup via Context7 for named external libraries, explicitly contrasting with 'general web research or real-world repository patterns'. This boundary-setting language makes it highly distinguishable from web search skills or code repository analysis skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill that clearly guides Claude through a two-step documentation lookup workflow. Its strengths are concrete CLI examples, explicit constraints (budget, safety, ordering), and good error handling. Minor verbosity in explanatory prose and the query quality table could be tightened slightly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but has some unnecessary padding. The query quality table and some explanatory text (e.g., 'Retrieves up-to-date documentation and code examples for the resolved library') could be trimmed. The good/bad query examples add value but the surrounding prose is slightly verbose. | 2 / 3 |
Actionability | Provides concrete, executable CLI commands with real examples (e.g., `ctx7 library react "..."`, `ctx7 docs /facebook/react "..."`). The workflow is copy-paste ready with specific command syntax, argument formats, and version-specific ID patterns. | 3 / 3 |
Workflow Clarity | Clear two-step sequence with explicit ordering constraint (MUST call library first), a budget cap (max 3 attempts), error handling with fallback strategies (quota errors, ambiguous results), and decision points (ask for clarification rather than guessing). The workflow is well-sequenced with appropriate validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill with no bundle files, the content is well-organized into logical sections (Workflow overview, Budget, Safety, Step 1, Step 2, Error Handling) with clear headers. The content is appropriately sized for a single file and doesn't need external references. | 3 / 3 |
Total | 11 / 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
- shillem/cc-marketplace
- Commit
2384118
- 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.