verify-this

Validate claims by comparing baseline and treatment artifacts into a verdict.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill verify-this-kscius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-this
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/verify-this
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill verify-this-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify or falsify claims by generating fresh local evidence, providing a reproducible baseline, a treatment state, and a clear verdict.

Core Features & Use Cases

  • Restate a claim in falsifiable terms and outline the expected outcome.
  • Capture a baseline from the current state and obtain a treated state after applying changes.
  • Compare artifacts (numbers, logs, outputs) and return a single verdict: VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
  • Use in QA, debugging, and validation workflows to triage claims about software behavior, performance, or API responses.

Quick Start

Provide a concrete, falsifiable claim and request a reproducible verification that yields a VERIFIED, NOT VERIFIED, or INCONCLUSIVE verdict.

Frequently Asked Questions about verify-this

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

FAQPage Schema
How do I verify a software claim with reproducible evidence?

You can validate debugging claims by capturing a baseline state, applying a treatment, comparing the resulting artifacts, and returning an objective verdict of VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

What is the best way to validate API response changes?

You can validate API response changes by generating fresh local evidence, capturing baseline and treated states, comparing the output artifacts, and returning an objective VERIFIED or NOT VERIFIED verdict.

How do I prove performance validation claims using before and after comparison?

You prove performance validation claims by capturing a baseline, applying changes to obtain a treated state, comparing the objective artifacts, and returning a VERIFIED, NOT VERIFIED, or INCONCLUSIVE verdict.

Can I use this approach for QA and debugging triage?

Yes, you can use this approach for QA and debugging triage to validate claims about software behavior by comparing baseline and treatment artifacts to reach a clear, objective verdict.

What does an inconclusive verdict mean in claim verification?

An INCONCLUSIVE verdict means the fresh local evidence generated from comparing baseline and treatment artifacts was insufficient to definitively prove or falsify the claim.