Individual skill
proof-derivation-forensics
Family-G proof & derivation integrity forensics: does a THIRD PARTY's written proof/derivation actually establish its theorem, or does it skip an obligation, assume its own conclusion, take an invalid step, drift a symbol's meaning, or smuggle an unstated assumption? Decides from the WRITTEN proof/derivation — verdict-bearing at L1 (the LaTeX source; PDF-extracted math is unreliable, so an L0 PDF-only run surfaces info only) — never asserts 'fabricated', only that the step shown does not hold. A fresh cross-model reviewer reads the theorem/proof + an extraction-only obligation scaffold and proposes per-obligation findings, each span-anchored to the evidence ledger (claims.json); reviewer≠adjudicator. Emits proof-derivation-forensics.findings.json; NEVER computes the verdict. dimension=proof, can be critical. Triggers: "proof forensics", "check this proof", "derivation integrity", "audit the math", "证明审计", "推导有没有漏洞".
skills/proof-derivation-forensics/SKILL.md
Source commit 014a1e7cd63f1656603daaeeadb856aed1df6869
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 180
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-generated-content Repository topic
- ai-scientist Repository topic
- autoresearch Repository topic
- forensics Repository topic
- llm-agents Repository topic
- peer-review Repository topic
- research-integrity Repository topic
- ai-research Repository topic
- aris Repository topic
- claude Repository topic
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytesSKILL.mdcore · 54,047 bytes
Read excerpt
# Proof & Derivation Forensics — does the written proof hold?
Audit family **G (proof & derivation integrity)** for: **$ARGUMENTS** (requires
`claims.json` from `/evidence-ledger`). A fresh cross-model reviewer reads each
theorem/proof and proposes span-anchored findings; this skill writes
`proof-derivation-forensics.findings.json`. The deterministic adjudicator — not this
skill — computes the verdict.
> 🔒 **Do not wrap this skill in `/loop`, `/schedule`, or `CronCreate`.** It is
> verdict-bearing input — it proposes the findings the deterministic adjudicator
> turns into the report. Re-firing it on a wall-clock timer adds no signal: its
> output changes only when the **paper / ledger** changes, not with the clock.
> Schedule the *external wait that precedes it* — ledger built → audit **once**.
> (Mirrors ARIS's external-cadence doctrine.)