context7
Fetch up-to-date library documentation via Context7 API. Use PROACTIVELY when: (1) Working with ANY external library (React, Next.js, Supabase, etc.) (2) User asks about library APIs, patterns, or best practices (3) Implementing features that rely on third-party packages (4) Debugging library-specific issues (5) Need current documentation beyond training data cutoff (6) AND MOST IMPORTANTLY, when you are installing dependencies, libraries, or frameworks you should ALWAYS check the docs to see what the latest versions are. Do not rely on outdated knowledge. Always prefer this over guessing library APIs or using outdated knowledge.
90
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/skillValidation for skill structure
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 skill description with excellent trigger coverage and completeness. It clearly defines when to use the skill with six explicit use cases and includes natural keywords users would say. The main weakness is that the 'what' portion could be more specific about the concrete actions available (e.g., retrieve API docs, fetch code examples, check version info).
Suggestions
Expand the opening sentence to list 2-3 specific concrete actions beyond 'fetch documentation', such as 'retrieve API references, fetch code examples, check latest package versions'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (library documentation via Context7 API) and describes the general action (fetch documentation), but doesn't list multiple specific concrete actions like 'retrieve API references, fetch code examples, check version compatibility'. | 2 / 3 |
Completeness | Clearly answers both what ('Fetch up-to-date library documentation via Context7 API') and when with explicit numbered triggers covering six distinct use cases. The 'Use PROACTIVELY when' clause provides comprehensive guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'library', 'React', 'Next.js', 'Supabase', 'APIs', 'best practices', 'debugging', 'dependencies', 'frameworks', 'docs', 'latest versions'. These are terms users naturally use when needing documentation help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on external library documentation via a named API (Context7). The emphasis on 'current documentation beyond training data cutoff' and checking 'latest versions' distinguishes it from general coding or documentation skills. | 3 / 3 |
Total | 11 / 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 efficiently teaches Claude how to fetch library documentation via Context7. The content is concise, actionable with executable commands, and appropriately structured. The main weakness is the lack of error handling guidance or validation steps for common failure scenarios like missing API keys or failed searches.
Suggestions
Add a brief troubleshooting section or inline notes for common errors (e.g., 'If search returns empty, try alternative library names' or 'If authentication fails, verify CONTEXT7_API_KEY in .env')
Consider adding expected output format or sample response snippet so Claude knows what successful results look like
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information. No unnecessary explanations of what Context7 is or how APIs work—assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides fully executable bash commands with concrete examples for both search and context operations. The quick reference table offers copy-paste ready commands for common use cases. | 3 / 3 |
Workflow Clarity | The two-step workflow is clearly sequenced (search → context), but lacks validation checkpoints. No guidance on what to do if search returns no results, if the API key is missing/invalid, or how to verify the fetched documentation is correct. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (Workflow, Quick Reference, When to Use). No need for external file references given the scope. | 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.