neva-to-mermaid

Convert Neva programs to valid Mermaid flowchart diagrams. Use when asked to visualize Neva code as Mermaid.

Quality

83%

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

Quality

Content

85%

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

The skill body is concise, actionable, and well-organized with concrete Mermaid syntax and worked examples. Its main gap is workflow clarity: the conversion process lacks explicit validation checkpoints to verify the output diagram is correct.

Suggestions

Add an explicit validation step, e.g. 'Verify the generated Mermaid: every Neva connection has a corresponding edge, every external port is a stadium node, and fan-out/fan-in uses junction nodes - re-check before output.'

Break the monolithic 'Generate a Mermaid flowchart' step into a clearer sub-sequence (parse components, parse connections, apply junction rules) so the conversion order is unambiguous.

Complete the reference example by including the expected Mermaid output that pairs with the given Neva code, so Claude has a full input-to-output template.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-focused, assuming Claude's competence - it jumps straight into conversion rules without explaining what Neva or Mermaid are, so every token earns its place.	3 / 3
Actionability	It provides concrete, executable guidance including exact Mermaid syntax (`flowchart TB`, `([":data"])`, junction nodes `jX(( ))`), with copy-paste-ready patterns and labeled edge rules with explicit examples.	3 / 3
Workflow Clarity	Steps are numbered (1-4) but the sequence is thin: 'Generate a diagram' is a single monolithic step, and the only verification is the final 'ensure output is ready to paste' - there is no validation/feedback loop to catch conversion errors, which caps clarity at 2.	2 / 3
Progressive Disclosure	For a sub-50-line single-purpose skill with no bundle files, the content is well-organized into clear sections (Instructions, Port/Component/Literal/Connection/Fan-out rules, Reference Example), satisfying the simple-skills note that organization alone can score 3.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 is concise, specific, and clearly states both what the skill does and when to use it, with a distinct niche. Trigger-term coverage could be slightly broader with more natural synonyms a user might say.

Suggestions

Broaden trigger terms with natural synonyms users might say, e.g. '...Use when asked to visualize, diagram, or render Neva code as a Mermaid flowchart.'

Dimension	Reasoning	Score
Specificity	The description names concrete actions - 'Convert Neva programs to valid Mermaid flowchart diagrams' - clearly stating the transformation performed, which lists multiple specific concrete actions equivalent to the score-3 anchor.	3 / 3
Completeness	It explicitly answers both what ('Convert Neva programs to valid Mermaid flowchart diagrams') and when ('Use when asked to visualize Neva code as Mermaid'), satisfying the score-3 anchor with an explicit 'Use when' clause.	3 / 3
Trigger Term Quality	It includes relevant terms like 'Neva', 'Mermaid', 'flowchart', and 'visualize', but lacks common natural variations a user might say (e.g., 'diagram', 'flowchart diagram', 'draw', 'render') beyond the single trigger phrasing.	2 / 3
Distinctiveness Conflict Risk	The niche is narrow and clearly distinct - converting Neva source specifically to Mermaid - making it unlikely to trigger for unrelated skills, matching the score-3 'clear niche with distinct triggers' anchor.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: nevalang/neva
Path: .codex/skills/neva-to-mermaid/SKILL.md
Commit: a0a5c5f

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.