Our review
Recovers PDF outline bookmarks by OCR-ing the printed table of contents via the Arcane-PP server, then using the parsed entries as seeds for recovery.
Strengths
- Leverages the printed table of contents as a reliable source even without a reference edition
- Combines OCR and heuristic analysis for robust recovery
- Offers both manual and automated paths for different confidence levels
Limitations
- Requires the Arcane-PP server to be running
- Does not work on scanned PDFs (document_kind == 'Scanned')
- TOC page range must be known or detected automatically
Use this skill when your PDF lacks bookmarks and the printed table of contents is the only reliable source of chapter structure.
Do not use if the PDF is scanned or if a reference edition with bookmarks is available.
Security analysis
SafeThe skill uses Arcane-PP CLI commands for PDF analysis and outline recovery, with no destructive or exfiltrating actions. Shell scripts are local and only for server checks and PDF processing.
No concerns found
Examples
Recover outline bookmarks for my PDF by OCR-ing its printed table of contents using Arcane-PP.I have a PDF without bookmarks. Use the printed table of contents (pages 3-5) to recover the outline.Set TOC page ranges for all sources in my project and recover outlines for the whole project.Skill: recover-outline-bridge
Recover PDF outline bookmarks by OCR-ing the printed table of contents via the Arcane-PP server, then using the parsed entries as seeds for recovery.
When to use
- The PDF has no bookmarks and no reference edition is available
- The printed TOC is the only reliable source of chapter structure
- The user mentions "Arcane-PP", "OCR", "TOC pages", or "bridge"
- Heuristic recovery (
recover-outline-heuristic) gave poor results
Prerequisites
- Arcane-PP server must be running. Verify:
bash .claude/commands/recover-outline-bridge/scripts/check-server.sh - User must provide (or agree to identify) the TOC page range.
Steps Claude must follow
-
Probe the PDF:
arcane analyze probe "<pdf>" --jsonAbort if
document_kind == "Scanned". -
Identify TOC page range — ask the user if unknown. Alternatively, detect automatically:
arcane analyze layout "<pdf>" --json | python3 -c \ "import sys,json; d=json.load(sys.stdin); \ toc=[a for a in d['anchors'] if a['kind']=='TocEntry']; \ print(f\"TOC pages: {min(a['page_index']+1 for a in toc)}-{max(a['page_index']+1 for a in toc)}\") if toc else print('No TOC anchors detected')" -
Manual path — extract and inspect (recommended for first time):
arcane pdf extract-pages "<pdf>" --start N --end M toc-extract.pdf arcane process-toc "<pdf>" --toc-pages "N-M" --output seeds.jsonShow the user the
seeds.jsoncontent. Ask: "Does this look like the correct chapter list?" Then run recovery with the seeds:arcane recover-outline "<pdf>" --seed-file seeds.json --toc-pages "N-M" \ --dry-run --depth 2 -
Automated path (when user is confident):
arcane recover "<pdf>" --toc-pages "N-M" --output "<fixed.pdf>" --depth 2 -
For a whole project (when all sources have TOC ranges set):
arcane recover-project --project "<name>" --dry-run arcane recover-project --project "<name>" -
Verify:
arcane analyze outline "<fixed.pdf>" --depth 2 -
Fill in
template.mdand present the summary.
Setting TOC ranges for batch recovery
When adding sources, include TOC page ranges so recover-project works:
arcane add "<project>" "<pdf>" --textbook --toc-start-page N --toc-end-page M
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Create log entries with timestamps
Documentation
Creates timestamped log entries to document discoveries, meetings, code reviews, articles, or significant events. Structures information with a summary, event type, sources, and tags, then saves the file to `docs/log/` with a date-based filename and descriptive slug.