create-documentation

Generate markdown documentation for a module or feature

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/create-documentation/SKILL.md

Quality

Content

61%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 well-structured and highly actionable with a complete MDX template and placement guidance, but it is missing explicit verification checkpoints and inlines content that could live in separate bundle files.

Suggestions

Add explicit validation steps to the workflow, e.g. 'Verify the new MDX page renders in the dev server' and 'Confirm the page appears in meta.json navigation'.

Consolidate the 'Your Task' and 'Process' lists into a single sequenced workflow to remove redundancy and tighten token usage.

Consider moving the MDX file-format template and Fumadocs component reference into a bundled file under references/ and linking from the body, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with good structure, but the full directory tree plus a location table plus two overlapping step lists ('Your Task' and 'Process') and the introductory Fumadocs framing could be tightened, matching the 'mostly efficient with some unnecessary explanation' anchor.	3 / 5
Actionability	It provides a complete, copy-paste-ready MDX template, a meta.json example, a placement table, and Fumadocs component syntax — concrete and executable with only minor gaps (real guidelines deferred to an external file).	4 / 5
Workflow Clarity	Two clear sequenced step lists exist, but there are no explicit validation checkpoints (e.g. verify the MDX renders, confirm navigation updated, build passes), so checkpoints are missing/implicit per the anchor.	3 / 5
Progressive Disclosure	Content is well organized into labeled sections with a clearly signaled one-level reference to WRITING_STYLE.md; most material is appropriately placed, though the bulk MDX/tree content is inlined rather than split into bundle files and no references/ directory exists.	4 / 5
	Total	14 / 20 Passed

Description

45%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 states a clear single-purpose action but lacks a 'Use when...' trigger clause and the concrete action variety that would make it comprehensive and distinctive.

Suggestions

Add an explicit trigger clause, e.g. 'Use when documenting a new module or feature, or updating existing MDX docs in content/docs/'.

List multiple concrete actions (create, update, structure navigation, add cross-references) rather than a single generic 'Generate'.

Include natural synonyms and file extensions users actually say, such as 'docs', 'MDX', and '.mdx'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('markdown documentation') with a single generic action ('Generate'); it does not list the multiple concrete actions (e.g. write, update, structure, cross-reference) the skill actually performs, so it sits below the 1-2-concrete-actions anchor of 3.	2 / 5
Completeness	It gives a clear 'what' ('Generate markdown documentation for a module or feature') but no 'when'/'Use when...' trigger clause; per the rubric guideline, a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	'markdown documentation', 'module', and 'feature' are relevant keywords, but common synonyms users say ('docs', 'MDX', '.md', 'write docs') are missing, matching the anchor with relevant but incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	'markdown documentation for a module or feature' is somewhat specific but broad enough to overlap with other documentation/writing skills, matching the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	11 / 20 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
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: LibPDF-js/core
Path: .opencode/skills/create-documentation/SKILL.md
Commit: 0fa22e0

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.