post-review-pickup

Authoritative protocol for next-lane pickup after ANY PR-lifecycle event boundary (review post, author response, implementation completion, PR open/update, ticket create, blocked-state resolution) AND for pre-review intake lane discovery from fresh boot or watchdog wake when no author lane is active. Prevents silent idle and reviewer-only cycles by requiring active lane selection or a review-first rationale per §15.6 self-select mandate. Triggers: Use immediately after posting a PR review, chaining a formal GitHub review state, sending an author review-response commentId handoff, completing a discrete implementation chunk, opening/updating a PR, creating a ticket via create_issue, resolving a previously blocked state (positive-path exit only; new blockers route to bug/follow-up plus next lane), OR before accepting the first PR review/re-review request in a fresh session/wake when no current author or implementation lane is claimed.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%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 SKILL.md body is an efficient, fully actionable router that points to a real, well-structured atlas reference one level deep. It assumes Claude's intelligence and offloads operational detail to the reference file, exactly as progressive disclosure intends.

Dimension	Reasoning	Score
Conciseness	The body is a single tight router paragraph with no concept explanation or padding; it assumes Claude's competence and points straight to the atlas file, matching the lean 5-anchor.	5 / 5
Actionability	Gives a fully executable instruction — 'use the view_file tool to read and strictly adhere to .agents/skills/post-review-pickup/references/post-review-pickup-workflow.md' — naming the exact tool and exact path, copy-paste ready.	5 / 5
Workflow Clarity	The sole action (read and adhere to the referenced workflow) is unambiguous and gated by explicit lifecycle triggers; the simple-skill exception applies, and validation/feedback loops live correctly in the referenced workflow (§5 freshness gate).	5 / 5
Progressive Disclosure	Body is a clean overview with one clearly signaled one-level-deep reference (verified to exist), and the referenced workflow file in turn links one-level-deep siblings, giving easy navigation and appropriate content splitting.	5 / 5
	Total	20 / 20 Passed

Description

100%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 is explicit, comprehensive, and uses third-person voice with a dedicated Triggers block answering both what and when. It is dense but every clause earns its place; no fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — 'next-lane pickup after ANY PR-lifecycle event boundary', 'pre-review intake lane discovery', 'active lane selection or a review-first rationale' — covering the domain comprehensively, matching the 5-anchor.	5 / 5
Completeness	Clearly answers both 'what' (authoritative next-lane pickup and pre-review intake discovery protocol) and 'when' ('Triggers: Use immediately after...' with concrete trigger phrases), matching the 5-anchor exactly.	5 / 5
Trigger Term Quality	An explicit 'Triggers:' block lists natural lifecycle phrases ('posting a PR review', 'opening/updating a PR', 'creating a ticket via create_issue', 'resolving a previously blocked state') giving comprehensive coverage of terms users would actually say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clearly scoped niche — PR-lifecycle event-boundary lane pickup and pre-review intake — with distinct triggers that are unlikely to fire for the wrong skill; minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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: neomjs/neo
Path: .agents/skills/post-review-pickup/SKILL.md
Commit: 210c03c

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.