BF developer-skills
开发者十二铁律 + 开发规范 + 高级调试方法论 — 开发者核心技能(合并自 diagnose)
开发者十二铁律 + 开发规范 + 高级调试方法论 — 开发者核心技能(合并自 diagnose)
As a process F 40/100 · Will not run — References files that are not bundled: scripts/remote-push.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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 1. 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
body-longSKILL.md body ≈ 9666 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/remote-push.py
Process rating: all ten parameters 40/100
Will not run. References files that are not bundled: scripts/remote-push.py
- 0Tools and files. 1 referenced file(s) missing: scripts/remote-push.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 18 mutating operations with no state check
- 40Execution cost. Instruction body is 9666 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 193 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (7 tags): a typed call is more reliable
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)
- +3Description length 48: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -259 emoji in the instructions: noise for the model
- +2Single-language instructions
- +4Structure: 79 headings
- +3Step-by-step instructions: 193 items
- +4Has examples (49 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 52.
External checks
ClawHub: clean
This is a developer guidance skill with broad coding and debugging advice, but it has no hidden installer, executable payload, or automatic data access.
LLM: benign (high) · VirusTotal: · 17 Jul 2026