BF review-python
Comprehensive Python/FastAPI backend code review with optional parallel agents
As a process F 48/100 · Will not run — References files that are not bundled: ../review-verification-protocol/SKILL.md, ../python-code-review/SKILL.md, ../fastapi-code-review/SKILL.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.
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: 2. 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: ../review-verification-protocol/SKILL.md - warning
missing-refreference to a missing file: ../python-code-review/SKILL.md - warning
missing-refreference to a missing file: ../fastapi-code-review/SKILL.md - warning
missing-refreference to a missing file: ../pytest-code-review/SKILL.md - warning
missing-refreference to a missing file: ../../../beagle-ai/skills/pydantic-ai-common-pitfalls/SKILL.md - warning
missing-refreference to a missing file: ../sqlalchemy-code-review/SKILL.md - warning
missing-refreference to a missing file: ../postgres-code-review/SKILL.md
Process rating: all ten parameters 48/100
Will not run. References files that are not bundled: ../review-verification-protocol/SKILL.md, ../python-code-review/SKILL.md, ../fastapi-code-review/SKILL.md
- 0Tools and files. 7 referenced file(s) missing: ../review-verification-protocol/SKILL.md, ../python-code-review/SKILL.md, ../fastapi-code-review/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Failures and branches. 4 branches
- 100Steps. 50 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2414 tokens
- low 13 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)
- +3Description length 78: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 19 headings
- +3Step-by-step instructions: 50 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.
External checks
ClawHub: clean
The available scan context is clean and does not show behavior that is hidden, destructive, or outside the skill’s stated purpose.
LLM: benign (medium) · VirusTotal: · 1 Jun 2026