context7
Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. This skill should be used when looking up documentation for any programming library or framework, finding code examples for specific APIs or features, verifying correct usage of library functions, or obtaining current information about library APIs that may have changed since training.
Install with Tessl CLI
npx tessl i github:intellectronica/agent-skills --skill context787
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
Discovery
82%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 solid skill description that clearly explains both what it does and when to use it. It has good trigger term coverage for documentation-related queries. The main weakness is potential overlap with other coding/documentation skills, and the specificity could be improved by listing more concrete actions beyond general documentation retrieval.
Suggestions
Add more distinctive trigger terms that differentiate from general documentation help, such as 'latest docs', 'current API', 'up-to-date reference', or mention specific popular libraries/frameworks as examples
Consider adding file extensions or specific output formats to increase distinctiveness (e.g., 'retrieves markdown documentation', 'fetches API signatures')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (documentation retrieval via Context7 API) and describes actions like 'looking up documentation', 'finding code examples', 'verifying correct usage', but these are somewhat generic documentation-related actions rather than highly specific concrete operations. | 2 / 3 |
Completeness | Clearly answers both what ('Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API') and when ('should be used when looking up documentation for any programming library or framework, finding code examples...'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'documentation', 'libraries', 'frameworks', 'code examples', 'APIs', 'library functions'. These are terms developers naturally use when seeking help with library documentation. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies Context7 API and focuses on documentation retrieval, terms like 'documentation', 'code examples', and 'library functions' could overlap with general coding assistance skills or other documentation tools. The Context7 API mention helps but isn't a user-facing trigger term. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
87%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-crafted skill that provides clear, actionable guidance for querying the Context7 API. The content is concise, executable, and well-organized. The main weakness is the lack of error handling guidance or validation steps in the workflow, which could leave Claude uncertain when API calls fail or return unexpected results.
Suggestions
Add error handling guidance: what to do if search returns empty results, if the library ID is invalid, or if rate limiting occurs
Include a brief validation step after Step 1 (e.g., 'Verify the returned library matches your intent before proceeding')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary information without explaining what APIs, curl, or documentation retrieval are. Every section serves a clear purpose with no padding. | 3 / 3 |
Actionability | Provides fully executable curl commands that are copy-paste ready, with clear parameter documentation and multiple concrete examples covering different libraries and use cases. | 3 / 3 |
Workflow Clarity | The two-step workflow is clearly sequenced, but lacks validation checkpoints. No guidance on handling errors (e.g., what if search returns no results, what if the library ID is wrong, or rate limiting occurs). | 2 / 3 |
Progressive Disclosure | For a skill of this scope (~80 lines), the content is well-organized with clear sections (Overview, Workflow, Examples, Tips). No external references needed; the structure is appropriate for the content volume. | 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.
- 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.