AF review-go
Comprehensive Go backend code review with optional parallel review areas. Use when reviewing changed Go files; detects BubbleTea, Wish SSH, and Prometheus and loads the matching review skills.
As a process F 51/100 · Will not run — References files that are not bundled: ../review-verification-protocol/SKILL.md, ../go-code-review/SKILL.md, ../go-testing-code-review/SKILL.md
How to improve
- 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 · 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
missing-refreference to a missing file: ../review-verification-protocol/SKILL.md - warning
missing-refreference to a missing file: ../go-code-review/SKILL.md - warning
missing-refreference to a missing file: ../go-testing-code-review/SKILL.md - warning
missing-refreference to a missing file: ../bubbletea-code-review/SKILL.md - warning
missing-refreference to a missing file: ../wish-ssh-code-review/SKILL.md - warning
missing-refreference to a missing file: ../prometheus-go-code-review/SKILL.md
Process rating: all ten parameters 51/100
- 0Tools and files. 6 referenced file(s) missing: ../review-verification-protocol/SKILL.md, ../go-code-review/SKILL.md, ../go-testing-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. 2 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 45 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1860 tokens
- low 11 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)
- +1No license
- +2Single-language instructions
- +3Description length 192: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.