BD 足球赛事数据 (Football Match Data)
📊 专业足球赛事多维度数据整理工具 — 整合多渠道公开赛事基础数据 31项球队统计维度交叉比对 | 41项数据校验规则自动清洗偏差 历史交锋·攻防数据·球员状态·联赛积分·近10场可视化 500.com+titan007+Odds API 三源交叉校验 | 一键生成标准化数据报告 💰 1元/场 | ⚡ /ampan 一键输出标准化数据文档 五大联赛·世界杯·欧冠·中超·日职 全覆盖
📊 专业足球赛事多维度数据整理工具 — 整合多渠道公开赛事基础数据 31项球队统计维度交叉比对 | 41项数据校验规则自动清洗偏差 历史交锋·攻防数据·球员状态·联赛积分·近10场可视化 500.com+titan007+Odds API 三源交叉校验 | 一键生成标准化数据报告 💰 1元/场 | ⚡…
As a process D 49/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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Obfuscation
obf-base64-blobscripts/create_order.py:18Long base64-looking blob (quoted — discussed, not commanded)PAY_TO = os.environ.get("CLAWTIP_PAYTO", "3c47…zLu")quoted
Files scanned: 79. 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")
Process rating: all ten parameters 49/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
- 40Consistency. Frontmatter name (足球赛事数据 (Football Match Data)) differs from the folder (football-match-data)
- 100Tools and files. No external tools needed
- 100Steps. 13 steps
- 100Execution cost. Instruction body is 845 tokens
- 100Running it twice. No mutating operations
- low 10 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
- -234 emoji in the instructions: noise for the model
- -33 of 6 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 194: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.