context7-auto-research

Automatically fetch latest library/framework documentation for Claude Code via Context7 API. Use when you need up-to-date documentation for libraries and frameworks or asking about React, Next.js, Prisma, or any other popular library.

Quality

51%

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 ./skills/context7-auto-research/SKILL.md

Quality

Content

25%Scale 1-5

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

This skill is essentially a placeholder that points to an external GitHub repository for all substantive content. It provides no concrete instructions on how the Context7 API works, what documentation is fetched, how to configure API keys, or what the actual usage patterns look like. The skill fails to be self-contained or actionable in any meaningful way.

Suggestions

Add concrete, executable examples showing how to use the skill in Claude Code conversations, including sample prompts and expected outputs.

Include actual API key configuration instructions (e.g., environment variable names, where to obtain keys) instead of deferring to the GitHub repo.

Explain what the skill actually does mechanically — how it fetches documentation, what the Context7 API returns, and how results are integrated into the conversation.

Move troubleshooting content and examples into the skill itself or into bundle files rather than pointing to an external repository.

Dimension	Reasoning	Score
Conciseness	The content is relatively short but includes unnecessary sections like 'When to Use' that largely repeat the description, and 'Best Practices' and 'Troubleshooting' sections that contain almost no useful information. Some padding is present but it's not egregiously verbose.	3 / 5
Actionability	The skill provides almost no concrete, executable guidance. The 'Step-by-Step Guide' is essentially 'install it, optionally configure it, use it' with no actual instructions on how the skill works, what API calls are made, what commands or prompts to use, or how to configure anything. Examples are deferred entirely to an external GitHub repo.	1 / 5
Workflow Clarity	There is a rough 3-step sequence (install, configure, use) but the steps are poorly defined with no specifics. 'Use naturally in Claude Code conversations' is not an actionable step. There are no validation checkpoints or any indication of what success looks like.	2 / 5
Progressive Disclosure	The skill defers all meaningful content (examples, troubleshooting, configuration details) to an external GitHub repository rather than providing it inline or in bundle files. There are no bundle files, so the references point entirely outside the skill ecosystem, making the skill itself nearly empty of useful content.	2 / 5
	Total	8 / 20 Passed

Description

78%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.

This is a solid skill description that clearly communicates its purpose and when to use it. Its main strength is the explicit 'Use when' clause with concrete examples of libraries. Its primary weakness is the limited specificity of what actions it performs beyond 'fetch' — it could better describe what the user gets (e.g., code examples, API references, usage guides).

Suggestions

Add more specific actions describing what happens with the fetched documentation, e.g., 'retrieves code examples, API references, and usage guides from latest library documentation'

Include additional natural trigger terms like 'docs', 'API reference', 'how to use', 'latest version', or 'npm package' to capture more user phrasings

Dimension	Reasoning	Score
Specificity	Names the domain (fetching documentation via API) and one concrete action (fetch latest library/framework documentation), but doesn't describe what happens with the documentation once fetched (e.g., search, summarize, provide code examples). The mention of 'Context7 API' adds some specificity but the overall action set is limited.	3 / 5
Completeness	Clearly answers both 'what' (automatically fetch latest library/framework documentation via Context7 API) and 'when' (when you need up-to-date documentation for libraries and frameworks or asking about React, Next.js, Prisma, or any other popular library). The 'Use when' clause is explicit with concrete trigger scenarios.	5 / 5
Trigger Term Quality	Includes good natural keywords like 'documentation', 'libraries', 'frameworks', and specific examples like 'React', 'Next.js', 'Prisma'. However, it could include more variations like 'docs', 'API reference', 'how to use [library]', or mention that it covers 'any npm package' or similar broader trigger terms users might naturally use.	4 / 5
Distinctiveness Conflict Risk	The mention of 'Context7 API' and the specific focus on fetching external library documentation makes it fairly distinct. There's minor overlap risk with general coding assistance skills or other documentation-related skills, but the specific mechanism (Context7) and focus on up-to-date external docs differentiates it well.	4 / 5
	Total	16 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/context7-auto-research/SKILL.md
Commit: 57c135b

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.