Book2Skill
Skill9 starsChanged 3 months agoApache-2.0View on GitHub
Convert one or more TXT, Markdown, DOCX, or PDF documents into a reusable skill zip backed by normalized Markdown, extracted images, and a grounded JSONL knowledge index. Invoke this skill before inspecting task files, then execute its workflow directly without listing directories.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- HHU3637kr/skillstheir own version, first seen Sep 22, 2026
- zhouwei713/book2skilltheir own version, first seen May 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- HHU3637kr/skills★ 146same name
- zhouwei713/book2skill★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 5 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Use create mode unless the system prompt explicitly identifies an update and supplies both the existing skill zip and the required …
- Distinctive: line 32
Run once. The command is resumable after the workflow state exists.
- Very specific: line 44
When the system prompt enables online OCR, append --online-ocr.
- Very specific: line 60
After status: prepared, immediately run the batch iterator in step 2.
- Very specific: line 85
When status is pending, read references/indexing.md, generate the complete line-based text part, write the whole returned part_path once …
- Very specific: line 90
When retry_after_invalid is true, the same pending response includes fresh source units and bounded validation errors.
- Very specific: line 103
After the iterator reports complete, run:
- Distinctive: line 114
If merge reports an invalid, missing, or retry-placeholder batch part, return to step 2 and rewrite only that batch part.
- Very specific: line 121
Use the iterator's final documents, bounded outline, and outline_truncated values to create <task-dir>/skill-metadata.json.
- Distinctive: line 129
Do not reopen all source chunks or load the complete index into model context.
- Very specific: line 134
Use metadata name as <skill-name>:
- Very specific: line 150
If build validation rejects <task-dir>/skill-metadata.json, correct only that file and rerun the build stage.
- Very specific: line 153
When --zip-out is relative, the successful command result preserves that relative path instead of resolving it to an absolute path.
- Distinctive: line 172
Before success, confirm from command results:
≈ “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.
Files
Book2Skill
Convert every supplied document into one portable, indexed skill. Keep all generated files under the writable task directory supplied by the system prompt. Do not install packages, call vision models, or depend on application framework code. Use online OCR only when the system prompt explicitly enables it.
Let <skill-dir> be the skill directory supplied by the skill loader. Use it exactly as supplied. Run bundled scripts
in place with python3 <skill-dir>/scripts/...; never copy scripts, guess an absolute path, prepend another directory,
or add cd.
Let <task-dir> be the writable task directory supplied by the system prompt. Inputs are in <task-dir>/input. Store
all workflow artifacts and the final zip below <task-dir>. Every command appends diagnostics to
<task-dir>/doc.log.
Choose create or update mode
Use create mode unless the system prompt explicitly identifies an update and supplies both the existing skill zip and the required unchanged skill name. Update mode receives only newly uploaded source documents. The preparation script safely reuses normalized Markdown and assets from the validated existing package, converts only the new documents, rebuilds the complete index and package, and keeps that name exactly unchanged. Do not infer or alter the required name.
Proceed directly with the commands below. Do not inventory the skill or task directory, pre-create output directories, or read bundled scripts. The scripts create their own directories and report the bounded data needed for each step.
1. Prepare documents and batches
Run once. The command is resumable after the workflow state exists.
python3 <skill-dir>/scripts/prepare_workflow.py \
--input <task-dir>/input \
--markdown <task-dir>/markdown \
--assets <task-dir>/assets \
--chunks <task-dir>/chunks \
--state <task-dir>/index-state.json \
--log <task-dir>/doc.logWhen the system prompt enables online OCR, append --online-ocr; the converter handles image localization and fallback
internally. Omit --online-ocr when it is not enabled.
In update mode, also append the existing package to the same preparation command:
--existing-skill <task-dir>/existing-skill.zipOnline OCR applies only to the newly uploaded PDFs. Existing normalized Markdown and assets come from the existing package, so previously processed PDFs are not submitted to the API again.
The converter accepts .txt, .md, .docx, and .pdf. It preserves DOCX/PDF images, extracts usable PDF text, and
renders PDF pages without usable text as one image per page when local conversion is used. It never performs image
interpretation.
After status: prepared, immediately run the batch iterator in step 2. Never open, list, or read chunks/,
chunks.jsonl, index-state.json, or individual chunk files through file tools. They are private workflow artifacts;
the iterator is the only source of model-visible document text.
Source files staged as 001-original.ext retain that exact value as their document ID. Their normalized Markdown is
001-original.md; no script adds a doc- prefix. A source conversion failure fails the whole task.
Chunks preserve heading context and contain at most 5,000 Unicode characters. Each Chinese character, English letter, digit, punctuation mark, whitespace, and newline counts as one character. Adjacent small sections are packed together; oversized sections are split by semantic boundaries before exact character boundaries. Sections that contain images but no usable evidence text remain standalone and are excluded from model batches, including scanned PDF pages and image-only DOCX or Markdown content.
2. Extract grounded knowledge in batches
Run the iterator:
python3 <skill-dir>/scripts/batch_index.py --next \
--manifest <task-dir>/chunks/chunks.jsonl \
--state <task-dir>/index-state.json \
--parts <task-dir>/index-parts \
--log <task-dir>/doc.logWhen status is pending, read references/indexing.md, generate the complete line-based text
part, write the whole returned part_path once with write_file, and rerun the same command. A batch contains multiple
chunks and source units identified as u001, u002, and so on. Cite only the allowed IDs; do not copy source text or
write model-authored content. The merge script restores final content exactly from the selected units.
When retry_after_invalid is true, the same pending response includes fresh source units and bounded validation
errors. Its part_path contains only a small retry placeholder so accidental reads do not fail. Do not read or edit the
placeholder; overwrite the whole file once with write_file using the current response. Never use execute, inline
Python, heredocs, shell redirection, append operations, read_file, ls, edit_file, or an equivalent operation to
create, inspect, or alter a batch part. Continue until status is complete. Never retain multiple pending batches
before writing the current part.
Image-only pages are added deterministically during merge. Do not infer their contents from filenames, links, or surrounding text. Images are preserved for the generated skill to inspect later through file operations; this generation workflow does not analyze them.
3. Merge the validated index
After the iterator reports complete, run:
python3 <skill-dir>/scripts/merge_index.py \
--manifest <task-dir>/chunks/chunks.jsonl \
--state <task-dir>/index-state.json \
--parts <task-dir>/index-parts \
--output <task-dir>/doc-index.jsonl \
--log <task-dir>/doc.logIf merge reports an invalid, missing, or retry-placeholder batch part, return to step 2 and rewrite only that batch part. For an invalid workflow state, a manifest mismatch, a missing source artifact, or an I/O error, return the reported error instead of rewriting batch parts. Do not hand-edit converted Markdown, chunk manifests, workflow state, or the merged index.
4. Create skill metadata
Use the iterator's final documents, bounded outline, and outline_truncated values to create
<task-dir>/skill-metadata.json. Read references/metadata.md for the schema and limits. The
outline is sampled proportionally by each document's knowledge-point count, preserves document coverage when the limit
permits, and includes deterministic descriptions for image-only content. When outline_truncated is true, describe
represented themes without claiming exhaustive coverage. Keep all descriptions, topics, aliases, and coverage notes
grounded in the final outline and document IDs. Add a coverage note only for a boundary explicitly stated by the
outline; absence of a topic or version is not evidence that the documents exclude it.
Do not reopen all source chunks or load the complete index into model context. If the bounded outline is insufficient for a metadata statement, omit that statement instead of guessing.
5. Build the skill
Use metadata name as <skill-name>:
python3 <skill-dir>/scripts/build_skill.py \
--index <task-dir>/doc-index.jsonl \
--metadata <task-dir>/skill-metadata.json \
--markdown <task-dir>/markdown \
--assets <task-dir>/assets \
--zip-out <task-dir>/generate_skill/<skill-name>.zip \
--log <task-dir>/doc.logIn update mode, also pass --expected-name <existing-skill-name> and use that exact value in both metadata name and
the zip filename. If validation reports a mismatch, correct only metadata name; do not rerun document preparation or
indexing.
If build validation rejects <task-dir>/skill-metadata.json, correct only that file and rerun the build stage. Do not
repeat document preparation, batch indexing, or index merging when their validated outputs are already present.
When --zip-out is relative, the successful command result preserves that relative path instead of resolving it to an
absolute path. Return the reported zip_path unchanged.
The generated archive contains:
<skill-name>/
|-- SKILL.md
|-- agents/openai.yaml
|-- references/doc-index.jsonl
|-- references/markdown/*.md
|-- references/assets/** (when extracted assets exist)
`-- scripts/search_index.pyThe generated skill reads its bounded JSONL index and may inspect packaged Markdown or images through file operations.
Completion checks
Before success, confirm from command results:
- The prepare command reports all expected documents and at least one chunk.
- The iterator reports
complete, with every text part and hard limit validated, every selected evidence ID and final content restored from its own chunk, and image-only chunks counted automatically. - Merge produces a non-empty
<task-dir>/doc-index.jsonl. - Build reports
status: complete,action: return_zip_path, and the finalzip_path; its deterministic validation guarantees the zip containsSKILL.md,agents/openai.yaml, the index, source Markdown, the retrieval script, and every referenced extracted asset. - Return only the reported
zip_pathimmediately. Do not calllsor reopen the zip, index, source chunks, ordoc.logafter a successful build. Inspect them only to diagnose a reported script error.
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.

