research-record-audit

Adversarially verify research records against cited sources by re-deriving claims and re-running measurements.

2|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Arasz/ai-badger --skill research-record-audit-arasz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-record-audit
Source: https://github.com/Arasz/ai-badger/tree/main/features/common/skills/research-record-audit
Command: npx skills add https://github.com/Arasz/ai-badger --skill research-record-audit-arasz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Written research records, findings documents, and incident reports often contain claims that drift from their cited sources: quotes get paraphrased, aggregate numbers go stale, grades like MEASURED or INFERRED get misapplied, and absence claims ignore retention policies. This Skill audits a record adversarially so factual errors and overclaims are caught before the document ships. ## Core Features & Use Cases - Claim re-derivation: Extracts every finding's claim, grade, and citation, then verifies quotes verbatim at cited path:line locations and re-runs every MEASURED command. - Grade and honesty audit: Checks that MEASURED maps to a rerunnable command, INFERRED is hedged, UNVERIFIED is stated plainly, and open questions carry no unsupported parentheticals. - Call-site and negative-claim verification: Greps for callers to catch gated or dormant code paths, and rules out prune/retention explanations before accepting absence claims. - Use Case: Before approving a findings document that cites a SQLite state database and CLI help output, run this audit to produce a verdict of ACCURATE, CORRECTED, or OVERCLAIMED per finding with path:line evidence for every verdict. ## Quick Start Adversarially audit the research record at docs/work/findings.md for factual accuracy, citation truth, and grade correctness, and report a verdict per finding.

Frequently Asked Questions about research-record-audit

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

FAQPage Schema
How do I verify citations in a research document?

Verify citations by opening each cited file at the cited line and comparing quoted text word-for-word, allowing fair elisions but not changed wording. Then re-run any MEASURED claims with the exact command and check that every path:line range exists and contains the claimed content.

How to audit claims graded as measured or inferred?

Audit grades by requiring MEASURED claims to map to a command you actually reran, INFERRED claims to be explicitly labeled and hedged as reasoning, and UNVERIFIED claims to be stated plainly. Never let a guess be promoted to a measured result.

Can I query a SQLite database read-only for fact checking?

Yes, open SQLite read-only with sqlite3.connect('file:path?mode=ro', uri=True) so the audit never mutates the database. Batch all SELECTs for a finding into one script so each query is attributable in the report, and use PRAGMA table_info for schema claims.

Why do absence claims fail during document audits?

Absence claims fail when the auditor does not rule out explanations like prune policies, retention windows, or auto-delete before concluding something never existed. Chain the evidence, such as checking auto_prune settings and archived row counts, rather than asserting from one empty query.

What are the limitations of auditing time-varying measurements?

Time-varying numbers like session counts and token totals drift between runs, so a mismatch is not automatically an error. Check whether the record hedged appropriately, and if a number cannot be reproduced, report it as unverified rather than fabricating confirmation.