CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-diagram

Generate a mermaid-only visual supplement for a plan artifact - the data-model, architecture, and flow diagrams a human wants when absorbing a plan. Use when the user wants to "diagram this plan", "visualize the plan", "draw the plan's architecture", "make diagrams for this plan", or invokes /prp-diagram.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

A tight, highly actionable single-purpose skill: it defines a mechanical output-location rule, a strict output format, and a concrete decision table for diagram selection, with the only gap being the absence of any verification step for the generated mermaid (no syntax/render check or fix-retry loop). Organization is clean and self-contained with no bundle overhead.

Suggestions

Add a lightweight validation checkpoint to the workflow, e.g. after writing the file, re-read each mermaid fence and check node/edge syntax (or render it) and fix-and-retry on failure.

Include one minimal example of the expected output shape (a caption line plus a small mermaid fence) so the 'single title line + caption + fence' policy is unambiguous on first run.

DimensionReasoningScore

Conciseness

The body is lean and every section carries instruction weight: 'One agent, one pass, no subagents... Nothing else', the canonical store-resolver bash, an exact output-path rule, a strict content policy, a plan-content-to-diagram-type table, and a one-line report spec. There is no re-teaching of concepts Claude already knows and no padding.

5 / 5

Actionability

Guidance is fully concrete and executable: the byte-identical bash resolver is copy-paste ready, the output path rule is mechanical ('strip the plan filename's trailing .md, append .diagrams.md'), the content policy specifies the exact output line format, and the table maps plan content to concrete mermaid diagram types with a node budget and label-quoting rule.

5 / 5

Workflow Clarity

Sections appear in execution order (resolve store, output path, content policy, choosing diagrams, HTML alternative, report), and overwrite-on-rerun is explicitly justified as a derived artifact so the destructive/batch validation cap does not apply. However there is no validation checkpoint on the generated output — e.g., no mermaid render/syntax verification loop — which keeps it below the anchor-5 'explicit validation steps' bar.

4 / 5

Progressive Disclosure

The skill is a self-contained ~60-line SKILL.md with no references/, scripts/, or assets/ bundle and no references to files that do not exist; every section is well-organized and appropriately inline, matching the simple-skill case where no external references are needed.

5 / 5

Total

19

/

20

Passed

Description

95%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.

A strong description: third-person, specific about outputs, and rich in natural trigger phrases including the slash-command name. The only weakness is minor coverage incompleteness — state/lifecycle diagrams are produced per the body but not named in the description.

Suggestions

Mention lifecycle/state diagrams in the description so the 'what' fully covers the diagram types the skill can produce.

Trim the framing phrase 'a human wants when absorbing a plan' — it adds tokens without changing triggering behavior.

DimensionReasoningScore

Specificity

'Generate a mermaid-only visual supplement for a plan artifact - the data-model, architecture, and flow diagrams' names the domain and several specific concrete outputs in third person. It falls short of the anchor-5 'comprehensive coverage' only because diagram categories the body supports (lifecycle/state diagrams via stateDiagram-v2) are not mentioned; it is clearly above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

It explicitly answers both questions: 'what' is 'Generate a mermaid-only visual supplement for a plan artifact - the data-model, architecture, and flow diagrams' and 'when' is the explicit 'Use when the user wants to...' clause with concrete quoted trigger phrases.

5 / 5

Trigger Term Quality

'Use when the user wants to "diagram this plan", "visualize the plan", "draw the plan's architecture", "make diagrams for this plan", or invokes /prp-diagram' provides comprehensive natural-phrase coverage with multiple synonyms plus the slash-command trigger, matching the anchor-5 example.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche — mermaid-only diagram supplements for plan artifacts — with distinct triggers ('diagram this plan', '/prp-diagram'), so the risk of firing for a generic visualization or document skill is minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Wirasm/prp
Reviewed

Table of Contents

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.