SKILLEMALL.ai

BA gstack-openclaw-office-hours

Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.

garrytan/gstack Agent Skills author: garrytan MIT 1 file body ≈ 4 177 tokens Open the sourcegithub.com↗ analyzed 6 d ago

Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any…

As a process A 82/100 · Runs to the end — weak spots: when it triggers

AnalyzerSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
83
Run on models
none yet
Process rating
A
82/100
Runs to the end
When it triggers w 12
20
Failures and branches w 10
65
Inputs and preconditions w 11
70
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: 1. 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 82/100

    • 20When it triggers. No condition that starts the skill
    • 65Failures and branches. 3 branches
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4177 tokens
    • 100Tools and files. No external tools needed
    • 100Steps. 74 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100Consistency. Name and required fields are in place
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 175: enough signal without eating the budget
    • +4Structure: 28 headings
    • +3Step-by-step instructions: 74 items
    • +3Output format is stated explicitly

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