BF ai-challenge-topic-analysis-assistant
AI 比赛/黑客松/hackathon 题目实战助手——把限时（30–90 分钟）AI 挑战赛题目转成一份可评分的作战包：题目解析、分步执行工作流、可运行单文件 HTML 原型、UX 走查、评委模拟打分、路演稿。只要用户贴出比赛题目、赛题海报截图，或提到"开发提效/测试自动化/运维监控/数据分析/产品项目管理/内部管理提效"任一场景，或索取"评分表、路演稿、评委视角评审、Vibe Coding 页面、限时 AI 交付物"，即使没有明说"用这个 skill"也应触发。不适用于与竞赛/限时交付物无关的普通编码请求或纯理论问答。
AI 比赛/黑客松/hackathon 题目实战助手——把限时（30–90 分钟）AI 挑战赛题目转成一份可评分的作战包：题目解析、分步执行工作流、可运行单文件 HTML 原型、UX…
As a process F 35/100 · Will not run — References files that are not bundled: references/scoring-rubric.md, references/scenarios.md, references/pitfalls.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: 0. 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") - warning
missing-refreference to a missing file: references/scoring-rubric.md - warning
missing-refreference to a missing file: references/scenarios.md - warning
missing-refreference to a missing file: references/pitfalls.md - warning
missing-refreference to a missing file: references/page-challenge.md - warning
missing-refreference to a missing file: references/prompts.md
Process rating: all ten parameters 35/100
- 0Tools and files. 5 referenced file(s) missing: references/scoring-rubric.md, references/scenarios.md, references/pitfalls.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
- 100Steps. 59 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1655 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)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 264: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 59 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.