BC travel-guide-generator
旅游攻略生成器 - 当用户提出旅游规划需求时自动调用，例如"生成XX旅游攻略"、"规划XX行程"、"XX几天怎么玩"、"情侣/周末/自驾游怎么安排"。支持全球任意城市（威海/青岛/大连/大理/厦门/Tokyo/Paris等仅为常见样例，不限于此）与 1-14 天行程（超过14天仍可生成，但会提示行程过长并建议拆分）。自动搜索真实攻略、高德API计算路线距离用时、生成PC/移动端自适应精美HTML，含每日行程、酒店、美食、避坑、预算。支持中/英/日/韩/法/德/西等多语言。不提供实时订票、签证办理、纯商务出差行程。
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Dangerous commands
cmd-shell-rcSKILL.md:298Writes to a shell startup fileecho 'export AMAP_KEY="你的key"' >> ~/.zshrc # 或 ~/.bashrc
Files scanned: 24. 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 58/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
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 162 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2858 tokens
- 100Running it twice. No mutating operations
- low 13 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -33 of 9 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 259: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 162 items
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.