context7-skill

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./context7-skill/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

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

The content is well-structured, actionable, and concise, with concrete commands and a clear read-only workflow supported by real one-level-deep bundle references. Main improvements are tightening minor padding and making at least one example fully copy-paste runnable.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete tool calls and commands and avoids explaining concepts Claude already knows, but the Overview reiterates the description and the Selection Criteria section is slightly padded, fitting level 4 with minor trim opportunities.	4 / 5
Actionability	Concrete MCP call signatures and ready-to-run CLI commands ("uv run --script .../scripts/context7_cli.py resolve-library-id <name>") plus an executable API-key existence check are provided, but MCP examples use placeholder args rather than a fully copy-paste runnable case, keeping it at level 4.	4 / 5
Workflow Clarity	A clear three-step Workflow (Check Availability -> Resolve -> Query) with guardrails (retry limit, ask-if-ambiguous, web-fetch fallback) is sequenced well; it lacks an explicit validate-then-proceed checkpoint but the skill is read-only so this is a minor gap at level 4.	4 / 5
Progressive Disclosure	The body is an overview that clearly signals one-level-deep references to real bundle files (scripts/context7_cli.py, references/troubleshooting.md) in a Resources section with content appropriately split; it is well above level 3 but not the textbook cleanly-split level-5 example.	4 / 5
	Total	16 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 clearly identifies the skill's purpose and names the Context7 service for distinctiveness, with reasonable trigger terms. It could be strengthened by listing more concrete actions and adding an explicit "Use when..." trigger phrase with synonyms.

Suggestions

Replace the purpose-style trigger with an explicit "Use when..." clause naming natural user phrases (e.g., "Use when checking version-specific API details, syntax, or usage examples for a library or framework").

Add concrete actions and synonyms to broaden trigger coverage (e.g., "docs", "API reference", "version-specific", "syntax").

List a couple more specific capabilities beyond the generic "access" and "verify" to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	"Access ... documentation and code examples" and "verify library and framework details" name a couple of concrete actions but the verbs are generic (access, verify) and not comprehensive, matching the level-3 anchor rather than the multi-action level-4 example.	3 / 5
Completeness	It states both what ("Access ... documentation and code examples from Context7") and when ("Use this skill to verify library and framework details"), but the trigger is phrased as purpose rather than an explicit "Use when the user mentions X" clause, so it sits at level 4 rather than 5.	4 / 5
Trigger Term Quality	Natural terms like "documentation", "code examples", "library", and "framework" appear, but common synonyms and variations (docs, API reference, syntax, version) are missing, fitting the level-3 anchor rather than the broader coverage at level 4.	3 / 5
Distinctiveness Conflict Risk	Naming the Context7 service gives it a clear niche with minimal conflict risk, but "verify library and framework details" is broad enough to overlap slightly with general documentation skills, placing it between levels 4 and 5.	4 / 5
	Total	14 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ceshine/ceshine-agent-skills
Path: context7-skill/SKILL.md
Commit: 87b64e9

Reviewed: 5 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.