SKILLEMALL.ai
GitHub ↗ RU Sign in

BF solo-review

Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report. Use when user says "review code", "quality check", "is it ready to ship", "final review", or after /deploy completes. Do NOT use for planning (use /plan) or building (use /build).

LeoYeAI/openclaw-master-skills Claude Code author: LeoYeAI MIT 2 files body ≈ 5 454 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report.

As a process F 61/100 · Will not run — References files that are not bundled: templates/stacks/{stack}.yaml, templates/principles/dev-principles.md

AnalyzerSoftware developmentInfrastructuretype 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
86/100
safety, quality, tests
Safety 60%
95
Quality 40%
73
Run on models
none yet
Process rating
F
61/100
Will not run
References files that are not bundled: templates/stacks/{stack}.yaml, templates/principles/dev-principles.md
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
50
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.

Broad scope 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 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.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  2. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Grep Bash Glob Write Edit mcp__solograph__session_search mcp__solograph__project_code_search mcp__solograph__codegraph_query mcp__solograph__codegraph_explain mcp__solograph__web_s

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5454 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: templates/stacks/{stack}.yaml
  • warning missing-ref reference to a missing file: templates/principles/dev-principles.md

Process rating: all ten parameters 61/100

Will not run. References files that are not bundled: templates/stacks/{stack}.yaml, templates/principles/dev-principles.md
  • 0Tools and files. 2 referenced file(s) missing: templates/stacks/{stack}.yaml, templates/principles/dev-principles.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 50When it triggers. No condition that starts the skill
  • 70Execution cost. Instruction body is 5454 tokens
  • 85Steps. 162 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 12 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 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

  • -5TODO / placeholder text left in the skill
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +4Description says when NOT to use the skill
  • +3Description length 329: enough signal without eating the budget
  • +4Structure: 35 headings
  • +3Step-by-step instructions: 162 items
  • +3Output format is stated explicitly
  • +4Has examples (21 code blocks)
  • +1License stated

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