skip-reviewer

Skip re-review processes for validated model paths within the Trust harness.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill skip-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skip-reviewer
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/skip-reviewer
Command: npx skills add https://github.com/AesopScott/mojo --skill skip-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the inefficiency of redundant review cycles in the Trust harness, preventing unnecessary expenditure of tokens, compute, and human effort when trust remains valid.

Core Features & Use Cases

  • Cost Efficiency Control: Implements logic to bypass re-review processes for trusted provider or model paths.
  • Harness Boundary Management: Provides a structured runbook for inspecting and modifying trust boundaries without compromising safety.
  • Use Case: When you have a verified model route that has already passed security checks, use this skill to skip the re-review step for subsequent identical requests to save on operational costs.

Quick Start

Invoke the skip-reviewer skill to analyze the current trust boundary and apply a cost-saving rule to bypass re-review for the specified model path.

Frequently Asked Questions about skip-reviewer

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

FAQPage Schema
How do I skip redundant model re-reviews to save token and compute costs?

You can skip redundant model re-reviews by applying conditional routing rules to bypass verification for validated paths. This requires verifying the trust state remains valid and adhering to defined safety gates before modifying route rules.

What is a trust harness boundary in software engineering workflows?

A trust harness boundary defines the validated provider or model paths that have already passed security checks. Managing this boundary allows you to control which requests require re-review and which can be safely skipped to optimize operational costs.

How do I configure conditional skipping of re-review processes for trusted model paths?

To configure conditional skipping, invoke the skip-reviewer skill to analyze the current trust boundary. You then apply a cost-saving rule that bypasses re-review for the specified verified model route, ensuring safety gates are respected.

When should I avoid skipping the re-review step in my automation workflow?

You should avoid skipping the re-review step if the trust state is unverified or the model path has not passed defined safety gates. Skipping is only safe for subsequent identical requests where trust remains valid.

Can I use this cost efficiency control for any software engineering automation workflow?

This cost efficiency control is specifically designed for software engineering workflows using the Trust harness where token usage and compute overhead must be strictly bounded. It requires defined safety gates and verified trust states to function safely.