BB move-planner
Use this skill when a user is actively planning, in the middle of, or wrapping up a residential move. Specific triggers: 'start a move,' 'we're moving to [place],' 'closing on [date],' 'moving day is [date],' 'where are we on the move,' 'move status,' 'update address with [account/category],' 'movers quoted [amount],' 'log this moving expense,' 'add a vendor for the move,' 'show me the address change checklist,' 'what's left before move day,' 'job relocation to [place],' 'sell and buy at the same time,' 'downsizing,' or any message that explicitly references a move-in/move-out date, closing date, or moving-vendor decision. Do NOT trigger on casual mentions of moving (e.g., 'I'm moving on from this project,' 'the meeting is moving to Tuesday'), unrelated real estate browsing, or generic packing questions outside a planned move. Covers: move-type templates (sell-and-buy, first-home, rent-to-rent, relocation, downsizing), task and timeline tracking, vendor directory, light move-budget tracking, and a 30+ item address-change checklist, all stored in a local JSON file.
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, running it twice
How to improve
- Shorten the description to 1024 characters.
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1080 chars, limit 1024
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 4 branches
- 70Execution cost. Instruction body is 4069 tokens
- 85Steps. 122 steps, 2 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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)
- +3Description length 1080: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 39 headings
- +3Step-by-step instructions: 122 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.