BF bigfish
🎣 BigFish · AI钓鱼助手 — 钓点分析·鱼情分析·钓点分享。拍水面分析鱼情，结合天气气压推荐鱼种·钓法·饵料，支持路亚、台钓、野钓、海钓，自动记录渔获和出钓报告。钓鱼攻略、钓点推荐、出钓报告一站式，助你告别打龟。| Fishing assistant — spot analysis, fish activity, weather & bait recommendations.
🎣 BigFish · AI钓鱼助手 — 钓点分析·鱼情分析·钓点分享。拍水面分析鱼情，结合天气气压推荐鱼种·钓法·饵料，支持路亚、台钓、野钓、海钓，自动记录渔获和出钓报告。钓鱼攻略、钓点推荐、出钓报告一站式，助你告别打龟。| Fishing assistant — spot analysis, fish…
As a process F 35/100 · Will not run — References files that are not bundled: /skills/weather, /skills/bigseed
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: 6. 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: /skills/weather - warning
missing-refreference to a missing file: /skills/bigseed
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: /skills/weather, /skills/bigseed
- 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. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 409 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
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 196: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.