BF OPC赛事活动追踪
追踪 OPC/AI/独立开发者相关赛事活动。从信息源抓取 → 提取结构化信息 → 提交到 OPC 公共赛事池。安装时引导用户获取 API Key。触发词:赛事、比赛、hackathon、活动、OPC赛事、AI比赛、独立开发者大赛、收录赛事、加到OPC
追踪 OPC/AI/独立开发者相关赛事活动。从信息源抓取 → 提取结构化信息 → 提交到 OPC 公共赛事池。安装时引导用户获取 API Key。触发词:赛事、比赛、hackathon、活动、OPC赛事、AI比赛、独立开发者大赛、收录赛事、加到OPC
As a process F 28/100 · Will not run — References files that are not bundled: scripts/events_history.json, scripts/user_config.json, scripts/data/赛事记录.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 2. 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") - warning
missing-refreference to a missing file: scripts/events_history.json - warning
missing-refreference to a missing file: scripts/user_config.json - warning
missing-refreference to a missing file: scripts/data/赛事记录.md - warning
missing-refreference to a missing file: scripts/data/ - warning
missing-refreference to a missing file: scripts/last_run_summary.json - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "agent_created" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "xiaping_trigger" - note
frontmatter-keyunknown frontmatter key "xiaping_category" - note
frontmatter-keyunknown frontmatter key "xiaping_tags"
Process rating: all ten parameters 28/100
- 0Tools and files. 5 referenced file(s) missing: scripts/events_history.json, scripts/user_config.json, scripts/data/赛事记录.md
- 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
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (OPC赛事活动追踪) differs from the folder (opc-event-tracker)
- 100Steps. 43 steps
- 100Execution cost. Instruction body is 2197 tokens
- low 11 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
- +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
- -212 emoji in the instructions: noise for the model
- +2Single-language instructions
- +3Description length 125: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 43 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (2 of 4)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.