AB local-poi-planner
Plan nearby places for dining, desserts, cafes, malls, and date spots using one local POI planning workflow. Best for queries like “附近有什么适合坐着聊天的咖啡店”, “帮我找地铁可达的甜品店”, or “规划一个适合约会的商场/餐厅”. Uses a single orchestrated flow: structured POI recall (Amap-first with OSM fallback) → anchor expansion → unified-search evidence → scoring → fallback to area-level recommendations when store-level data is weak.
Plan nearby places for dining, desserts, cafes, malls, and date spots using one local POI planning workflow.
As a process B 74/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
exfil-webhook-urlscripts/telegram_entities_demo.py:23Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)url = f"https://api.telegram.org/bot{BOT_TOKEN}/sendMessage"placeholder
Files scanned: 17. 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 14, column 24: - unified-search/: Unified search skill (must be installed as sibling skill… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "files" - note
edit-residuethe text marks something as outdated (lines 97, 98, 100, 101, 104, 109): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 74/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 64 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2065 tokens
- 100Running it twice. No mutating operations
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)
- -37 of 9 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 398: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 64 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (2 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.