code-wiki

Generate wiki docs + Mermaid diagrams for any codebase.

Quality

71%

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 ./optional-skills/software-development/code-wiki/SKILL.md

Quality

Content

88%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 content is a highly actionable, well-sequenced multi-file generation procedure with explicit verification checkpoints and error-prevention pitfalls — its main limitation is conciseness/organization given the inline template bulk, not correctness or executability.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence — concrete templates, Mermaid shape semantics, and heuristics earn their tokens — with only minor repetition in the report block and template sections that could be trimmed.	4 / 5
Actionability	Executable shell commands (git clone --depth 50, find -maxdepth 3, pygount), exact file templates with parameterized placeholders, Mermaid syntax examples, and a heredoc state file give copy-paste-ready guidance covering the common cases.	5 / 5
Workflow Clarity	A 12-step numbered procedure with a Quick Reference table is backed by an explicit Verification checklist (Mermaid balance, expected files, module count, no fabricated paths), Scope Control cost-confirmation, and Re-Run state handling — satisfying the validation requirement for batch generation.	5 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single well-organized file with clear headers (When to Use, Quick Reference, Procedure, Pitfalls, Verification) acting as its own overview; it is well structured but keeps substantial per-file templates inline with minor organization gaps rather than splitting them out.	4 / 5
	Total	18 / 20 Passed

Description

53%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 cleanly states what the skill does but lacks any 'Use when...' trigger guidance, capping its completeness. It is specific enough to be distinct from generic doc skills yet not comprehensive enough in enumerated actions or trigger synonyms to score higher.

Suggestions

Add an explicit 'Use when the user asks to document a codebase, generate a wiki, or create architecture diagrams' trigger clause to raise completeness and trigger-term coverage.

Enumerate the concrete outputs (overview, architecture, per-module deep-dives, class and sequence diagrams) to move specificity from listing two actions to several.

Include natural synonyms users actually say (e.g., 'document this codebase', 'architecture diagrams', 'onboarding docs') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	The phrase 'Generate wiki docs + Mermaid diagrams' names the domain and two concrete actions but does not enumerate the wiki's contents (overview, architecture, per-module docs, class/sequence diagrams), so coverage is not comprehensive.	3 / 5
Completeness	The 'what' is clear (generate wiki docs + Mermaid diagrams for a codebase) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'wiki docs', 'Mermaid diagrams', and 'codebase' are relevant keywords, but the description omits common variations and synonyms users would say ('document this codebase', 'architecture diagrams', 'onboarding').	3 / 5
Distinctiveness Conflict Risk	The codebase-wiki-plus-Mermaid niche is mostly distinct from generic documentation skills, though it carries minor overlap risk with closely related codebase-inspection and documentation skills and lacks explicit distinguishing triggers.	4 / 5
	Total	13 / 20 Passed

Validation

75%

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 — 12 / 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
relative_links	Relative link issues: 13 missing	Warning

	Total	12 / 16 Passed

Repository: NousResearch/hermes-agent
Path: optional-skills/software-development/code-wiki/SKILL.md
Commit: fcbd107

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