CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reviewer-protocol

Reviewer rejection workflow and strict lockout semantics

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/reviewer-protocol/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 body is a well-structured, highly actionable orchestration protocol: explicit MUST rules, concrete coordinator dialogue, sequenced workflows with verification checkpoints and deadlock escalation, worked examples, and an anti-pattern checklist. Its only real weaknesses are the dense bolted-on Waza/Rai boundary paragraphs, which slightly hurt conciseness and organization.

DimensionReasoningScore

Conciseness

The body is dominated by terse imperatives ("The original author is locked out. They may NOT produce the next version of that artifact. No exceptions.") with no explanation of concepts Claude already knows, matching the "efficient; minor instances of over-explanation" anchor. It misses anchor 5 because the dense "Waza rejection boundary (Squad only)" and "Rai/Fact Checker output boundary" paragraphs read as appended policy blocks with some redundancy, and the Context section restates the Patterns premise ("This prevents defensive feedback loops...").

4 / 5

Actionability

The guidance is fully executable as behavior: explicit MUST directives ("the Coordinator MUST verify that the selected agent is NOT the original author"; "the Coordinator MUST refuse and ask the Reviewer to name a different agent"), ready-to-use coordinator dialogue ("The original author is locked out. Please name a different agent."), and four worked examples covering the common cases (reassign, escalate, deadlock, reviewer mis-assignment). Per the scoring notes, the absence of code in an instruction-only skill is not penalized when the guidance is this actionable.

5 / 5

Workflow Clarity

The rejection → lockout → revision → rereview → approval sequence is explicit throughout, with a pre-spawn validation checkpoint ("Before spawning a revision agent, the Coordinator MUST verify that the selected agent is NOT the original author"), a focused rereview gate before approval, and an error-recovery escalation path for deadlock ("the Coordinator MUST escalate to the user rather than re-admitting a locked-out author"). The examples walk each full sequence step by step.

5 / 5

Progressive Disclosure

Sections (Context, Patterns with subsections, Examples, Anti-Patterns) are clearly headed and easy to navigate with no nested references, matching the "good structure; minor organization gaps" anchor. It does not reach anchor 5 because the skill exceeds 50 lines yet inlines two dense, tangential sub-policy paragraphs ("Waza rejection boundary (Squad only)", "Rai/Fact Checker output boundary") mid-section that would be better placed in their own signaled sections or a separate reference file.

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 names a distinct, recognizable niche but is a bare noun phrase: it conveys the 'what' at a high level while omitting any 'use when' trigger guidance, natural keyword variations, and the specific enforcement actions the skill actually performs. It lands at the midpoint of the scale on most dimensions.

Suggestions

Add an explicit trigger clause for completeness, e.g.: "Use when an agent with a Reviewer role (Tester, Code Reviewer, Lead) rejects or blocks another agent's work and a revision must be assigned."

Broaden natural trigger terms to cover keyword variations users would actually say: "rejects", "approve", "blocked", "revision", "reassign", "escalate".

State the concrete actions performed rather than naming topics only, e.g.: "Enforces reviewer reassignment or escalation on rejection, locks the original author out of revising the rejected artifact, and escalates deadlocks to the user."

DimensionReasoningScore

Specificity

"Reviewer rejection workflow" and "strict lockout semantics" name the domain plus two concrete processes, matching the anchor for naming a domain and 1-2 concrete actions without comprehensive coverage (coordinator enforcement, escalation, and deadlock handling are all absent). It is above a bare domain name (anchor 2) but does not list several specific actions with only minor gaps (anchor 4).

3 / 5

Completeness

The 'what' is stated clearly ("Reviewer rejection workflow and strict lockout semantics") but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"Reviewer" and "rejection" are natural terms a user orchestrating agent teams might say, but common variations and synonyms ("reject", "approve", "code review", "revision", "escalate") are missing, matching the "some relevant keywords but missing common variations" anchor. It falls short of anchor 4's good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

The phrase "strict lockout semantics" carves a distinct niche in agent orchestration with minimal conflict risk, but "Reviewer" and "rejection" have minor overlap with general code-review skills, matching the "mostly distinct; minor overlap risk" anchor. It does not reach anchor 5's clear-niche-with-distinct-triggers level because the description carries no explicit trigger phrases.

4 / 5

Total

13

/

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

microsoft/waza

Path

.github/skills/reviewer-protocol/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.