BF game-development
游戏开发辅助技能,涵盖游戏数据分析、关卡设计、资产整理、项目构建自动化、测试框架、游戏存档解析、 Unity / Unreal / Godot 项目辅助。触发场景:游戏数据分析、关卡配置、资产整理打包、项目构建自动化、游戏测试、存档解析、引擎项目辅助、shader 调试、日志分析。
As a process F 31/100 · Will not run — References files that are not bundled: scripts/level_config.py, scripts/asset_packer.py, scripts/build_godot.py
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.
For the model run — optional
- 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: 5. 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: scripts/level_config.py - warning
missing-refreference to a missing file: scripts/asset_packer.py - warning
missing-refreference to a missing file: scripts/build_godot.py - warning
missing-refreference to a missing file: scripts/game_tester.py - warning
missing-refreference to a missing file: scripts/save_parser.py - warning
missing-refreference to a missing file: scripts/generate_csharp.py - warning
missing-refreference to a missing file: references/unity-build.md - warning
missing-refreference to a missing file: references/godot-api.md - warning
missing-refreference to a missing file: references/game-data-formats.md
Process rating: all ten parameters 31/100
Will not run. References files that are not bundled: scripts/level_config.py, scripts/asset_packer.py, scripts/build_godot.py
- 0Tools and files. 9 referenced file(s) missing: scripts/level_config.py, scripts/asset_packer.py, scripts/build_godot.py
- 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 (game-development) differs from the folder (game-dev-assistant)
- 100Steps. 49 steps
- 100Execution cost. Instruction body is 390 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 141: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 49 items
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.
External checks
ClawHub: clean
This is a broad game-development helper that reads local game files and can run Unity builds, but the reviewed artifacts are disclosed, purpose-aligned, and show no hidden network, persistence, credential, or destructive behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026