synthesize-verificatio…
Aggregate all detected errors and gaps into the final verification report, apply strict…
Validate externally referenced theorems by querying arXiv theorem search first and Codex's built-in web search second. Use when a markdown proof cites statements from external papers.
$ npx -y skills add frenzymath/Danus --skill check-referenced-statements --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/check-referenced-statementsContext preview
The summary Claude sees to decide when to auto-load this skill.
Validate externally referenced theorems by querying arXiv theorem search first and Codex's built-in web search second. Use when a markdown proof cites statements from external papers.
name: check-referenced-statements description: Validate externally referenced theorems by querying arXiv theorem search first and Codex's built-in web search second. Use when a markdown proof cites statements from external papers.
Validate every external-paper reference used in the proof.
For each cited external theorem/lemma/definition:
1. Query `search_arxiv_theorems` using the full referenced statement as `query`. 2. Inspect returned results and compare theorem text directly to the referenced statement in reasoning. 3. Expand the definitions and terminology appearing in the cited statement using the cited paper's context before deciding whether the theorem applies. 4. Check whether the same words in the current proof mean the same thing as they do in the cited paper. In mathematics, identical words can carry different definitions in different contexts. Distinguish similar-looking definitions: compare their exact formulas, notation, and quantifiers; do not collapse two just because the names or formulas look close. 5. Accept as matched and applicable only when both are true:
6. If the theorem exists but the current proof uses different definitions, hypotheses, ambient objects, or a subtly different defining formula, record a critical error for incorrect application. 7. If the proof uses the cited statement to derive further conclusions, verify that transition too: a hand-wavy specialization or instantiation is a `gap`; a logically invalid transition is a `critical_error`; if it deduces one property from another, compare their exact defining formulas before accepting. 8. If no match is found, use Codex's built-in web search with the same statement text. 9. If still not found, emit a critical error:
10. When a step cites an internal `fact_id` (16 hex characters) rather than an external paper, apply the verifier contract's P3-supplement **chain check** (`agents/contracts/verifier.md`): read the cited fact from the project fact graph and, if its own statement carries an unproven conditional premise, record the inherited defect as a `critical_error`. Read and apply the wording from the contract; do not fork it here. 11. Keep each reference check in context for the synthesis step (you persist nothing — the verifier is stateless).
Do not rely on dedicated comparison utility code; perform comparison through careful reasoning.
Produce one record per reference check, kept in context for synthesis:
{
"location": "Lemma 2",
"referenced_statement": "Exact statement text",
"context_expansion": "In the cited paper, 'regular' means regular with respect to the valuation topology.",
"arxiv_match_found": false,
"web_match_found": false,
"critical_error": {
"location": "Lemma 2",
"issue": "Referenced external theorem was not found in arXiv search or Codex built-in web search."
}
}(Findings stay in context for synthesis — nothing is persisted.)
🚀✨ News: This branch is the version that solved YTD. 🎉 Danus orchestrates mathematical reasoning agents with fact-graph memory.
Aggregate all detected errors and gaps into the final verification report, apply strict…
Verify a markdown proof in the order it is written. Use when the task is to check local…
Construct candidate counterexamples to test a proposed conjecture, lemma, or intermediate…
Generate and analyze simpler examples that satisfy both the assumptions and the conclusion of…
Screen a decomposition plan by first trying to prove all of its subgoals directly, then…
Synthesize the common stuck points across failed decomposition plans. Use when the current…