AC ocas-voyage
Travel planning, itinerary construction, reservation management, lodging search, and flight search. Parallel lodging search across Expedia, Marriott Bonvoy, Marriott AI, Google Hotels, 1Stay, and HotelsByDay (day-use rooms). Flight search via Google Flights. Uses Sift for destination research and optionally GoPlaces for location enrichment. HotelOracle (Google Hotels) used for price trends, area guides, and price comparison research. NOT for generic travel inspiration, visa advice, or points-only optimization.
Travel planning, itinerary construction, reservation management, lodging search, and flight search.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "includes" - note
frontmatter-keyunknown frontmatter key "source" - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 5 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 100Steps. 61 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3990 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 23 top-level sections: this looks like several domains in one skill
- medium 2 test cases, all positive: not one "should refuse" or "should ask first"
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
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 515: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 61 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (16 of 16)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.