verify-first

Enforces verification-before-claiming and approval-gate compliance rules during interactive agent sessions.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill verify-first-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-first
Source: https://github.com/tapway/shogun-os/tree/main/skills/hermes/verify-first
Command: npx skills add https://github.com/tapway/shogun-os --skill verify-first-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often announce success without testing, route around approval blocks, or make destructive changes without confirmation. This Skill applies a behavioral overlay that forces verification, assumption-challenging, and plan-first execution on every turn. ## Core Features & Use Cases - Proof-Based Reporting: Requires a passing test or verification output before the agent may claim something is fixed or working. - Approval Gate Compliance: When a command is blocked by the approval system, the agent must stop rather than circumvent the block with alternative tools. - Pre-Execution Review: Destructive or irreversible changes (file deletions, config edits, restarts) require a presented plan and explicit user confirmation first. - Use Case: During a debugging session, the agent curls the deployed endpoint, checks logs, applies a fix, re-tests to confirm HTTP 200, and only then reports the fix as verified. ## Quick Start Ask the agent to load the verify-first overlay and work cautiously, verifying every change before reporting results.

Frequently Asked Questions about verify-first

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

FAQPage Schema
How do I make an AI agent verify changes before reporting success?

Load the verify-first overlay, which requires the agent to run a verification step such as a test or curl check before announcing any fix. If verification fails, the agent reports the failure honestly instead of assuming success.

What happens when a command is blocked by the approval system?

The agent must stop immediately and wait for explicit user approval. It is forbidden from routing around the block using alternative tools, different shell commands, or file-writing workarounds.

Can verify-first be used in autonomous or cron contexts?

Yes, but only partially. In autonomous contexts, rules 3-5 (challenging assumptions, approval patience, pre-execution review) are skipped since no user is present, while verification rules 1-2 still apply.

When should I not use the verify-first overlay?

Skip it for read-only operations with zero side effects and simple, low-risk single actions. It is designed for interactive sessions involving high-risk, irreversible, or complex troubleshooting work.

Does verify-first require a plan before destructive changes?

Yes. Before destructive or irreversible actions like file deletions, config edits, or process kills, the agent must present a concise plan and wait for explicit confirmation such as "yes" or "go ahead" before executing.