agentleFS
VeryMathVeryMath/AI4Math-Paper-Reading/skills/paper-to-skill/CLAUDE.md

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.

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
  1. Very specific:

    Read skills/registry.yaml for phase routing, input/output contracts, and review gates.

    line 9
  2. Very specific:

    Use SKILL.md only as the top-level compatibility entrypoint.

    line 11
  3. Distinctive:

    Follow AGENTS.md for the repository contract.

    line 12
  4. Very specific:

    Every accepted or review-worthy SkillCard must include source.paper_md, source.start_line, and source.end_line.

    line 18
  5. Very specific:

    Keep platform-specific behavior thin.

    line 19

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

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.yaml for 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.md only as the top-level compatibility entrypoint.
  • Follow AGENTS.md for the repository contract.

Operating Boundary

  • Accept paper.pdf as the default user input; accept paper.md when conversion has already happened.
  • Preserve the original paper.pdf when provided and the full converted paper.md.
  • Every accepted or review-worthy SkillCard must include source.paper_md, source.start_line, and source.end_line.
  • Keep platform-specific behavior thin; improve the shared skills/ layer first.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.