CtrlK
BlogDocsLog inGet started
Tessl Logo

gitnexus-pr-swarm-review

Run a GitNexus production-readiness pull request review using a coordinated reviewer swarm.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/gitnexus-pr-swarm-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

The adapter body is concise and well-structured, with clear lane sequencing and an explicit validation hard gate at lane 7. Its only weakness is that the bulk of executable detail lives in an external orchestration.md that is not bundled with this skill.

DimensionReasoningScore

Conciseness

The body is lean: a one-line purpose, a short distinction blockquote, the command, and four tight bullets pinning only the Claude-Code specifics, with every token earning its place and no concept over-explanation.

5 / 5

Actionability

Gives concrete, executable adapter guidance (dispatch each lane via the Agent tool; lanes 1-2 then 3-6 parallel then 7) but delegates the bulk of executable detail to an external orchestration.md, leaving minor gaps — matches anchor 4.

4 / 5

Workflow Clarity

Sequencing is explicit (lanes 1-2 first, 3-6 parallel, lane 7 last on the draft) and includes a hard-gate validation checkpoint with a feedback loop ('revise and re-run it' until the Required corrections section is empty).

5 / 5

Progressive Disclosure

Well-structured overview that delegates the canonical contract to a clearly signaled, one-level-deep reference (pr-swarm-review/orchestration.md) plus persona files; the referenced paths are not bundled locally, leaving a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

53%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.

The description states a clear, domain-specific purpose but lacks any explicit 'when to use it' trigger clause and omits common synonyms, leaving it at mid-range on completeness and trigger terms. It is distinctive enough to avoid most conflict.

Suggestions

Add an explicit 'Use when ...' clause naming trigger phrases such as 'PR review', 'code review', or 'production-readiness check' to satisfy the 'when' half of completeness.

Include common synonyms/file cues (e.g., 'PR', 'pull request', 'production readiness') to broaden natural trigger-term coverage.

Optionally list 1-2 more concrete actions (e.g., 'dispatches persona subagents and synthesizes findings') to lift specificity above anchor 3.

DimensionReasoningScore

Specificity

Names the domain ('GitNexus production-readiness pull request review') and one concrete action (run a review via a 'coordinated reviewer swarm'), but coverage is not comprehensive — matches anchor 3.

3 / 5

Completeness

Gives a clear 'what' but entirely omits any 'Use when...' trigger clause; per judging guidelines a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Has relevant keywords ('pull request review', 'production-readiness') but misses common synonyms users would say like 'PR review', 'code review', or 'production readiness check', matching anchor 3.

3 / 5

Distinctiveness Conflict Risk

The 'GitNexus production-readiness pull request review using a coordinated reviewer swarm' framing carves a clear niche with only minor overlap risk against generic code-review skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
abhigyanpatwari/GitNexus
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.