CC auto-review-loop
Autonomous multi-round research review loop. In Copilot CLI it defaults to the native complementary rubber-duck subagent with host-event model evidence; elsewhere it uses Codex, while explicit external reviewer overrides remain available. Implements fixes and re-reviews until a policy-approved positive assessment or max rounds is reached.
Autonomous multi-round research review loop.
As a process C 68/100 · Has gaps — References files that are not bundled: ../shared-references/external-cadence.md, ../shared-references/reviewer-backends.md, ../shared-references/output-versioning.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bash(*)allowed-tools: Bash(*) Read Grep Glob Write Edit Skill Task mcp__codex__codex mcp__codex__codex-reply mcp__manual_review__review mcp__manual_review__review_reply mcp__antigravity__antigravity mcp__ant
Files scanned: 1. 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
body-longSKILL.md body ≈ 18582 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../shared-references/external-cadence.md - warning
missing-refreference to a missing file: ../shared-references/reviewer-backends.md - warning
missing-refreference to a missing file: ../shared-references/output-versioning.md - warning
missing-refreference to a missing file: ../shared-references/output-manifest.md - warning
missing-refreference to a missing file: ../shared-references/output-language.md - warning
missing-refreference to a missing file: ../shared-references/reviewer-routing.md - note
edit-residuethe text marks something as outdated (lines 21, 51, 250, 259): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 68/100
- 0Tools and files. 6 referenced file(s) missing: ../shared-references/external-cadence.md, ../shared-references/reviewer-backends.md, ../shared-references/output-versioning.md
- 10Execution cost. Instruction body is 18582 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 85Steps. 141 steps, 1 vague phrases
- 100Result and completion. Output format and completion criterion are stated
- 100Inputs and preconditions. Inputs and preconditions are listed
- 100Failures and branches. 8 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
- high The skill tells the model to perform an irreversible action with no human approval
- low The response is described with custom markup (23 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)
- +1No license
- +2Single-language instructions
- +3Description length 340: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 141 items
- +3Output format is stated explicitly
- +4Has examples (18 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 53.