How do I install the Verify skill?

Run npx skillmds add thedixitjain/verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Verify skill do?

Prove a RuView result is real — run the deterministic SHA-256 proof and the witness bundle (ADR-028), and lint any claim for MEASURED-vs-CLAIMED honesty. It is listed under Coding & Dev Tools on SkillMD.

Is Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Verify?

thedixitjain (@thedixitjain) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Verify by thedixitjain — Agent Skill

Name: Verify
Rating: 4.2 (5 reviews)
Author: thedixitjain

File contents

verify

The "prove everything" skill. Nothing ships as validated without this.

Deterministic proof (Trust Kill Switch)

ruview_verify runs archive/v1/data/proof/verify.py: it feeds a reference signal through the production pipeline and hashes the output against expected_features.sha256. Must print VERDICT: PASS. If numpy/scipy changed the hash, regenerate with verify.py --generate-hash then re-verify.

Witness bundle (ADR-028)

For a release-grade attestation:

bash scripts/generate-witness-bundle.sh
cd dist/witness-bundle-ADR028-*/ && bash VERIFY.sh   # must be 7/7 PASS

Contains the Rust test log, the proof + expected hash, firmware SHA-256 manifest, and crate versions — a recipient can re-verify with one command.

Claim honesty

Run ruview_claim_check {text} on any report, README section, PR body, or model card before quoting accuracy. It flags:

untagged accuracy numbers (must be MEASURED / CLAIMED / SYNTHETIC),
MEASURED claims with no reproducer cited,
the retracted "100%/perfect accuracy" framing.

Firmware-specific

A firmware fix is not "hardware-validated" without a captured boot log on real silicon (e.g. the v0.8.1-esp32 rev-v0.2 validation: running headless so CSI captures (#1000) + CSI filter upgraded to MGMT+DATA + a no-false-detect mmwave probe). Do not merge or release on a build-passes signal alone.

Source: ruvnet/RuView → harness/ruview/.claude/skills/verify/SKILL.md

Frequently asked questions