BC sonarqube-autofix
Use when analyzing SonarQube issues and turning them into SPEC SDDs for TDD implementation.
Analyze issues reported by SonarQube, regardless of language or framework, classify them by type, and create approved SPEC SDDs that describe the fixes.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6775 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 20 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 60Steps. 153 steps, 8 vague phrases
- 70Execution cost. Instruction body is 6775 tokens
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 20 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 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 91: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -244 emoji in the instructions: noise for the model
- +2Single-language instructions
- +4Structure: 71 headings
- +3Step-by-step instructions: 153 items
- +4Has examples (20 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: suspicious
The skill is mostly aligned with SonarQube remediation, but it gives the agent broad repository-changing and tool-execution authority with several unsafe or under-scoped behaviors.
LLM: suspicious (high) · 12 Sept 2026