framework-docs-researcher

Gathers comprehensive documentation and best practices for frameworks, libraries, or dependencies. Use when you need official docs, version-specific constraints, or implementation patterns.

Quality

66%

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 ./.agents/skills/framework-docs-researcher/SKILL.md

Quality

Content

50%

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

The body is a well-structured research playbook with a clear numbered workflow and a mandatory deprecation checkpoint, but it is verbose, more descriptive than instructive, and lacks executable examples or external reference files.

Suggestions

Add a concrete worked example (e.g. a sample Context7 fetch + `bundle show` walkthrough with real command output) so the guidance is copy-paste actionable rather than descriptive.

Collapse the overlapping bullets across Core Responsibilities, Workflow Process, and Quality Standards into a single concise checklist to cut tokens.

Add an explicit verification step to the workflow, e.g. confirm the documented API matches the installed version and cross-check deprecation findings against official docs before reporting.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but it is verbose: "Core Responsibilities", "Workflow Process", and "Quality Standards" restate the same guidance in descriptive bullets ("Provide practical, actionable insights rather than generic information") that could be tightened.	2 / 3
Actionability	It includes some concrete guidance (Context7, `bundle show <gem_name>`, the search string template `"[API/service name] deprecated [current year] sunset shutdown"`), but most of the body describes rather than instructs and offers no executable, copy-paste-ready examples.	2 / 3
Workflow Clarity	The numbered 5-step Workflow Process is clearly sequenced and includes one explicit checkpoint ("Report findings before proceeding"), but there are no validation/feedback loops (validate → fix → retry) for error recovery.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is over 50 lines with no bundle files and no external references; content such as the detailed Output Format lives inline rather than being split into one-level-deep referenced files.	2 / 3
	Total	8 / 12 Passed

Description

82%

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 solid description with an explicit Use-when trigger and natural trigger terms, but it leans on abstract phrasing ("comprehensive documentation and best practices") rather than concrete capabilities, which limits specificity and distinctiveness.

Suggestions

Replace abstract verbs with concrete actions, e.g. "Fetches official docs via Context7, locates installed gem source with `bundle show`, and flags deprecated APIs and version-specific constraints."

Tighten the niche in the description so it cannot trigger for general coding-research needs, e.g. emphasize framework/library version-specific research as the distinguishing purpose.

Dimension	Reasoning	Score
Specificity	"Gathers comprehensive documentation and best practices for frameworks, libraries, or dependencies" names the domain and a couple of actions, but stops at high-level abstractions rather than listing multiple concrete distinct actions like extraction/filling/merging.	2 / 3
Completeness	It answers what ("Gathers comprehensive documentation and best practices...") and explicitly when ("Use when you need official docs, version-specific constraints, or implementation patterns."), satisfying the explicit trigger clause.	3 / 3
Trigger Term Quality	"frameworks, libraries, or dependencies" and "official docs" are natural terms users say when needing research, giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The framework/library documentation niche is reasonably distinct, but "comprehensive documentation and best practices" is broad enough to overlap with general coding-research skills, so it is not a tight unambiguous niche.	2 / 3
	Total	10 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/framework-docs-researcher/SKILL.md
Commit: 45116fd

Reviewed: about 14 hours 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.