BC trip-plan
Plan a trip end to end (itinerary by day, a packing list to tick off, a budget, and the calendar checked for conflicts) as pages in the workspace. Use when the user is going somewhere for more than a day and wants a plan, an itinerary or a packing list.
The skill promises an end-to-end trip plan: daily itinerary, packing checklist, budget breakdown, and calendar conflict detection across workspace pages. Grade B, quality score 79, safety 100. No critical issues found, but process score sits at 62—the logic for handling data needs watching. Single file, no scripts, modest footprint at 797 tokens.
For trips longer than a day, this will work if you accept basic functionality without frills. Worth installing: safety checks pass, no serious findings. Keep in mind the lower process score though—complex scenarios or heavy automation might stumble.
Plan a trip end to end (itinerary by day, a packing list to tick off, a budget, and the calendar checked for conflicts) as pages in the workspace.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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
- note
frontmatter-keyunknown frontmatter key "channel"
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 797 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 253: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 17 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.