BC activity-planner
✓ Security Audited · 一站式AI活动策划助手 · Your AI Event Planner 输入活动类型 + 预算 + 目标人群，3 分钟输出完整可落地方案。 方案包含：活动定位 | 创意主题 | Slogan | 流程时间线 | 预算分配表 | 传播节奏 | 人力分工 | 物料文案 | 话术脚本 | 风险预案 | 推广监控 | 效果评估 输出结构化 HTML 报告，可直接使用、打印或分享。 适用场景：新品发布 · 年会 · 快闪店 · 促销活动 · 社群活动 · 展会参展 触发词：event planning / marketing campaign / 活动策划 / 活动方案 / 帮我策划活动 / 年会方案 / 发布会策划
✓ Security Audited · 一站式AI活动策划助手 · Your AI Event Planner 输入活动类型 + 预算 + 目标人群，3 分钟输出完整可落地方案。 方案包含：活动定位 | 创意主题 | Slogan | 流程时间线 | 预算分配表 | 传播节奏 | 人力分工 | 物料文案 |…
As a process C 53/100 · Has gaps — 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: 9. 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") - note
frontmatter-keyunknown frontmatter key "agent_created"
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. 77 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 860 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 333: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 77 items
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.