BF code-reviewer
AI-powered code review assistant for OpenClaw agent developers. Automatically analyzes code quality, detects security vulnerabilities, performance issues, and provides actionable improvement suggestions. Built specifically for AI agent code with a focus on safety, best practices, and maintainability.
As a process F 36/100 · Will not run — References files that are not bundled: CONTRIBUTING.md, LICENSE, docs/README.md
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 · 6
✓ No critical or high findings
Medium and low: 6
-
low Secrets in code
secret-labelled-tokencode-review-report.md:28Labelled token / key literal (vendor format unknown — verify it is not a live credential) (placeholder value)const API_KEY = "sk-1…def";
placeholder -
low Secrets in code
secret-password-literalcode-review-report.md:28Hard-coded password / key literal (may be an example) (placeholder value)const API_KEY = "sk-1…def";
placeholder -
low Secrets in code
secret-labelled-tokencode-review-report.md:50Labelled token / key literal (vendor format unknown — verify it is not a live credential) (placeholder value)const API_KEY = "sk-1…def";
placeholder -
low Secrets in code
secret-password-literalcode-review-report.md:50Hard-coded password / key literal (may be an example) (placeholder value)const API_KEY = "sk-1…def";
placeholder -
low Secrets in code
secret-labelled-tokentest-bad-code.js:4Labelled token / key literal (vendor format unknown — verify it is not a live credential) (placeholder value)const API_KEY = "sk-1…def";
placeholder -
low Secrets in code
secret-password-literaltest-bad-code.js:4Hard-coded password / key literal (may be an example) (placeholder value)const API_KEY = "sk-1…def";
placeholder
Files scanned: 7. 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: CONTRIBUTING.md - warning
missing-refreference to a missing file: LICENSE - warning
missing-refreference to a missing file: docs/README.md
Process rating: all ten parameters 36/100
- 0Tools and files. 3 referenced file(s) missing: CONTRIBUTING.md, LICENSE, docs/README.md
- 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
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (code-reviewer) differs from the folder (cuihua-code-reviewer)
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 57 steps
- 100Execution cost. Instruction body is 1796 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- -242 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 303: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 57 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.