context7-skill

Access up-to-date, version-specific documentation and code examples from Context7. Use this skill to verify library and framework details.

Quality

58%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./context7-skill/SKILL.md

Quality

Discovery

67%

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 is functional and covers both what the skill does and when to use it, earning good marks on completeness. However, it lacks specificity in the concrete actions it performs and could include more natural trigger terms that users would actually say. The mention of Context7 helps distinguish it somewhat, but the broad terms 'documentation' and 'code examples' create potential overlap with other skills.

Suggestions

Add more specific concrete actions, e.g., 'Fetches API references, retrieves function signatures, looks up configuration options, and finds usage examples from Context7.'

Expand trigger terms with natural user language variations, e.g., 'Use when the user asks about docs, API usage, how to use a library, package documentation, or needs to check the latest API for frameworks like React, Django, etc.'

Dimension	Reasoning	Score
Specificity	Names the domain (documentation lookup via Context7) and some actions ('access documentation and code examples', 'verify library and framework details'), but doesn't list multiple concrete actions like searching, comparing versions, or retrieving API signatures.	2 / 3
Completeness	Clearly answers both 'what' (access up-to-date, version-specific documentation and code examples from Context7) and 'when' ('Use this skill to verify library and framework details'), providing an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'documentation', 'code examples', 'library', 'framework', and 'Context7', but misses common user-facing terms like 'docs', 'API reference', 'how to use [library]', 'latest version', or specific framework names that users would naturally say.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Context7' as a specific tool adds some distinctiveness, but 'documentation' and 'code examples' are broad terms that could overlap with general coding assistance skills or other documentation-fetching skills.	2 / 3
	Total	9 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides a reasonable structure for integrating with Context7, with clear tool descriptions and a logical workflow. However, it falls short on actionability due to the lack of complete, executable examples showing a full resolve-and-query cycle with realistic inputs and outputs. The workflow could benefit from explicit validation checkpoints, and some introductory text is unnecessarily verbose for Claude's context window.

Suggestions

Add a complete, executable end-to-end example showing a real resolve-library-id call followed by a query-docs call, with realistic arguments and expected output.

Trim the overview paragraph — Claude doesn't need to be told why version-specific docs matter; just state the tool's purpose in one line.

Add an explicit validation step after resolving the library ID (e.g., 'Confirm the resolved ID matches the expected library before proceeding to query').

Replace the placeholder example output in Step 3 with a realistic, concrete response showing actual fields and structure Claude should expect.

Dimension	Reasoning	Score
Conciseness	The overview paragraph explains what Context7 does in a way that's somewhat redundant given the skill description. Phrases like 'accurate, version-specific documentation and code examples directly from the source' and 'ensuring your code is based on the correct version' are padding. The tool descriptions and workflow are reasonably tight but could be leaner.	2 / 3
Actionability	The skill provides MCP call signatures and CLI commands, which is concrete, but the examples are incomplete — there are no full executable examples showing a complete resolve-then-query workflow with actual arguments and expected output. The 'Example Output' in Step 3 is a vague placeholder rather than a realistic, copy-paste-ready example.	2 / 3
Workflow Clarity	The three-step workflow (check availability → resolve → query) is clearly sequenced, and there's a retry limit mentioned. However, there are no explicit validation checkpoints or feedback loops — e.g., no step to verify the resolved library ID is correct before querying, and no structured error-handling path beyond 'proceed with best available information.'	2 / 3
Progressive Disclosure	The skill references `scripts/context7_cli.py` and `references/troubleshooting.md`, which is good progressive disclosure structure. However, no bundle files were provided to verify these exist, and the main SKILL.md contains inline content (like selection criteria and handling results) that could arguably be in a reference file. The references are one-level deep and clearly signaled, which is positive.	2 / 3
	Total	8 / 12 Passed

Validation

100%

Warnings & errors only

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: ceshine/ceshine-agent-skills
Commit: fc251b2

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.