context7-skill
Access up-to-date, version-specific documentation and code examples from Context7. Use this skill to verify library and framework details.
Install with Tessl CLI
npx tessl i github:ceshine/ceshine-agent-skills --skill context7-skill69
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
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description adequately conveys the skill's purpose of accessing Context7 documentation but lacks the specificity and explicit trigger guidance needed for reliable skill selection. It would benefit from concrete action verbs, natural user trigger terms, and an explicit 'Use when...' clause to improve Claude's ability to select it appropriately.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks about library documentation, API references, framework usage, or needs to check the latest syntax for a specific version.'
Include natural trigger terms users would say: 'docs', 'API', 'how do I use', 'latest version of', 'syntax for', along with common framework/library names if applicable.
List more specific concrete actions: 'retrieve API documentation', 'fetch code snippets', 'look up function signatures', 'check version-specific syntax'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (documentation/code examples) and source (Context7), mentions 'verify library and framework details' as an action, but lacks concrete specific actions like 'search docs', 'retrieve API references', or 'fetch code snippets'. | 2 / 3 |
Completeness | Describes what it does (access documentation and code examples, verify details) but lacks an explicit 'Use when...' clause. The when is only implied through the action 'verify library and framework details' rather than explicitly stated. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'documentation', 'code examples', 'library', 'framework', but misses common user phrases like 'docs', 'API', 'how to use', 'latest version', or specific framework names that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Context7 as a source provides some distinctiveness, but 'documentation' and 'code examples' are generic enough to potentially conflict with other documentation-related skills. The 'version-specific' qualifier helps but isn't strongly distinctive. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured with actionable guidance and good progressive disclosure. The main weaknesses are minor verbosity in the overview and missing explicit validation/error recovery steps in the workflow. The content effectively balances quick reference (tool calls, CLI commands) with detailed usage guidelines.
Suggestions
Tighten the Overview section by removing explanatory phrases like 'ensuring your code is based on the correct version' - Claude understands the purpose from context
Add explicit validation steps to the workflow, such as 'Verify the returned library ID matches expected format before proceeding' or error handling guidance when tools fail
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation in the overview that restates what the skill does. Phrases like 'ensuring your code is based on the correct version' and the detailed overview paragraph could be tightened. | 2 / 3 |
Actionability | Provides concrete MCP calls and CLI commands with specific syntax. The workflow steps include clear selection criteria and specific actions to take in different scenarios. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (Check Availability → Resolve → Query), but lacks explicit validation checkpoints. The 'Limit Attempts' guideline mentions retry limits but doesn't provide a clear feedback loop for error recovery. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, appropriate use of tables for configuration, and references to external files (troubleshooting.md, scripts) that are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 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.