SKILLEMALL.ai
GitHub ↗ RU Sign in

AC utility-mermaid-diagrams

Teaches PMs to create syntactically valid mermaid diagrams by selecting the right diagram type for their communication need, following syntax validity rules, and validating before shipping. Covers all 15 mermaid diagram types with PM-relevant examples and a dual-lens navigation system.

product-on-purpose/pm-skills Agent Skills author: product-on-purpose Apache-2.0 8 files body ≈ 1 494 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Teaches PMs to create syntactically valid mermaid diagrams by selecting the right diagram type for their communication need, following syntax validity rules…

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, running it twice

GeneratorSoftware developmentOperations and projectstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 57/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (node) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 100Steps. 36 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1494 tokens

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +4No input/output examples
    • +2Single-language instructions
    • +3Description length 286: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 36 items
    • +3Output format is stated explicitly
    • +4Reference files are cited in the instructions (5 of 5)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.