lo2cin4bt Acceptance Review
lo2cin4/lo2cin4bt
Runs a pass, revise or block acceptance review on lo2cin4bt work, checking a deliverable against the request, repo contracts, tests, docs and the public GitHub boundary.
Proves a RuView result is real by running a deterministic SHA-256 proof and a witness bundle, and by checking reports for untagged or unreproducible accuracy claims.
Install RuView Result Verification
$ npx skills add ruvnet/RuView --skill verify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ruvnet/RuView verify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ruvnet/RuView.git skills-src && mkdir -p .claude/skills && cp -r skills-src/harness/ruview/.claude/skills/verify .claude/skills/verify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verify" agent skill from https://github.com/ruvnet/RuView/tree/main/harness/ruview/.claude/skills/verify into .claude/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ruvnet/RuView/tree/main/harness/ruview/.claude/skills/verifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ruvnet/RuView --skill verify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ruvnet/RuView verify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/RuView.git skills-src && mkdir -p .agents/skills && cp -r skills-src/harness/ruview/.claude/skills/verify .agents/skills/verify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify" agent skill from https://github.com/ruvnet/RuView/tree/main/harness/ruview/.claude/skills/verify into .agents/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruvnet/RuView --skill verify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ruvnet/RuView verify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/RuView.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/harness/ruview/.claude/skills/verify .cursor/skills/verify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verify" agent skill from https://github.com/ruvnet/RuView/tree/main/harness/ruview/.claude/skills/verify into .cursor/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ruvnet/RuView.git --path harness/ruview/.claude/skills/verify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ruvnet/RuView --skill verify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ruvnet/RuView verify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/RuView.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/harness/ruview/.claude/skills/verify .gemini/skills/verify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/ruvnet/RuView/tree/main/harness/ruview/.claude/skills/verify into .gemini/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ruvnet/RuView verifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ruvnet/RuView --skill verify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ruvnet/RuView.git skills-src && mkdir -p .github/skills && cp -r skills-src/harness/ruview/.claude/skills/verify .github/skills/verify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/ruvnet/RuView/tree/main/harness/ruview/.claude/skills/verify into .github/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ruvnet/RuView --skill verify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ruvnet/RuView verify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ruvnet/RuView.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/harness/ruview/.claude/skills/verify .opencode/skills/verify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verify" agent skill from https://github.com/ruvnet/RuView/tree/main/harness/ruview/.claude/skills/verify into .opencode/skills/verify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verify- GitHub stars
- 97k
- Token cost
- ~395 tokens
- SKILL.md length
- 162 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- MIT
At a glance
Proves a RuView result is real by running a deterministic SHA-256 proof and a witness bundle, and by checking reports for untagged or unreproducible accuracy claims.
- Confirming a RuView pipeline change still reproduces the expected output hash
- SKILL.md covers Deterministic proof (Trust…, Witness bundle (ADR-028), Claim honesty and Firmware-specific
- Calls bash
- Producing a witness bundle that a recipient can re-verify with one command
What it does
The skill acts as a gate for the RuView project: nothing counts as validated without it. ruview_verify runs a Python verify script that feeds a reference signal through the production pipeline and compares the hash of the output with a stored expected-features hash, and the run must print VERDICT: PASS. If a numpy or scipy change alters the hash, the script is rerun with --generate-hash and then verified again.
For release-grade attestation, a script builds a witness bundle (ADR-028) holding the Rust test log, the proof and expected hash, a firmware SHA-256 manifest and crate versions, and its VERIFY.sh must report 7/7 PASS. ruview_claim_check scans reports, README sections, PR bodies and model cards and flags accuracy numbers not tagged as measured, claimed or synthetic, measured claims without a reproducer, and the retracted perfect-accuracy framing. A firmware fix counts as hardware-validated only with a boot log captured on real silicon.
When your agent uses it
- Confirming a RuView pipeline change still reproduces the expected output hash
- Producing a witness bundle that a recipient can re-verify with one command
- Checking a report or PR description for unsupported accuracy claims
- Deciding whether a firmware fix is validated enough to merge or release
Example prompts
- “Run the deterministic proof and tell me whether it prints PASS.”
- “Generate the witness bundle for this release and run its VERIFY script.”
- “Check the README accuracy section for claims that are not tagged as measured or claimed.”
Requirements
- A RuView checkout with the proof script and expected hash
- Python with numpy and scipy
What it can do on your machine
Read from SKILL.md and the folder at commit 0ef6b96. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
RuView Result Verification loads about 395 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 162 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ruvnet/RuView at commit 0ef6b96, republished under its MIT licence (© ruvnet). 162 words, ~395 tokens.
Download SKILL.mdSave it as
.claude/skills/verify/SKILL.md (or your agent's skills folder).- name
- verify
- description
- 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.
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 PASSContains 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.
© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in harness/ruview/.claude/skills/verify of ruvnet/RuView.
Open the folder on GitHubat commit 0ef6b96
Compare with similar skills
RuView Result Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| RuView Result Verification this skillruvnet/RuView | 97k | — | ~395 | Automated safety check: Pass | MIT | |
| lo2cin4bt Acceptance Reviewlo2cin4/lo2cin4bt | 288 | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Codewhale Verification Laddercodewhale-hq/Codewhale | 41k | — | ~1.4k | Automated safety check: Pass | MIT | |
| TUI Change Verification for Warpwarpdotdev/warp | 65k | 1 repos | ~5.5k | Automated safety check: Notes | AGPL-3.0 | |
| Codewhale Dogfood Installcodewhale-hq/Codewhale | 41k | — | ~1.3k | Automated safety check: Pass | MIT | |
| TiDB Verification Profilespingcap/tidb | 41k | — | ~496 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Codewhale Verification Ladder
codewhale-hq/Codewhale
Climbs a focused-to-broad set of verification rungs, from formatting checks to budget scripts CI enforces, so a Codewhale change is called done only with quoted command output behind it.
TUI Change Verification for Warp
warpdotdev/warp
Runs Warp's terminal UI for real, drives it with keystrokes and reads the rendered screen back to confirm that a change looks and behaves as intended.
Codewhale Dogfood Install
codewhale-hq/Codewhale
Proves a Codewhale change in the real product: a stamped release build, an atomic local install, fresh-shell verification and manual QA that automated gates cannot cover.
TiDB Verification Profiles
pingcap/tidb
Chooses how much validation a TiDB change needs: scoped checks while iterating, required checks at delivery, and expensive runs only when explicitly needed.
Hydra Dev
streamband/hydra-srt
Run HydraSRT development workflows: mix q quality gate, Elixir unit/E2E tests, native Rust tests, web Vitest/Playwright, and make dev.
More from ruvnet/RuView
All 24 skills in this repoRuView Advanced Sensing
ruvnet/RuView
Reference for RuView's research-grade WiFi sensing features: multistatic fusion, cross-viewpoint geometry, persistent field models, RF tomography, intention signals and mesh security.
RuView Sensing Applications
ruvnet/RuView
Runs RuView's WiFi sensing applications: presence, vital signs, activity and fall detection, pose estimation, sleep monitoring and environment mapping.
RuView CLI, API and WASM
ruvnet/RuView
Covers the RuView `wifi-densepose` command line binary, its Axum REST API and the WebAssembly builds for browsers and ESP32, for embedding or scripting RuView.
RuView Deployment Configuration
ruvnet/RuView
Tunes a deployed RuView WiFi-sensing system without changing code: firmware sdkconfig variants, NVS provisioning over serial, channel and MAC filtering, edge processing tiers and mesh slotting.
Agent-Browser Automation
ruvnet/RuView
Drives a web browser through the agent-browser CLI, using compact accessibility snapshots with element refs in place of the full DOM to keep context small.
RuView Hardware Setup
ruvnet/RuView
Brings a RuView CSI sensing node online by building ESP32-S3 or ESP32-C6 firmware, flashing the board, provisioning WiFi and checking the serial output.
Related
Categories
Questions about RuView Result Verification
What does RuView Result Verification do?
Proves a RuView result is real by running a deterministic SHA-256 proof and a witness bundle, and by checking reports for untagged or unreproducible accuracy claims. The skill acts as a gate for the RuView project: nothing counts as validated without it. ruview_verify runs a Python verify script that feeds a reference signal through the production pipeline and compares the hash of the output with a stored expected-features hash, and the run must print VERDICT: PASS.
When should I use RuView Result Verification?
RuView Result Verification fits situations like: confirming a RuView pipeline change still reproduces the expected output hash; producing a witness bundle that a recipient can re-verify with one command; checking a report or PR description for unsupported accuracy claims; deciding whether a firmware fix is validated enough to merge or release.
How do I install RuView Result Verification in Claude Code?
Run `npx skills add ruvnet/RuView --skill verify -a claude-code`. Or copy the skill folder (harness/ruview/.claude/skills/verify in ruvnet/RuView) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.
How do I install RuView Result Verification in Codex?
Run `npx skills add ruvnet/RuView --skill verify -a codex`. Or copy the skill folder (harness/ruview/.claude/skills/verify in ruvnet/RuView) into .agents/skills/verify in your project. Codex loads it when a task matches its description.
Can I use RuView Result Verification in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/RuView --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.
What does RuView Result Verification need to run?
Going by SKILL.md and its folder, RuView Result Verification needs the command-line tools its instructions call (bash). Our summary lists: A RuView checkout with the proof script and expected hash; Python with numpy and scipy.
Does RuView Result Verification access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is RuView Result Verification safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does RuView Result Verification use?
RuView Result Verification is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does RuView Result Verification use?
About 395 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to RuView Result Verification?
Skills that share tags, products or a category with RuView Result Verification: lo2cin4bt Acceptance Review (lo2cin4/lo2cin4bt, 288 stars), Codewhale Verification Ladder (codewhale-hq/Codewhale, 41k stars), TUI Change Verification for Warp (warpdotdev/warp, 65k stars) and Codewhale Dogfood Install (codewhale-hq/Codewhale, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains RuView Result Verification?
ruvnet (a GitHub user) maintains it in ruvnet/RuView, which has 96,741 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 7, 2026.
Source: ruvnet/RuView on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.