agentleFS
youcislayoucisla/Agent-Foundry/skills/optional/book-to-skill/SKILL.md

book-to-skill

Skill1 starsChanged 23 days agoMITView on GitHub

Turn a book, PDF, or long article into a skill draft with reference chapters and a glossary. Use when converting long-form source material into a reviewable draft rather than a finished skill.

  • Installs packages

20 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Add frontmatter: license, author, status: draft, source: local.

    line 55
  2. Distinctive:

    Add at least two anti-patterns and at least two verification checks.

    line 57

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “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

Book to Skill

Extracts a long document into chapter references, a glossary skeleton, and a minimal SKILL.md. The output is a draft. A human writes the procedure and passes the quality gates.

Procedure

What ships

skills/optional/book-to-skill/scripts/book_to_skill.py.

PDF input requires pypdf (pip install pypdf). Markdown, text, and URLs use the standard library. URL input fetches the document once.

Usage

python skills/optional/book-to-skill/scripts/book_to_skill.py \
  --input=book.pdf --skill-name=my-book --output-dir=plans/skills/drafts/my-book
python skills/optional/book-to-skill/scripts/book_to_skill.py \
  --input=chapter.md --output-dir=plans/skills/drafts/my-chapter

There is no extract subcommand: pass the flags directly. Drafts belong under the gitignored plans/skills/drafts/ tree. The script does not enforce the destination, so choose it deliberately; never point it at skills/.

What it actually produces

  • Up to 30 sections, split on Markdown H1/H2 headings or PDF page headings
  • references/ch-NN-<slug>.md for each section
  • assets/glossary.json with bolded capitalized terms (definitions empty)
  • assets/summary.json with section and term counts
  • A minimal SKILL.md containing an outline, key concepts, and reference links

It does not generate 3-7 instructions per chapter, does not validate the draft, and does not add license, author, status, or source metadata.

Human completion pass

  1. Add frontmatter: license, author, status: draft, source: local.
  2. State one trigger sentence, then a procedure with verifiable steps.
  3. Add at least two anti-patterns and at least two verification checks.
  4. Run ./.venv/Scripts/python.exe scripts/foundry-eval.py --target <draft>/SKILL.md.
  5. Promote only after the evaluator passes and a human reviews the draft.

Anti-patterns

  • Copying chapter text verbatim instead of distilling procedures.
  • Shipping the generated shell as a finished skill.
  • Converting copyrighted material without checking the license.
  • Placing drafts in skills/, where discovery and packaging will pick them up.

Verification Checklist

  • Every reference chapter is present and non-empty.
  • The glossary is reviewed and definitions are filled in or removed.
  • The draft has a single trigger, procedure, anti-patterns, and checks.
  • foundry-eval passes before the draft leaves plans/.

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.