SKILLEMALL.ai

BC brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers Agent Skills author: obra MIT 8 files · 2 scripts body ≈ 3 780 tokens Open the sourcegithub.com analyzed 31 h ago

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.

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

GeneratorSoftware developmentData and analyticsDesigntype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
98
Quality 40%
76
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 · 2

    ✓ No critical or high findings

    Medium and low: 2
    • low Dangerous commands cmd-background-process scripts/start-server.sh:179
      Starts a background / autostarted process (code comment)
      # Use nohup to survive shell exit; disown to remove from job table
      comment
    • low Dangerous commands cmd-background-process scripts/start-server.sh:182
      Starts a background / autostarted process
      disown "$SERVER_PID" 2>/dev/null

    Files scanned: 8. 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
    • 40Result and completion. Does not say what the result is
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 57 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3780 tokens
    • 100Running it twice. Mutating operations check current state
    • low The response is described with custom markup (4 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
    • -5TODO / placeholder text left in the skill
    • -33 of 3 scripts are never mentioned in SKILL.md
    • +1No license
    • +2Single-language instructions
    • +3Description length 198: enough signal without eating the budget
    • +4Structure: 9 headings
    • +3Step-by-step instructions: 57 items
    • +4Has examples (1 code blocks)

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