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

AI4Math-Paper-Reading / paper-to-skill

AGENTS.md6 starsChanged 4 months agoMITView on GitHub

This repository implements a coding-agent-assisted paper-to-skill workflow for an AI4Math skill library. Codex is the reference operator for this repository, but the Skill layer should remain usable by other coding agents such as Claude Code, Gemini, OpenCode, Cursor, and similar agentic development tools. The goal is not to summarize papers, but to extract reusable mathematical research skills from papers. Prioritize the user-facing workflow Skill at skills/paper-to-skill-workflow. The default user input is paper.pdf. If the user provides paper.md, skip conversion and…

The file

We split this AGENTS.md into the rules it gives an agent

9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep PDF conversion, extraction, retrieval, synthesis, and future automation as separate Skills rather than folding every responsibility …

    line 19
  2. Very specific:

    Always preserve the original paper.pdf when provided and the full converted paper.md.

    line 23
  3. Very specific:

    Every extracted skill must include source line references back to paper.md.

    line 25
  4. Very specific:

    Keep platform-specific adapter files thin and point them back to skills/registry.yaml and the shared skills/ layer.

    line 30
  5. Distinctive:

    Keep required YAML fields and templates explicit.

    line 31
  6. Distinctive:

    Keep future Python automation compatible with the Skill workflow.

    line 32
  7. Distinctive:

    Use direct mathematical checks and existing validation commands.

    line 33
  8. Distinctive:

    Do not silently drop source text.

    line 34
  9. Distinctive:

    Prefer small composable modules and deterministic output formats.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.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
AGENTS.md

AGENTS.md

Project Goal

This repository implements a coding-agent-assisted paper-to-skill workflow for an AI4Math skill library.

Codex is the reference operator for this repository, but the Skill layer should remain usable by other coding agents such as Claude Code, Gemini, OpenCode, Cursor, and similar agentic development tools.

The goal is not to summarize papers, but to extract reusable mathematical research skills from papers.

Current Scope

Prioritize the user-facing workflow Skill at skills/paper-to-skill-workflow.

The default user input is paper.pdf. If the user provides paper.md, skip conversion and extract directly.

The active coding agent is the extraction engine. The workflow should not require external LLM APIs.

Keep PDF conversion, extraction, retrieval, synthesis, and future automation as separate Skills rather than folding every responsibility into one file.

Source of Truth

Always preserve the original paper.pdf when provided and the full converted paper.md. Structured files are weak indexes, reports, or generated artifacts, not replacements for the original paper.

Every extracted skill must include source line references back to paper.md.

Engineering Rules

  • Encode the extraction workflow as a portable Skill first.
  • Keep platform-specific adapter files thin and point them back to skills/registry.yaml and the shared skills/ layer.
  • Keep required YAML fields and templates explicit.
  • Keep future Python automation compatible with the Skill workflow.
  • Use direct mathematical checks and existing validation commands; do not add a schema framework or test dependencies.
  • Do not silently drop source text.
  • Prefer small composable modules and deterministic output formats.

Done Means

A task is done only when:

  • the portable Skill workflow is written or updated;
  • a PDF paper can be processed end-to-end into Markdown, SkillCandidates, SkillCards, and a report;
  • generated outputs match the expected schema;
  • extracted skills include source evidence and review status.

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.