setup-context7-mcp

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

Quality

32%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/mcp/skills/setup-context7-mcp/SKILL.md

Quality

Discovery

22%

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 description is too vague and incomplete to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and natural user-facing keywords. The mention of 'Context7 MCP server' provides some distinctiveness, but the overall description reads more like a title than a functional skill description.

Suggestions

Add a 'Use when...' clause specifying trigger conditions, e.g., 'Use when the user wants to set up Context7 MCP server, configure documentation sources, or connect MCP to technology-specific docs.'

List specific concrete actions the skill covers, e.g., 'Configures Context7 MCP server connections, sets up documentation endpoints, maps technology libraries to documentation sources, and troubleshoots MCP connectivity issues.'

Include natural trigger terms users might say, such as 'Context7 setup', 'MCP configuration', 'connect docs server', 'documentation server', or specific technology names commonly used with Context7.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'guide for setup' and 'load documentation' without listing concrete actions. It doesn't specify what steps are involved or what outcomes are produced.	1 / 3
Completeness	The description weakly addresses 'what' (setup Context7 MCP server) but completely lacks a 'when should Claude use it' clause. There are no explicit triggers or usage conditions specified.	1 / 3
Trigger Term Quality	It includes some relevant keywords like 'Context7', 'MCP server', and 'documentation', but misses natural user phrases like 'install Context7', 'configure MCP', 'docs lookup', or 'technology docs'. 'Context7 MCP server' is fairly specific jargon that a user familiar with the tool might use.	2 / 3
Distinctiveness Conflict Risk	The mention of 'Context7 MCP server' is fairly distinctive and unlikely to conflict with many other skills, but 'load documentation for specific technologies' is generic enough to overlap with other documentation-related skills.	2 / 3
	Total	6 / 12 Passed

Implementation

42%

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

This skill provides a reasonable high-level workflow for setting up Context7 MCP but lacks the concrete, actionable details needed for Claude to execute it reliably. The biggest weakness is the absence of specific commands, configuration examples, or actual MCP setup instructions—it delegates to an external README without providing any fallback content. The workflow structure is decent but would benefit from validation steps.

Suggestions

Add a concrete example of what the MCP server configuration looks like (e.g., the JSON config for `.mcp.json` or `claude_desktop_config.json`) so Claude doesn't depend entirely on fetching the external README.

Include a validation step after setup (e.g., 'Test the connection by calling `resolve-library-id` with a known library') to confirm the MCP server is working.

Provide a concrete example of the final CLAUDE.md output with real library IDs (e.g., `mongodb/docs` or `vercel/next.js`) instead of just the template placeholder `[doc-id]`.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably concise but includes some unnecessary verbosity, such as explaining the three storage options in detail when Claude could infer most of this. The step descriptions could be tightened.	2 / 3
Actionability	The skill is largely vague and procedural rather than concrete. It says 'guide user through setup process' and 'search through context7 MCP' without providing specific commands, code, or examples of what the MCP configuration looks like. There's no executable code or copy-paste ready configuration.	1 / 3
Workflow Clarity	The three steps are clearly sequenced and logically ordered, but there are no validation checkpoints (e.g., verifying the MCP server is actually working after setup, confirming the CLAUDE.md update is correct). The fallback in step 2 (loading README if not set up) is a nice touch but lacks error handling.	2 / 3
Progressive Disclosure	For a skill of this size and simplicity (under 50 lines, single-purpose), the content is well-organized into clear sections with no need for external references. The structure is clean and easy to navigate.	3 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: NeoLabHQ/context-engineering-kit
Commit: dedca19

Reviewed: 1 day 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.