spec-loop-setup-doc-rendering

Help set up and troubleshoot rendering for task files and glossary files. Use when the user asks about PlantUML, AsciiDoc, VS Code, Cursor, other VS Code-based IDEs, JetBrains, preview rendering, Java, or Graphviz needed to review rendered task or glossary files.

Quality

77%

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 ./skills/spec-loop-setup-doc-rendering/SKILL.md

Quality

Content

65%

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

A well-structured, actionable diagnostic skill body with concrete commands and a clear path-based workflow; its main gaps are minor redundancy and broken/missing referenced setup files that undermine progressive disclosure.

Suggestions

Add the missing referenced files vscode-setup.md and jetbrains-setup.md to the bundle (or remove the references and inline the essential setup steps), since the body depends on them.

Reference scripts/setup-vscode-server-based.sh from the body where the VS Code server-based path is discussed, so the existing helper script is discoverable.

Tighten redundancy: drop the restated purpose line and consolidate the two separate mentions of the vscode-setup.md / jetbrains-setup.md references into one.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but it restates the description in its first line and references vscode-setup.md / jetbrains-setup.md twice (top and bottom), so it could be tightened further.	2 / 3
Actionability	It gives concrete, copy-paste-ready commands ('command -v dot', 'dot -V', 'command -v java', 'java -version', 'test -f') plus specific probe-file requirements (at least one class diagram, plus sequence/component/Mermaid glossary), which is actionable guidance for an instruction-only skill.	3 / 3
Workflow Clarity	The diagnostic sequence is present (gather evidence, report working/missing/cannot-verify, suggest probes, follow the selected path), but validation checkpoints are implicit rather than explicit and there is no validate-fix-retry feedback loop.	2 / 3
Progressive Disclosure	References are one level deep and clearly signaled with markdown links, but the referenced files vscode-setup.md and jetbrains-setup.md do not exist in the bundle, and the one present bundle file (scripts/setup-vscode-server-based.sh) is never referenced from the body.	2 / 3
	Total	9 / 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 description with an explicit 'Use when' trigger and a dense set of natural keywords; its only weakness is that the action phrasing ('set up and troubleshoot') is somewhat general rather than enumerating multiple concrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('rendering for task files and glossary files') and two concrete actions ('set up and troubleshoot'), but stops at two general verbs rather than listing multiple specific concrete actions like the anchor-3 example.	2 / 3
Completeness	It explicitly answers both 'what' ('Help set up and troubleshoot rendering for task files and glossary files') and 'when' via an explicit 'Use when...' trigger clause, matching the anchor-3 example.	3 / 3
Trigger Term Quality	The 'Use when the user asks about PlantUML, AsciiDoc, VS Code, Cursor, other VS Code-based IDEs, JetBrains, preview rendering, Java, or Graphviz' clause gives broad coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The niche is narrow and distinct (rendering setup for task/glossary files across specific IDEs with named tools like PlantUML and Graphviz), making conflict with generic skills unlikely.	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
relative_links	Relative link issues: 4 missing	Warning

	Total	15 / 16 Passed

Repository: dpolivaev/spec-loop
Path: skills/spec-loop-setup-doc-rendering/SKILL.md
Commit: 741f932

Reviewed: 4 days 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.