BC travel-guide-pages
Plan trips end-to-end and turn them into polished static travel-guide webpages deployed to Cloudflare Pages. Use when a user wants help deciding where to go, comparing route/base options, shaping an itinerary around interests and constraints, choosing hotels and activities, building a visual travel guide, adding route maps or booking checklists, or publishing the result as a live Cloudflare Pages microsite.
Plan trips end-to-end and turn them into polished static travel-guide webpages deployed to Cloudflare Pages.
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 2. 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 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 40Consistency. Frontmatter name (travel-guide-pages) differs from the folder (travel-guide-test)
- 50When it triggers. No condition that starts the skill
- 85Steps. 165 steps, 3 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 2358 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 15 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 410: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 165 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.