CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-and-evaluate

Runs two parallel agents — one performs a rigorous PR review (via the review-pr skill), the other evaluates findings against the project's design context (ADRs, sprint goals) — then synthesizes a decision-ready report with Apply / Skip / Discuss verdicts per finding. Copied from zora-pantheon `.claude/commands/review-and-evaluate.md` and adapted to this repo's skill structure.

Quality

81%

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

82%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 tight, highly actionable orchestration skill: verbatim commands, fully specified agent prompts, and a concrete output format with a clear verdict taxonomy. The main gaps are missing validation/error-recovery checkpoints in the workflow and a slightly long inline agent-task spec that could be split out.

DimensionReasoningScore

Conciseness

The body is efficient and command-first with no explanations of concepts Claude already knows — git commands, agent prompts, and output structure are given directly. Minor trims are possible (the opening paragraph repeats the frontmatter description; "(MANDATORY)" and the parenthetical /pr-iterate note are slight padding), so it sits just below the every-token-earns-its-place level-5 anchor.

4 / 5

Actionability

Fully executable throughout: verbatim commands (`git fetch origin`, `git merge-base origin/main HEAD`, `git diff <merge-base>..HEAD --name-only`), complete copy-paste-ready agent task prompts with explicit overrides, a concrete report template with a table schema, and the exact closing question. This matches the fully-executable level-5 anchor.

5 / 5

Workflow Clarity

A clear 0 → 1 → 2 sequence with concrete commands at each step and explicit guardrails ("Do NOT rebase or modify the current branch", "Do NOT post anything to GitHub", "Skip steps 6 and 7 entirely"). It falls short of level 5 because there are no explicit validation checkpoints or error-recovery loops — e.g., what to do if the merge-base lookup fails, the branch has no unique commits, or an agent returns ambiguous output.

4 / 5

Progressive Disclosure

The skill has no bundle files, and the body is well-organized into numbered protocol steps with the detailed agent-task specs appropriately inline as core instruction. File references are one level deep and clearly signaled (`.agents/skills/review-pr/SKILL.md`, `docs/adr/`, `docs/spec.html`, `docs/diary.md`). At ~75 lines it exceeds the under-50-line simple-skill case, and the Agent 2 prompt's six-step spec could arguably live in a reference file, so it does not quite reach a 5.

4 / 5

Total

17

/

20

Passed

Description

71%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 specific, action-rich description that clearly communicates what the skill does, undermined by the complete absence of any "when to use this" trigger guidance. It also carries a provenance sentence ("Copied from zora-pantheon ... adapted to this repo's skill structure") that adds tokens without helping triggering or capability communication.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing a pull request before merging, or when the user asks whether PR findings align with sprint goals or ADRs."

Include common synonyms such as "pull request", "code review", and "pre-merge review" so natural phrasings match the trigger terms.

Remove or shorten the provenance sentence ("Copied from zora-pantheon .claude/commands/... and adapted...") — it is repo history, not capability description, and wastes description tokens.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "performs a rigorous PR review", "evaluates findings against the project's design context (ADRs, sprint goals)", "synthesizes a decision-ready report with Apply / Skip / Discuss verdicts per finding" — comprehensively covering the skill's function. It exceeds the level-4 anchor because there are no meaningful gaps in action coverage.

5 / 5

Completeness

The "what" is clearly and concretely answered, but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is entirely absent. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "PR review", "sprint goals", "ADRs", and "findings" are present and match what a user would say. A few common variations are missing ("pull request" spelled out, "code review", "before merging"), keeping it below the comprehensive-synonyms level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The combined review-plus-alignment-synthesis niche with Apply/Skip/Discuss verdicts is mostly distinct from other skills. There is minor overlap risk with a plain PR-review skill, which the description itself references ("via the review-pr skill"), so it does not reach the minimal-conflict level-5 anchor.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agranado2k/ai-report-platform

Path

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