flux-verify-claims

Execute proving commands and report real outcomes from exit statuses.

7|1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Nairon-AI/flux --skill flux-verify-claims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flux-verify-claims
Source: https://github.com/Nairon-AI/flux/tree/main/skills/flux-verify-claims
Command: npx skills add https://github.com/Nairon-AI/flux --skill flux-verify-claims

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Do not claim success from inference; this skill ensures you verify claims by executing the exact command that proves the result and by examining the output to state the real outcome.

Core Features & Use Cases

  • Standardizes a verification gate before any completion claim, ensuring the claim is backed by reproducible evidence.
  • Guides users through identifying the proving command, executing it, and interpreting the exit status and output for reliable validation.
  • Applies to tests, builds, bug fixes, reviews, and releases to improve trust in increments.

Quick Start

Identify the proving command, run it, and report the outcome.

Frequently Asked Questions about flux-verify-claims

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

FAQPage Schema
How do I verify build outcomes and test results using command output?

Verify build or test outcomes by executing the exact proving command, capturing its output and exit status, then evaluating the real result to confirm the claim instead of relying on inference.

What is the best way to validate a bug fix before claiming completion?

Validating a bug fix requires running the command that proves the resolution, examining the command output and exit status, and reporting the actual outcome to ensure the claim is backed by reproducible evidence.

How do I standardize a verification gate for CI/CD release workflows?

Standardize a verification gate for CI/CD releases by identifying the proving command, executing it, and interpreting the exit status and output to reliably validate increments before any completion claim.

Does claim verification work for task validation across development workflows?

Claim verification applies to tests, builds, bug fixes, reviews, and releases across development workflows, requiring the execution of the proving command and the evaluation of its output to state the real outcome.

Can I confirm a successful build without manually checking the command output?

You cannot confirm a successful build from inference alone; you must execute the proving command, capture its output and exit status, and report the real result to ensure the completion claim is valid.