rich-modern

Use when you need a full-spec example with rich frontmatter, dynamic injection and substitutions.

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 ./test/fixtures/skills/rich-modern/SKILL.md

Quality

Content

65%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 commendably lean and uses dynamic injection effectively, but the workflow steps are vague without the exact helper command or any verification, and the reference.md link is broken against the actual bundle.

Suggestions

Spell out the exact helper invocation (e.g., `bash ${CLAUDE_SKILL_DIR}/scripts/helper.sh "$target"`) instead of the abstract "Run the helper script".

Create the missing reference.md referenced in the body, or remove the broken link, so progressive disclosure navigation resolves.

Add a brief verification step (e.g., confirm the tree output is non-empty before producing the report) to raise workflow clarity above 3.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean with no padding or over-explanation of concepts Claude already knows; every line (the dynamic find injection, the reference pointer, the three steps) earns its place, matching the lean-and-efficient anchor.	5 / 5
Actionability	The dynamic `!\`find...\`` block is concrete and executable, but step 1 ("Read the reference material") is abstract and step 2 ("Run the helper script using ${CLAUDE_SKILL_DIR}") omits the exact command, leaving the guidance only partially executable.	3 / 5
Workflow Clarity	A clear three-step sequence is present, but it is a read/report skill with no validation or verification checkpoints, and steps 1 and 3 are vague, placing it at the steps-listed-but-checkpoints-missing anchor.	3 / 5
Progressive Disclosure	The body appropriately points to one-level-deep references (reference.md, scripts/) rather than inlining detail, but the referenced reference.md does not exist in the bundle, so the structure is reasonable yet has a broken navigation link.	3 / 5
	Total	14 / 20 Passed

Description

41%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 provides an explicit trigger clause and a distinct, niche domain, but leans on technical jargon and second-person voice while leaving the actual capability (what the skill does) only weakly implied.

Suggestions

State the concrete action the skill performs (e.g., "Generates a repository structure map") before the trigger clause so "what" is explicit, not implied.

Rewrite in third person and drop "you need" to avoid the second-person voice penalty on specificity.

Add natural user-facing trigger phrases (e.g., "visualize the repo", "generate a map") rather than only jargon like "dynamic injection".

Dimension	Reasoning	Score
Specificity	The description names the domain ("rich frontmatter, dynamic injection and substitutions") but describes features of an example fixture rather than concrete actions the skill performs, and the second-person phrasing "you need" triggers the voice penalty, lowering it from 3 to 2.	2 / 5
Completeness	It has an explicit "Use when..." clause for the "when", but the "what" is only weakly implied (it provides an example) rather than clearly stated, so it sits at the clear-when/weak-what anchor.	3 / 5
Trigger Term Quality	Terms like "full-spec example", "dynamic injection", and "substitutions" are technical jargon a user would rarely say naturally, and the natural phrases users would actually voice are absent, matching the one-or-two-generic-keywords anchor.	2 / 5
Distinctiveness Conflict Risk	The niche phrasing ("rich frontmatter, dynamic injection and substitutions") is fairly distinct and unlikely to trigger for unrelated skills, with only minor overlap risk against other example/demo skills.	4 / 5
	Total	11 / 20 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: saif-shines/doraval
Path: test/fixtures/skills/rich-modern/SKILL.md
Commit: 0fa2092

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.