skills.rest
michael-conrad
michael-conradCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-enforcement

Verify factual claims against live sources before and after content generation.

Updated Apr 24, 2026
Search Tags:#verification#audit#evidence#verify#workflows#claims#live-sources
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill verification-enforcement
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-enforcement
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/verification-enforcement
Command: npx skills add https://github.com/michael-conrad/.opencode --skill verification-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Verification Enforcement skill ensures that every content claim based on specs, runbooks, docs, or correspondence is verified against live sources before publication and that unverified claims are handled post-generation through a structured escalate path.

Core Features & Use Cases

  • Pre-generation: per-section sub-agents gather live-source artifacts for each factual claim.
  • Post-generation: revisit pass resolves remaining unverified markers and escalates unresolved claims to the developer.
  • Enforcement: reject sub-agent outputs that lack evidence artifacts and re-task or escalate as needed.
  • Scope: applicable to specifications, runbooks, manuals, and formal communications requiring live-source verification.

Quick Start

Invoke verification-enforcement at the start of any content-generation workflow to require live-source verification and artifact collection before release.

Frequently Asked Questions about verification-enforcement

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

FAQPage Schema
How do I enforce live-source verification for factual claims in technical documentation?▼

Live-source verification for factual claims is enforced by gathering evidence artifacts per section before generation and running a post-generation revisit pass to resolve or escalate unverified markers. This ensures every claim in specs, runbooks, and correspondence is supported by live sources before publication.

What is pre-generation verification and how does it work for specification writing?▼

Pre-generation verification deploys per-section sub-agents to gather live-source artifacts for each factual claim before content is generated. Sub-agent outputs lacking evidence artifacts are rejected and re-tasked or escalated to ensure claims are verified upfront.

How do I verify claims in runbooks and official correspondence after generation?▼

Post-generation verification conducts a revisit pass to resolve remaining unverified markers in runbooks and correspondence. Unresolved or unverifiable claims are escalated to the developer through a structured path, ensuring no unsupported claim goes unnoticed.

What happens to sub-agent outputs that lack evidence artifacts during content verification?▼

Sub-agent outputs lacking evidence artifacts are rejected during verification enforcement. The system then re-tasks the sub-agent to gather proper live-source evidence or escalates the unresolved claim to the developer for manual resolution.

Do I need live sources to verify every claim in manuals and formal communications?▼

Yes, live sources are required to verify every factual claim in manuals and formal communications. The enforcement mechanism mandates evidence artifacts for all claims and escalates any unverifiable assertions to the developer for resolution.

When should I use automated verification enforcement instead of manual claim auditing?▼

Automated verification enforcement should be used for specifications, runbooks, manuals, and formal communications requiring live-source verification at scale. It rejects outputs lacking evidence artifacts and escalates unresolved claims, replacing manual cross-referencing with structured pre- and post-generation passes.

Related Skills

Explore More Content & Communication Skills→
Ben2pcBen2pc
1

verification-before-completion

Enforce verification steps before declaring task completion in software workflows.

Official
Advanced
michael-conradmichael-conrad

verification

Verify text, vision, and audio claims against evidence with PASS/FAIL/UNVERIFIED results.

Community
Advanced
barichterbarichter

iterative-retrieval

Implement a max-3-cycle protocol for agent sub-tasks with WHY context and coordinator validation.

Community
Advanced
cegit27cegit27
3

canary

Monitor live production apps for console errors and performance regressions.

Official
Advanced