CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-swarm

Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review,...

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured orchestration skill with an unusually clear workflow: scope resolution, parallel launch rules, filtering, ordering, and a path forward are all explicitly sequenced. The main cost is redundancy — the read-only constraint and reviewer role are restated per sub-agent — and the absence of a concrete prompt template keeps guidance one step short of copy-paste ready.

Suggestions

State the read-only constraint once in Step 2 ("Every sub-agent is read-only: no edits, apply_patch, staging, or commits") and delete the two-sentence repetition from each of the four sub-agent sections; likewise state "Recommended sub-agent role: `reviewer`" once.

Add a short literal example of the sub-agent prompt and one example normalized finding (file/line, category, severity, why, fix, confidence) so the launch and output steps are copy-paste ready.

Move the four sub-agent role checklists into references/ (e.g. references/reviewer-roles.md) and summarize each role in one line in SKILL.md, keeping the always-loaded overview lean.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence (no explanations of git or review concepts), but the constraint "This sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes" is repeated verbatim in all four sub-agent sections after the same rule already appears in the Step 2 bullet list, and "Recommended sub-agent role: `reviewer`" is repeated four times. This systematic redundancy (~10 lines) goes beyond the 4 anchor's 'minor instances that could be trimmed' and fits the 3 anchor's 'could be tightened'.

3 / 5

Actionability

Concrete, executable guidance throughout: exact diff commands ("git diff", "git diff --cached"), an explicit per-sub-agent prompt checklist ("file and line or symbol, issue, why it matters, recommended follow-up, and confidence"), a normalized finding schema with severity/confidence enums, and named output groupings ("fix now", "fix soon", "optional follow-up"). It falls short of 5 because no literal sub-agent prompt template or example rendered finding is provided — the launcher must assemble prompts from the requirement lists.

4 / 5

Workflow Clarity

Five clearly sequenced steps with explicit decision checkpoints: a scope-precedence order with "If there is no clear review scope, stop and say so briefly", an intent-inference fallback ("infer it from the diff and say that the inference may be incomplete"), aggressive filtering rules, and an escape hatch ("If there are no material issues, say that directly"). The skill is read-only, so destructive/batch validation caps do not apply, and the checklist-plus-decision-gate structure matches the 5 anchor.

5 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well-sectioned (When to Use, Steps 1-5, Limitations) with no buried or nested references. This fits the 4 anchor's good-structure placement; it is not 5 because the file is ~185 lines and the four sub-agent role checklists, which are only needed at launch time, could arguably live in reference files to slim the always-loaded overview.

4 / 5

Total

16

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete capability statement, and an explicit 'Use when' trigger clause. Its only real defect is the literal trailing "..." after the trigger list, which reads as a truncation artifact and leaves trigger coverage slightly incomplete.

Suggestions

Replace the trailing "..." in the trigger clause with a complete list, e.g. "Use when the user asks for a review swarm, parallel review, diff review, code review, or review of changed files."

DimensionReasoningScore

Specificity

The description names the mechanism ("Parallel read-only multi-agent review of a current git diff or explicit file scope") and comprehensively enumerates what it finds ("behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps"), matching the comprehensive-coverage anchor. Not 4 because the finding categories plus the read-only/parallel mechanics leave no material gaps in what the skill does.

5 / 5

Completeness

It explicitly answers both questions: what ("Parallel read-only multi-agent review ... to find behavioral regressions, security or privacy risks...") and when ("Use when the user asks for a review swarm, parallel review, diff review"). This mirrors the 5 anchor's what-plus-concrete-trigger-phrases pattern; the 4 anchor would require the 'when' clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Trigger terms are natural ("Use when the user asks for a review swarm, parallel review, diff review") but the list is visibly cut off by a literal trailing "..." and omits common phrasings like "code review" or "review my changes". It matches the good-coverage-with-a-few-missing-terms anchor rather than 5's comprehensive synonym coverage, and is well above 3 since multiple natural phrases users would say are present.

4 / 5

Distinctiveness Conflict Risk

The multi-agent read-only review swarm niche is mostly distinct, but broad triggers like "review" or "diff review" create minor overlap with any generic code-review skill a user might have. Fits the 4 anchor (mostly distinct, minor overlap with closely related skills) better than 5, since a plain "review this diff" request would plausibly fire both this and a standard code-review skill.

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/review-swarm/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.