AC universal-travel-planner
通用商旅出行规划技能 v1.0 · 面向所有商务出差人士。 一站式AI出行规划 + 全平台酒店比价 + HTML报告生成。 集成12306 MCP（火车票实时查询）+ 高德地图（路径规划/POI/天气）+ Web搜索（航班/酒店价格）。 支持**实时HTML报告生成**，所有预订链接真实可一键跳转。 触发条件： (1) 用户提到"出差"、"出行规划"、"旅行计划"、"行程安排" (2) 用户提到"帮我订酒店"、"机票"、"火车票"、"高铁" (3) 用户提到"规划行程"、"预算估算"、"目的地攻略" (4) 用户提到" itinerary"、"trip plan"、"travel"
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
The same skill appears in 1 more place: ClawHub
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
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. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1968 tokens
- 100Running it twice. No mutating operations
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -233 emoji in the instructions: noise for the model
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 294: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (19 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.