agentleFS
acprkacprk/crypto-research-agents/skills/textbook-index/SKILL.md

textbook-index

Skill15 starsChanged 9 days agoMITView on GitHub

Build and query a table-of-contents index of math and crypto textbooks to answer "which book and chapter proves X?". Use when a proof needs a standard lemma, when idea mining needs an external mathematical structure, or when adding books to references/textbooks.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No usable bookmarks → parses the printed "Contents" pages (txt, printed page numbers).

    line 17
  2. Very specific:

    If the statement is load-bearing, hand it to theorist for a Sage/Lean check.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

textbook-index

Build / extend the index

python3 skills/textbook-index/scripts/extract_toc.py <book-or-dir> ... \
        --out-dir references/textbooks/toc --summary /tmp/toc.json [--max-level 2]
python3 skills/textbook-index/scripts/extract_toc.py --selftest
  • PDF with bookmarks → bm (pages = physical PDF pages).
  • No usable bookmarks → parses the printed "Contents" pages (txt, printed page numbers); rejects OCR garbage using a dictionary hit-rate check (needs /usr/share/dict/words; otherwise accepts with a warning).
  • Scanned (no text layer), DjVu without djvused, or noisy OCR → stub; fill a chapter-level TOC from the publisher's public page and label it TOC from public source.
  • Output contains only bibliographic data + TOC; never commit PDFs or body text. Then add a row to references/textbooks/CATALOG.md and, if it fills a gap, to TOPIC-MAP.md.

Query ("which book/chapter proves X?")

  1. TOPIC-MAP.md row for the topic → first look / second opinion.
  2. grep -ril "<term>" references/textbooks/toc/ for terms the map lacks; beware homonyms (Frobenius norm vs Frobenius automorphism vs Frobenius group; "character" of a group vs of a field; "lattice" of subgroups vs Euclidean lattice; "trace" of a matrix vs field trace).
  3. Open your own copy at the section; copy the exact statement, and check each hypothesis against your setting (characteristic, ring vs field, finite vs infinite group, prime vs prime power modulus, Galois vs non-Galois extension). Most mis-citations fail here, not at the conclusion.
  4. Record in MATH-REFS.md: | id | statement we use | source (book, section, printed page) | hypotheses checked? | used in |.
  5. If the statement is load-bearing, hand it to theorist for a Sage/Lean check.

Ignition pattern for idea mining

"Book B chapter C + concrete bottleneck step S": ask what structure in C acts on the objects of S (a group action, a grading, a decomposition, a norm, an extremal bound). This pairing, not "give me ideas", is what produces candidate free parameters for idea-mining-loop.

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.