AC handdraw-flowchart
Create hand-drawn workflow diagrams from natural-language process descriptions by generating strictly validated Mermaid flowchart, sequenceDiagram, or classDiagram code, converting Mermaid to Excalidraw scene files, and exporting PNGs. Use when Codex needs sketch-style process diagrams, Mermaid-to-Excalidraw conversion, validated Mermaid diagram generation, or PNG exports from process descriptions.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:83High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…HiJ+i3JUvcp/35JchYejb2+5MVe…pAa/P2PY…4HD+aHQ==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:431High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…g95+dndv…4vA+Wb2w==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:566High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…HGA+ULqazeIVV+cr29…DSg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:578High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…RN1+Y1N6…2bN/oXwX…TBw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:649High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…XPn/zV+zis1…Vp9+fVqy…iST/VhUQ…Jqw==",
detector
Files scanned: 6. 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 56/100
- 0Result and completion. Does not say what the result is
- 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
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 23 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 646 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (5 tags): a typed call is more reliable
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 401: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.