verify-this

Verify claims by capturing baseline and treatment evidence and returning a verdict.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill verify-this-ryanportfolio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-this
Source: https://github.com/ryanportfolio/threejs-interview-test/tree/main/.agents/skills/verify-this
Command: npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill verify-this-ryanportfolio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It resolves uncertainty about whether a change actually worked by replacing assumptions with fresh local evidence, producing a clear VERIFIED, NOT VERIFIED, or INCONCLUSIVE verdict. ## Core Features & Use Cases - Falsifiable Restatement: Restates any claim as a testable statement before gathering evidence. - Baseline vs Treatment Comparison: Captures before-and-after evidence locally and compares the two states. - Explicit Verdicts: Returns VERIFIED, NOT VERIFIED, or INCONCLUSIVE so results are never ambiguous. - Use Case: After applying a bug fix, ask the assistant to prove the fix works; it restates the claim, runs the failing scenario before and after, and reports a verdict with evidence. ## Quick Start Ask the assistant to verify that the recent fix resolved the reported issue and show the supporting evidence.

Frequently Asked Questions about verify-this

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

FAQPage Schema
How do I verify that a code fix actually worked?▼

Restate the claim as a falsifiable statement, capture the baseline behavior, apply the change, then capture the treatment behavior and compare. The skill returns VERIFIED, NOT VERIFIED, or INCONCLUSIVE based on the evidence.

What evidence does a verification workflow need?▼

It needs fresh local evidence from both a baseline run and a treatment run of the same scenario. Comparing the two states determines whether the claim holds rather than relying on assumptions.

When does verification return INCONCLUSIVE instead of VERIFIED?▼

It returns INCONCLUSIVE when the captured evidence is insufficient or ambiguous to confirm or refute the claim. This happens when baseline and treatment cannot be cleanly compared or the environment prevents reliable measurement.

Can this skill commit or push changes after verifying?▼

No. Skill invocation alone does not authorize commits, pushes, pull requests, deploys, or dependency installation. Those outward actions require an explicit user request.

What are the limitations of evidence-based claim verification?▼

Verification only covers what can be observed locally at the time of testing. Flaky environments, non-deterministic behavior, or untestable claims may yield INCONCLUSIVE results rather than a definitive verdict.