stage-clms-auditor

Audits every manuscript number against fingerprinted evidence files and updates the claim ledger.

2|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/wanghao9610/STAGE --skill stage-clms-auditor-wanghao9610
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stage-clms-auditor
Source: https://github.com/wanghao9610/STAGE/tree/main/.qwen/skills/stage-clms-auditor
Command: npx skills add https://github.com/wanghao9610/STAGE --skill stage-clms-auditor-wanghao9610

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Academic manuscripts accumulate numbers that may drift from their underlying experimental evidence, leaving claims unsourced or mismatched before submission. This Skill mechanically traces every number in LaTeX sections and tables back to fingerprinted evidence files, assigning a verdict of matched, mismatched, or unsourced so no unsupported figure survives to submission. ## Core Features & Use Cases - Per-number trace and verdict: Extracts every numeric token from manus/secs/ and manus/tabs/, follows % src: comments and claim-ledger evidence links to fingerprinted mates/ entries, and assigns matched, mismatched, or unsourced verdicts. - Claim ledger management: Flips notes/claims.md statuses between drafted, verified, and unsourced based on audit results, and files one tasks/ item per failure routed to the owning skill. - Staleness detection: Runs import.sh --diff to detect drifted upstream evidence, tainting matches made against stale sources and blocking verification flips. - Use Case: Before a submission freeze, run the auditor over the full manuscript to confirm every reported result traces to fingerprinted evidence, receive a CLAIMS_<date>.md report, and get a task list of every number needing a fix. ## Quick Start Ask the AI to run stage-clms-auditor on the whole manuscript, or pass a section name or claim ID such as C7 to audit only that scope.

Frequently Asked Questions about stage-clms-auditor

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

FAQPage Schema
How do I verify that numbers in my LaTeX paper match experimental results?

Run the claims auditor over manus/secs/ and manus/tabs/. It extracts every numeric token, follows % src: comments and ledger evidence links to fingerprinted files under mates/, and reports each number as matched, mismatched, or unsourced.

How do I audit a single section or claim instead of the whole manuscript?

Pass a section name to audit that section's file plus every table it inputs or references, or pass a claim ID like C7 to audit that claim everywhere its Stated in field reaches. No argument audits all sections and tables.

What happens when evidence files have drifted from the upstream source?

The auditor runs import.sh --diff as a staleness gate before tracing. Drifted evidence taints every match made against it: those numbers are reported as matched-but-stale, a re-import task is filed, and affected claims are not flipped to verified.

Does the claims auditor fix mismatched numbers in the manuscript?

No. It never edits the manuscript, the evidence directory, or the bibliography. Every failure becomes a task routed to the owning skill: drafting skills fix prose and tables, and wrong upstream numbers are fixed in STAR and re-imported.

What is the difference between the claims audit and the citation audit?

Numbers attributed to a cited work via a \cite command are assertions about that work and are handed off to the citation auditor for checking against reading notes. All other numbers, including table rows whose % src: points at imported evidence, belong to the claims audit.