AI4Math-Paper-Reading / paper-to-skill
CLAUDE.md6 starsChanged 4 months agoMITView on GitHub
This repository is a coding-agent-neutral AI4Math paper-to-skill workflow. Claude Code should use the shared Skill layer under skills/; do not create a Claude-specific workflow fork.
In this repository7 other files it gives its agents.
- skills/paper-to-skill/AGENTS.mdAGENTS.md
- skills/paper-to-skill/.github/copilot-instructions.mdCopilot instructions
- ai4math-paper-readingSkill
- after-ocrSkill
- graph-theory-paper-readingSkill
- math-paper-readingSkill
- paper-to-skillSkill
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Read skills/registry.yaml for phase routing, input/output contracts, and review gates.
- Very specific: line 11
Use SKILL.md only as the top-level compatibility entrypoint.
- Distinctive: line 12
Follow AGENTS.md for the repository contract.
- Very specific: line 18
Every accepted or review-worthy SkillCard must include source.paper_md, source.start_line, and source.end_line.
- Very specific: line 19
Keep platform-specific behavior thin.
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CLAUDE.md
This repository is a coding-agent-neutral AI4Math paper-to-skill workflow.
Claude Code should use the shared Skill layer under skills/; do not create a Claude-specific workflow fork.
Entry Points
- Read
skills/registry.yamlfor phase routing, input/output contracts, and review gates. - For user-facing PDF or Markdown paper processing, prioritize
skills/paper-to-skill-workflow/SKILL.md. - Use
SKILL.mdonly as the top-level compatibility entrypoint. - Follow
AGENTS.mdfor the repository contract.
Operating Boundary
- Accept
paper.pdfas the default user input; acceptpaper.mdwhen conversion has already happened. - Preserve the original
paper.pdfwhen provided and the full convertedpaper.md. - Every accepted or review-worthy SkillCard must include
source.paper_md,source.start_line, andsource.end_line. - Keep platform-specific behavior thin; improve the shared
skills/layer first.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

