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
88%
Does it follow best practices?
Impact
Pending
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 skill description with excellent completeness and trigger term coverage. The explicit 'Use PROACTIVELY when' clause with six numbered scenarios provides clear guidance for skill selection. The main weakness is that the core capability could be more specific about what concrete actions the skill performs beyond 'fetch documentation'.
Suggestions
Add more specific concrete actions like 'retrieve API references, fetch code examples, check latest package versions, get migration guides' to improve specificity
| 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, get version-specific docs'. | 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 | Includes excellent natural keywords users would say: 'React', 'Next.js', 'Supabase', 'library APIs', 'best practices', 'debugging', 'dependencies', 'frameworks', 'documentation'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on external library documentation via Context7 API. The specific mention of 'Context7 API' and focus on 'current documentation beyond training data cutoff' creates a distinct trigger profile unlikely to conflict with other 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. 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 when searches return no results or API calls fail.
Suggestions
Add a brief error handling section showing what to do when search returns no results or context fetch fails (e.g., 'If no results: try alternative library names or check spelling')
| 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 commands with concrete examples (next.js search, React hooks context fetch). Commands are copy-paste ready with clear parameter explanations. | 3 / 3 |
Workflow Clarity | The two-step workflow is clearly sequenced (search → context), but lacks validation checkpoints. No guidance on handling errors, invalid library IDs, or empty results. | 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.
- Repository
- am-will/codex-skills
- Commit
7b702a5
- 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.