documentation-lookup

Use up-to-date library and framework docs via Context7 MCP instead of training data. Activates for setup questions, API references, code examples, or when the user names a framework (e.g. React, Next.js, Prisma).

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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

The skill body is highly actionable and clearly sequenced with a sensible fallback rule, and it is well-organized for a self-contained single-purpose skill. The main improvement is trimming the redundant Examples section that repeats the documented workflow.

Suggestions

Collapse the three near-identical Examples into one worked example plus a short table of library/ID pairs, since 'How it works' already covers the step sequence.

Optionally move the per-tool parameter reference into a compact table to tighten the 'How it works' steps.

Dimension	Reasoning	Score
Conciseness	The body is well-organized and avoids explaining concepts Claude already knows, but the three near-identical Examples (Next.js, Prisma, Supabase) re-walk the same 4-step flow already covered in 'How it works', adding padding that could be tightened.	2 / 3
Actionability	Concrete MCP tool names with their exact parameters (libraryName, query, libraryId) and example values like '/vercel/next.js' give copy-paste-ready, fully specified guidance.	3 / 3
Workflow Clarity	A clear 4-step sequence (resolve → select → fetch → use) with an explicit retry/fallback rule (max 3 calls, then state uncertainty) provides the checkpoint behavior the rubric rewards; the operation is read-only so destructive-validation caps do not apply.	3 / 3
Progressive Disclosure	A self-contained single-task skill with no bundle files, organized into clearly labeled sections (Core Concepts, When to use, How it works, Examples, Best Practices) and no nested references — well-structured for discovery.	3 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that covers what, when, and concrete trigger terms in third-person voice. Its only weakness is that it names one primary capability rather than enumerating several distinct actions.

Suggestions

Consider listing a couple of distinct concrete actions (e.g. 'resolve library IDs and fetch current docs') to lift specificity toward the multi-action anchor.

Dimension	Reasoning	Score
Specificity	Names the domain (library/framework docs) and the single concrete action (use up-to-date docs via Context7 MCP), but does not list multiple distinct capabilities — closer to 'names domain and some actions' than the multi-action anchor at 3.	2 / 3
Completeness	Explicitly answers both what ('Use up-to-date library and framework docs via Context7 MCP') and when ('Activates for setup questions, API references, code examples, or when the user names a framework').	3 / 3
Trigger Term Quality	'setup questions, API references, code examples' plus named frameworks (React, Next.js, Prisma) gives good coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The Context7 MCP niche plus specific framework-name triggers make this clearly distinguishable and unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 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: affaan-m/ECC
Commit: 4130457

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.