AD luma-events-query
查 lu.ma / Luma 公开活动,方式与 Luma App 搜索框相同(关键词 Hangzhou/杭州/重庆,不限城市目录)。用户说查活动、Luma、meetup、某城最近有什么活动时使用。用户没指定主题时只搜城市,不要默认加 AI。不要用来查大麦/秀动/猫眼。不要向用户索要 Parse/pmx_ API Key。
查 lu.ma / Luma 公开活动,方式与 Luma App 搜索框相同(关键词 Hangzhou/杭州/重庆,不限城市目录)。用户说查活动、Luma、meetup、某城最近有什么活动时使用。用户没指定主题时只搜城市,不要默认加 AI。不要用来查大麦/秀动/猫眼。不要向用户索要 Parse/pmx API Key。
As a process D 46/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.
- 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: 4. 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 46/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
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 362 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
- +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
- +2Single-language instructions
- +3Description length 161: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.