setup-context7-mcp

Guide for setup Context7 MCP server to load documentation for specific technologies.

Quality

57%

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 ./plugins/mcp/skills/setup-context7-mcp/SKILL.md

Quality

Content

61%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 and concise with a clear three-step workflow, but execution detail is thin in step 2 and post-write validation is absent, capping actionability and workflow_clarity at 3. Progressive disclosure is good given the skill's small size and single external reference.

Suggestions

Make step 2 actionable: specify the exact request/command to test Context7 MCP availability instead of 'by making request'.

Add an explicit verification checkpoint after step 3 (e.g., confirm the MCP server returns documentation for a sample library ID before finishing).

Replace the generic [doc-id] placeholder guidance with a concrete example of how to discover and format a Context7 library ID.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no padding about what MCP or Context7 is), with only minor tightening possible in step 3's long sentence, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Concrete paths and a CLAUDE.md template are provided, but step 2 ('making request') is vague with no executable check, the template uses a placeholder [doc-id], and actual installation is deferred to an external README, leaving guidance incomplete.	3 / 5
Workflow Clarity	Three numbered steps give a clear sequence and step 2 acts as an 'already setup?' checkpoint, but there is no validation after the CLAUDE.md write (e.g., verifying the MCP server responds), so checkpoints are missing/implicit.	3 / 5
Progressive Disclosure	Under 50 lines with well-organized numbered sections and a clearly signaled one-level external reference (the Context7 README URL); it stops short of 5 because the actual setup detail is offloaded to an external URL rather than a bundled reference file.	4 / 5
	Total	14 / 20 Passed

Description

53%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 target tool and primary actions but lacks an explicit 'when to use' trigger clause and has limited keyword variation, capping several dimensions at 3. It is distinctive thanks to the named Context7 MCP technology.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when setting up Context7 MCP to fetch up-to-date library/framework docs in a project') to lift completeness above 3.

Expand trigger terms with natural synonyms users say, such as 'MCP server', 'library docs', 'framework documentation', and 'Context7'.

List a couple more concrete actions (e.g., 'configure CLAUDE.md, fetch and pin recommended library IDs') to raise specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	The phrase 'Guide for setup Context7 MCP server to load documentation' names the domain and two concrete actions (setup, load documentation), but coverage is not comprehensive; it is above the minimal/generic anchor (2) and below the 'several specific actions' anchor (4).	3 / 5
Completeness	It states a clear 'what' (setup Context7 MCP server to load documentation) but provides no 'when'/Use-when guidance; per the rubric a missing 'Use when...' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Keywords like 'Context7 MCP server', 'setup', and 'load documentation' are relevant and users familiar with the tool would say them, but common variations/synonyms are missing and no natural trigger clause is present, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific 'Context7 MCP server' gives it a clear niche with only minor overlap risk against generic documentation skills, fitting 'mostly distinct; minor overlap risk' rather than the fully distinct anchor (5).	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: NeoLabHQ/context-engineering-kit
Path: plugins/mcp/skills/setup-context7-mcp/SKILL.md
Commit: 8539779

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