util-verify

Enforce evidence-backed claims with a five-step verification workflow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/180VRisLife/.claude --skill util-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: util-verify
Source: https://github.com/180VRisLife/.claude/tree/main/skills/utl-verify
Command: npx skills add https://github.com/180VRisLife/.claude --skill util-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evidence is required before any completion claims are asserted; this skill enforces a strict verification before reporting results.

Core Features & Use Cases

  • Implements a structured five-step verification workflow (IDENTIFY, RUN, READ, VERIFY, ONLY THEN) to validate claims with fresh outputs.
  • Prevents premature status updates by requiring concrete evidence from fresh runs.
  • Ideal for development, QA, and agent workflows that demand verifiable, reproducible results.

Quick Start

Run the full verification command in your environment and paste the resulting output here for evaluation.

Frequently Asked Questions about util-verify

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

FAQPage Schema
How do I enforce evidence-backed claims for development and QA workflows?

Evidence-backed completion requires a strict verification process before reporting results. It enforces a five-step workflow—IDENTIFY, RUN, READ, VERIFY, ONLY THEN—ensuring claims about tests, builds, or fixes are proven with fresh command outputs.

What is the structured verification process for validating agent workflow claims?

The structured verification process is a five-step workflow: IDENTIFY the claim, RUN the command, READ the output, VERIFY the evidence, and ONLY THEN assert completion. This mechanism ensures reproducible results by requiring fresh outputs.

How do I prevent premature status updates in automated agent workflows?

Prevent premature status updates by requiring concrete evidence from fresh command runs before any completion status is asserted. This governance approach ensures claims about tests or fixes are fully validated with fresh outputs rather than assumptions.

Does evidence-backed verification work for quality assurance and governance compliance?

Yes, evidence-backed verification is ideal for quality assurance and governance compliance workflows that demand verifiable, reproducible results. It ensures development and QA claims are strictly validated with fresh command outputs before completion.

How do I validate test and build claims with fresh command outputs?

Validate test and build claims by running the full verification command in your environment, reading the fresh output, and verifying it proves the claim. Only then can you assert completion status, ensuring reproducible results.