BC ai-code-format-review
Use when reviewing AI-generated code for formatting consistency. Enforces naming, structure, comments, and style conventions. Optimized for Java.
Enforces naming, structure, comments, and style conventions.
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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
body-longSKILL.md body ≈ 7650 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 52/100
- 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. 16 mutating operations with no state check
- 40Consistency. Frontmatter name (ai-code-format-review) differs from the folder (java-code-format-review)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 7650 tokens
- 85Steps. 71 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- 100Progress reporting. Reports progress
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
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 145: enough signal without eating the budget
- +4Structure: 27 headings
- +3Step-by-step instructions: 71 items
- +4Has examples (57 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: suspicious
The skill is not malicious, but it is under-scoped for a formatting aid because it can lead an agent to run repository build tools and perform broader correctness review.
LLM: suspicious (high) · VirusTotal: · 23 Jun 2026