SKILLEMALL.ai
GitHub ↗ RU Sign in

BF coding-framework

Orchestrate the complete coding workflow with multiple development modes (TDD/incremental/spec-dr...

ClawHub Agent Skills author: paudyyin v13.0.0 MIT-0 39 files · 3 scripts body ≈ 18 194 tokens Open the sourceclawhub.ai↗ analyzed 34 h ago

Orchestrate the complete coding workflow with multiple development modes (TDD/incremental/spec-dr...

As a process F 29/100 · Will not run — References files that are not bundled: scripts/static_analysis.py, scripts/benchmark_runner.py, scripts/analyze_impact.py

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
75/100
safety, quality, tests
Safety 60%
94
Quality 40%
47
Run on models
none yet
Process rating
F
29/100
Will not run
References files that are not bundled: scripts/static_analysis.py, scripts/benchmark_runner.py, scripts/analyze_impact.py
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Dangerous commands cmd-persistence references/security-patterns-detail.md:27
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)
    5. **计划任务** (high) — schtasks, crontab, New-ScheduledTask
    security skill

A further 1 matches are quotations in this security skill's documentation and are not counted as findings.

Files scanned: 39. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning body-long SKILL.md body ≈ 18194 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: scripts/static_analysis.py
  • warning missing-ref reference to a missing file: scripts/benchmark_runner.py
  • warning missing-ref reference to a missing file: scripts/analyze_impact.py
  • note frontmatter-key unknown frontmatter key "dependencies"

Process rating: all ten parameters 29/100

Will not run. References files that are not bundled: scripts/static_analysis.py, scripts/benchmark_runner.py, scripts/analyze_impact.py
  • 0Tools and files. 3 referenced file(s) missing: scripts/static_analysis.py, scripts/benchmark_runner.py, scripts/analyze_impact.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
  • 10Execution cost. Instruction body is 18194 tokens: crowds the task out of the window
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 5 mutating operations with no state check
  • 100Steps. 252 steps
  • 100Consistency. Name and required fields are in place
  • 100Progress reporting. Reports progress
  • low 31 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (6 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 100: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • -224 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +4Structure: 132 headings
  • +3Step-by-step instructions: 252 items
  • +4Has examples (81 code blocks)
  • +4Reference files are cited in the instructions (11 of 12)
  • +3All 9 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 47.

External checks

ClawHub: suspicious
This coding automation skill has a coherent purpose, but it includes broad command execution and automatic Git/worktree mutation paths that are not safely scoped.
LLM: suspicious (high) · 3 Aug 2026