CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/context7-auto-research/SKILL.md

The canonical home for this skill is context7-auto-research in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

53%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 body is concise and neatly sectioned but provides little executable guidance for the core task, leaning on external GitHub links instead of concrete usage examples. Workflow steps are listed but vague with no verification checkpoints.

Suggestions

Add an executable example showing how to actually fetch documentation via the Context7 API (e.g., a sample command or code snippet), rather than only 'Use naturally in Claude Code conversations'.

Inline one or two concrete examples instead of deferring all of them to the external GitHub repo, so the skill is self-contained for the common case.

Tighten the step-by-step guide into concrete, verifiable steps (e.g., how to confirm the API key is configured and a query succeeds) instead of 'Use naturally'.

DimensionReasoningScore

Conciseness

The body is lean with no padded concept explanations ("Automatically fetch latest library/framework documentation ..."), respecting token budget; not a 5 because low-value lines like "Use naturally in Claude Code conversations" could be trimmed.

4 / 5

Actionability

Only the install command (`npx skills add -g ...`) is executable; the core action is described as "Use naturally in Claude Code conversations" and "See GitHub Repository for examples", giving minimal concrete guidance and missing the specific steps to actually fetch documentation.

2 / 5

Workflow Clarity

A rough sequence is present (install, configure, use), but step 3 "Use naturally in Claude Code conversations" is vague and no validation/feedback checkpoints are specified; matches 'steps listed but validation gaps; checkpoints implicit'.

3 / 5

Progressive Disclosure

Sections are well-organized and the skill is under 50 lines, but examples and troubleshooting are deferred to external GitHub URLs rather than clearly-signaled one-level-deep local references, leaving a minor organization gap.

4 / 5

Total

13

/

20

Passed

Description

78%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 states what the skill does and when to use it, with named library triggers that aid discoverability. It is somewhat thin on the range of concrete actions and has minor overlap with general research skills.

DimensionReasoningScore

Specificity

Quotes "fetch latest library/framework documentation ... via Context7 API" name the domain and a single concrete action, but list no further actions, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor; not a 4 because there is no set of several specific actions.

3 / 5

Completeness

It explicitly answers "what" ("fetch latest library/framework documentation ... via Context7 API") and "when" ("Use when you need up-to-date documentation ... or asking about React, Next.js, Prisma, or any other popular library") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Quotes "documentation", "libraries and frameworks", and "React, Next.js, Prisma" are natural terms users say, giving good keyword coverage; not a 5 because common variations like "docs", "API reference", or version/migration phrasing are absent.

4 / 5

Distinctiveness Conflict Risk

The named "Context7 API" gives a clear niche distinct from general skills, but "library/framework documentation" overlaps with related research skills (tavily-web, exa-search), so minor overlap risk keeps it just below a 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.