SKILLEMALL.ai

AB the-2-minute-launch

Break the paralysis on the thing you keep not starting with a 2-minute launch sequence — a countdown into motion before the resistance can win. Use when asked I keep putting this off, help me finally start, I've been avoiding this for days, or I can't make myself begin. Produces a diagnosis of what flavor of resistance is stopping you, a 2-minute launch move matched to it, a literal countdown into action, and a bare-minimum win definition — designed to convert avoidance into motion in the next 120 seconds, not to make a plan for later.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 1 file body ≈ 788 tokens Open the sourcegithub.com analyzed 2 d ago

Break the paralysis on the thing you keep not starting with a 2-minute launch sequence — a countdown into motion before the resistance can win.

As a process B 72/100 · Nearly there — weak spots: when it triggers, failures and branches

AnalyzerData and analyticstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
B
72/100
Nearly there
Failures and branches w 10
0
When it triggers w 12
20
Result and completion w 14
60
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: the-2-minute-launch (mohitagw15856/pm-claude-skills)

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 72/100

    • 0Failures and branches. Linear process with no failure handling
    • 20When it triggers. No condition that starts the skill
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 28 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 788 tokens
    • 100Running it twice. No mutating operations
    • 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)
    • +1No license
    • +2Single-language instructions
    • +3Description length 541: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 28 items
    • +3Output format is stated explicitly
    • +4Has examples (0 code blocks)

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