BF play-any-game
AI游戏伴侣助手 - 当你在游戏中遇到困难、卡关、不知道怎么操作时,AI可以帮你分析游戏画面、解答问题、甚至简单操作界面帮你解决问题。不是全自动代肝,而是你的游戏伙伴,在你需要的时候伸出援手。当用户提到"帮我看下这个怎么过"、"这个怎么操作"、"卡关了"、"不知道怎么弄"时使用此技能。支持原神、崩坏星穹铁道等各类游戏。
As a process F 35/100 · Will not run — References files that are not bundled: games/genshin-impact/SOUL.md, games/honkai-starrail/SOUL.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-agent-memory-dumpgames/default/SOUL.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensgames/default/SOUL.md
Files scanned: 22. 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: games/genshin-impact/SOUL.md - warning
missing-refreference to a missing file: games/honkai-starrail/SOUL.md
Process rating: all ten parameters 35/100
- 0Tools and files. 2 referenced file(s) missing: games/genshin-impact/SOUL.md, games/honkai-starrail/SOUL.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. 44 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2123 tokens
- 100Running it twice. No mutating operations
- low 14 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
- +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
- -42 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 160: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (18 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.