AC fliggy-search
Search flights, hotels, tickets, and holidays on Fliggy (飞猪). IMPORTANT: Before ANY search, CHECK login state by running `ls ~/.fliggy-session.json`. If NO login state exists, FIRST run `fliggy login` to login and save state. After login, use `--headless` for background searches. Use when user wants to: (1) Search flights (机票), (2) Search hotels (酒店), (3) Search scenic tickets (门票), (4) Search holidays/tours (度假/跟团游/一日游), (5) Plan travel, (6) Book travel products.
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Search flights, hotels, tickets, and holidays on Fliggy (飞猪). IMPO… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 53/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 819 tokens
- 100Running it twice. No mutating operations
- low 11 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
- +1No license
- +2Single-language instructions
- +3Description length 468: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (17 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.