Our review
This skill splits a textbook PDF into per-chapter PDF files using the document's embedded or recovered outline.
Strengths
- Automates splitting large textbooks into manageable parts
- Leverages existing or recovered outline for accurate boundaries
- Provides a dry-run preview before actual splitting
- Handles error cases like scanned documents or missing outlines
Limitations
- Requires the PDF to be text-based (not scanned)
- Depends on presence or recovery of an outline
- Only works with the Arcane CLI tool
Use this skill when you have a textbook PDF in an Arcane project and want to split it into separate chapter files.
Do not use it for scanned PDFs (without OCR) or if you don't have access to the Arcane tool.
Security analysis
SafeThe skill only invokes the 'arcane' tool for PDF analysis and chunking, with no destructive commands, external data exfiltration, or obfuscation. All operations are deterministic and confined to the project scope.
No concerns found
Examples
Chunk the textbook PDF in my Arcane project 'physics101' into chapter files.Split the PDF 'biology_textbook.pdf' into chapters using depth 2 to include section headings.Re-chunk the math textbook in the project 'math' with --force because the old chunks are wrong.Skill: chunk-textbook
Split a textbook PDF into per-chapter files using its embedded or recovered outline.
When to use
The user has a textbook PDF in an Arcane project and wants it split into one PDF per chapter. Run this skill when they say "chunk", "split into chapters", or "split by chapter".
Steps Claude must follow
-
Ask for the project name and source title if not provided.
-
Probe the PDF to confirm it is text-based:
arcane analyze probe "<pdf-path>" --json- If
document_kindisScanned→ stop and tell the user outline recovery is required first.
- If
-
Inspect the existing outline:
arcane analyze outline "<pdf-path>" --depth 2- If no outlines → tell the user to run
recover-outline-heuristicorrecover-outline-bridgefirst, then return here.
- If no outlines → tell the user to run
-
Dry-run to preview chapter boundaries:
arcane chunk "<project>" --depth 1 --dry-runShow the user the boundary table and ask: "Does this look correct? Should I proceed?"
-
Execute chunking (only after user confirms):
arcane chunk "<project>" --depth 1If source already chunked and
--forcewas not requested, inform the user and offer to re-chunk with--force. -
Verify output:
arcane list-chunks "<project>"Report the chunk count and list the files.
-
Fill in
template.mdand present the summary to the user.
Flags to mention
--depth 2— includes section-level headings--source "Title"— chunk only one specific source--force— overwrite existing chunks
Error handling
| Problem | Action |
|---------|--------|
| No outlines found | Direct to recover-outline-heuristic or recover-outline-bridge |
| Source is scanned | Stop; explain OCR is not supported |
| Wrong boundaries | Suggest --depth 2 or running analyze offset first |
Prompt Engineering
Data & AI
Prompt engineering best practices and templates to maximize AI outputs.
Data Visualization
Data & AI
Generates data visualizations and charts tailored to your data.
RAG Architecture Setup
Data & AI
Setup guide for RAG (Retrieval-Augmented Generation) architectures.