proof-material

Store source-indexed proof material with stable identifiers and citations.

2|1|Updated May 7, 2026
One-click install
npx skills add https://github.com/shenmuxing/EtaSkill --skill proof-material
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof-material
Source: https://github.com/shenmuxing/EtaSkill/tree/main/skill-examples/proof-material
Command: npx skills add https://github.com/shenmuxing/EtaSkill --skill proof-material

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you store and inspect source-indexed proof material so later agents can reuse ideas without losing the original paper location, stable ID, or citation trail.

Core Features & Use Cases

  • Source-Indexed Library: Organizes one public source per file with a global index for fast lookup.
  • Stable Material IDs: Preserves reusable IDs, tags, dependencies, and proof skeletons across updates.
  • Proof Pipeline Support: Bridges extraction and synthesis by feeding material from proof-finder into proof-cooker.
  • Use Case: When you extract lemmas from a paper, use this Skill to keep them tied to the exact section, theorem, or equation they came from.

Quick Start

Use the proof-material skill to add a new public source entry with stable IDs, source locations, and reusable abstractions.

Frequently Asked Questions about proof-material

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

FAQPage Schema
How do I organize extracted lemmas and proofs from research papers for later reuse?

Organize extracted proofs by storing one public source per file with a global index, stable material IDs, and traceable paper citations. This structured library ties each extracted lemma to its exact section or theorem location for later lookup.

What is source-indexed proof material and when do I need it in a research workflow?

Source-indexed proof material is a structured library of reusable lemmas, strategies, and definitions extracted from public PDFs. You need it when your research workflow requires preserving the original paper location, stable IDs, and citation trail for future synthesis.

How do I maintain a citation trail when extracting definitions and dependencies from public PDFs?

Maintain a citation trail by assigning stable identifiers to each extracted definition or dependency and linking them to their precise source locations within the public PDF. One source file per public source preserves this traceable evidence across updates.

Can I reuse proof skeletons across updates without losing the original paper locations?

Yes, you can preserve reusable proof skeletons across updates by maintaining a global index with stable material IDs, tags, and dependencies. This approach ensures the original paper locations and citation trails remain intact for later agents.

Does this proof material storage approach work for bridging extraction and synthesis pipelines?

Yes, this approach bridges extraction and synthesis pipelines by feeding structured material from proof-finder into proof-cooker. It stores concise proof skeletons that preserve evidence without exposing private logs, ensuring clean downstream reuse.

What are the limitations of storing proof material with stable identifiers for research workflows?

This storage approach requires maintaining a global index and one source file per public source, limiting its use to public PDFs. It does not expose private logs and focuses strictly on preserving concise proof skeletons with traceable evidence.