CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adjudicate-review

Turn an incoming set of findings — from an AI reviewer, a referee report, a code review, a linter, or a second model — into verified fixes, without letting a confident misread damage correct work. Every finding is a CANDIDATE until checked against the actual source. Use whenever you receive review comments, audit findings, or a critique you did not write yourself, especially when the reviewer is a model or when the volume is too large to check by feel.

Quality

70%

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 ./.agents/skills/adjudicate-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 body is a generated redirect stub: concise and clearly written, but it contains none of the skill's actual instructions, and every load-bearing reference points outside the bundle to files that are not present, so the skill is unnavigable and non-actionable as shipped here. Only the cross-agent portability notes carry concrete guidance.

Suggestions

Inline the actual adjudication procedure (or ship the source .claude/skills/adjudicate-review/SKILL.md and AGENTS.md inside the bundle at the referenced relative paths) so the primary 'Read that file now' instruction resolves and the skill is self-contained.

Add the skill's core workflow steps — candidate classification, source-checking, and a validate/fix/re-verify loop for batch findings — directly in the body so a reader can act without the missing external file.

Trim the Codex/Antigravity adaptation bullets and the 'Generated by' comment into a short portability note or separate reference file to earn back conciseness tokens.

DimensionReasoningScore

Conciseness

The ~25-line body is lean with no explanations of concepts Claude already knows — every section is either a redirect ('Read that file now and follow it') or concrete portability rules. It falls short of anchor 5 because the Codex/Antigravity adaptation bullets and the generator comment ('Generated by scripts/sync-agent-skills.py ...') spend tokens irrelevant to the primary Claude Code runtime and could be trimmed.

4 / 5

Actionability

The core instruction is 'This skill's instructions live in .claude/skills/adjudicate-review/SKILL.md. Read that file now and follow it' — a high-level pointer, not executable guidance for the skill's actual task, and the referenced path does not resolve within this bundle. The cross-agent bullets ('use what the user asked for' for $ARGUMENTS, 'run it in a separate session') are concrete, but the specific steps to execute are entirely deferred, matching anchor 2 rather than anchor 3's 'incomplete but present' concrete guidance.

2 / 5

Workflow Clarity

A clear reading sequence is present ('Read AGENTS.md first if you have not already', then the source SKILL.md 'and the files it points to'), but no validation checkpoints exist and the actual adjudication procedure — a batch verification workflow where feedback loops matter — is not in this document, capping the score at 3 per the batch-validation guideline. It is above anchor 2 because the listed steps are well-defined and correctly ordered, not 'rough' with 'many gaps'.

3 / 5

Progressive Disclosure

References are clearly signaled and nominally one level deep (SKILL.md → source SKILL.md), but scored against the actual bundle structure the targets are dangling: no references/, scripts/, or assets/ directories exist, and neither ../../../.claude/skills/adjudicate-review/SKILL.md nor ../../../AGENTS.md resolves, so navigation dead-ends at the first hop. This lands at anchor 3 — structure and signaling present, but the organization does not actually deliver the content.

3 / 5

Total

12

/

20

Passed

Description

78%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: it explicitly states what the skill does and when to use it, with natural trigger terms and a distinctive 'not written by you' carve-out. The only deductions are second-person phrasing in the trigger clause and slightly thin coverage of concrete capability actions and trigger synonyms.

DimensionReasoningScore

Specificity

The description names the domain and concrete actions — 'Turn an incoming set of findings ... into verified fixes' and 'checked against the actual source' — plus a specific input enumeration ('AI reviewer, a referee report, a code review, a linter, or a second model'), which sits between anchors 3 and 4 (1-2 core actions, good input coverage but not multiple distinct capability actions). The trigger clause uses second person ('whenever you receive review comments', 'a critique you did not write yourself'), so per the judging guidelines the score is reduced by 1 from 4 to 3.

3 / 5

Completeness

Both questions are answered explicitly: what ('Turn an incoming set of findings ... into verified fixes, without letting a confident misread damage correct work') and when ('Use whenever you receive review comments, audit findings, or a critique you did not write yourself, especially when the reviewer is a model or when the volume is too large to check by feel') — a concrete 'Use when...' clause with specific trigger phrases, matching anchor 5 exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'review comments', 'audit findings', 'critique', 'code review', 'linter', 'referee report' — phrases a user would plausibly say when needing this skill. It falls short of anchor 5 because common variations like 'PR feedback', 'pull request comments', or 'reviewer suggestions' are missing, but it clearly exceeds anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (verifying findings produced by others) with a distinguishing qualifier — 'a critique you did not write yourself' — that separates it from review-producing skills. Minor overlap risk remains with closely related code-review/review-response skills, so anchor 4 fits better than anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

pedrohcgs/claude-code-my-workflow

Path

.agents/skills/adjudicate-review/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.