SKILLEMALL.ai

AC <phase-or-classification-skill-name>

<single-line 20-100 word description; include trigger keywords and do not use folded YAML>

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

<single-line 20-100 word description; include trigger keywords and do not use folded YAML>

As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, consistency

Proceduretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
100
Quality 40%
76
Run on models
none yet
Process rating
C
58/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning frontmatter-yaml SKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 9, column 13: category: <one of: research, problem-framing, ideation, specification, valida… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
    • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
    • note frontmatter-key unknown frontmatter key "phase"
    • note frontmatter-key unknown frontmatter key "updated"

    Process rating: all ten parameters 58/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 1 mutating operations with no state check
    • 40Consistency. Frontmatter name (<phase-or-classification-skill-name>) differs from the folder (skill-template)
    • 50When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 100Tools and files. No external tools needed
    • 100Steps. 15 steps
    • 100Execution cost. Instruction body is 242 tokens
    • low The response is described with custom markup (22 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
    • +3Description length 90: 120–800 characters recommended
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +4Structure: 7 headings
    • +3Step-by-step instructions: 15 items
    • +3Output format is stated explicitly
    • +4Has examples (0 code blocks)
    • +4Reference files are cited in the instructions (2 of 2)
    • +1License stated

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