skills.rest
AshleyHollis
AshleyHollisCOMMUNITY
Explore all skills by this author →
GitHub

reviewer-protocol

Enforce structured artifact review workflows with author lockout after rejection.

Updated May 10, 2026
Search Tags:#review workflow#independent review#reviewer protocol#reviewer lockout#artifact revision
One-click install
npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill reviewer-protocol-ashleyhollis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewer-protocol
Source: https://github.com/AshleyHollis/agentic-identity-lab/tree/main/.copilot/skills/reviewer-protocol
Command: npx skills add https://github.com/AshleyHollis/agentic-identity-lab --skill reviewer-protocol-ashleyhollis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enforces a structured workflow for artifact reviews, ensuring independent reviews and preventing original authors from revising their own work after rejection.

Core Features & Use Cases

  • Reviewer Rejection Protocol: Supports reviewer approval or rejection with reassignment or escalation options.
  • Strict Lockout Semantics: Locks out original authors after rejection, requiring a different agent for revisions.
  • Mechanical Enforcement: Coordinator ensures rules are followed, verifying revision authors are not the original authors.
  • Scope and Duration: Lockout applies to specific artifacts and persists through revision cycles.

Quick Start

Activate the 'reviewer-protocol' skill with a rejected artifact and specify the required action or new agent for the revision.

Frequently Asked Questions about reviewer-protocol

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce an independent artifact review workflow where rejected authors cannot revise their own work?▼

You can enforce independent artifact reviews by activating a reviewer protocol with the rejected artifact and specifying a new agent for the revision. The Coordinator mechanically verifies that the revision author is not the original author.

What is a reviewer lockout and how does it work during artifact revision?▼

A reviewer lockout prevents the original author from modifying a specific artifact after rejection. This lockout persists through revision cycles and requires a different agent to handle the artifact revision.

How do I assign artifact revisions to a different agent after a reviewer rejection?▼

To assign revisions after a reviewer rejection, trigger the rejection protocol and specify the required action or new agent for the revision. The Coordinator then enforces the reassignment and verifies the new author.

Can I escalate an artifact review rejection if the original author cannot perform the revision?▼

Yes, the reviewer rejection protocol supports reviewer approval, rejection, reassignment, or escalation options. You can escalate the rejected artifact to ensure a different agent handles the required revision.

Does the reviewer lockout apply permanently to the artifact or only during a single revision cycle?▼

The reviewer lockout applies to specific artifacts and persists through revision cycles. This ensures the original author remains locked out of revisions across the entire duration of the independent review workflow.

Related Skills

Explore More Software Engineering Skills→
sachinnair90sachinnair90

reviewer-protocol

Enforces rejection lockout and reassigns revisions to different agents.

Community
Advanced
QuintenpsQuintenps

reviewer-protocol

Enforce reviewer lockout and reassign rejected artifacts to new agents.

Community
Advanced
jperezdelrealjperezdelreal

reviewer-protocol

Enforce lockout and delegation rules after reviewer rejection.

Community
Advanced
jguadagnojguadagno
18

reviewer-protocol

Enforce author lockout policies during reviewer rejection workflows.

Community
Advanced