SKILLEMALL.ai

BB issue-audit

Audit and triage general issue backlogs with read-only defaults, interactive cleanup decisions, and guidance steering; use this for "audit open issues" instead of aiwg-issue

jmagly/aiwg Agent Skills author: jmagly 2 files · 1 script body ≈ 2 533 tokens Open the sourcegithub.com↗ analyzed 9 h ago

Audit and triage general issue backlogs with read-only defaults, interactive cleanup decisions, and guidance steering; use this for "audit open issues"…

As a process B 70/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

AnalyzerOperations and projectstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
B
70/100
Nearly there
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

The same skill appears in 2 more places: aiwg, aiwg

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: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "namespace"
    • note frontmatter-key unknown frontmatter key "script"
    • note frontmatter-key unknown frontmatter key "requires"
    • note frontmatter-key unknown frontmatter key "ensures"
    • note frontmatter-key unknown frontmatter key "errors"
    • note frontmatter-key unknown frontmatter key "invariants"
    • note frontmatter-key unknown frontmatter key "commandHint"
    • note edit-residue the text marks something as outdated (lines 23, 147): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 70/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. 4 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. No external tools needed
    • 100Steps. 33 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2533 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)
    • -31 of 1 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 173: enough signal without eating the budget
    • +4Structure: 18 headings
    • +3Step-by-step instructions: 33 items
    • +3Output format is stated explicitly
    • +4Has examples (6 code blocks)

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