BD Hike Planner
一站式徒步出行规划。根据用户明确指令生成行程计划(含徒步路线/交通/住宿/人文/装备)。支持查询票务/酒店信息,不执行订票/下单/候补/支付。多源交叉验证(12306/两步路/高德/小红书/GPX/KML文件)。行程状态持久化到本地文件,编辑命令自动写入,短信解析需用户确认。
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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
-
low Exfiltration
exfil-secret-in-urlscripts/render-itinerary-map.js:31Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)const url = `https://restapi.amap.com/v3/geocode/geo?address=…)}&output=json&key=${key}${cityQuery}`;placeholder
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "permissions"
Process rating: all ten parameters 43/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
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (Hike Planner) differs from the folder (hike-planner)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 5 steps
- 100Execution cost. Instruction body is 1308 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- -5TODO / placeholder text left in the skill
- -2localhost URLs: will not work for another user
- -241 emoji in the instructions: noise for the model
- -33 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 138: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 5 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.
External checks
ClawHub: error
ClawScan could not complete because the scanner failed before an artifact-backed review could finish.
LLM: (low) · VirusTotal: · 26 Jun 2026