Epub Hypercard Obsidian Skill for Codex

Convert EPUB card books into Obsidian-ready HyperCard Markdown folders and portable zip files. Use when Codex needs to turn an EPUB with XHTML chapters, table-of-contents cards, keyword index cards, backlinks, Luhmann/Zettelkasten numbers, or cross-links into one Markdown file per card with verified relative links, keyword cards, previous/home/next navigation, and GitHub/shareable zip output.

6k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

256

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/twhsi/skills --skill epub-hypercard-obsidian

The instruction itself

7 sections, as written by the author

EPUB HyperCard Obsidian

Create an Obsidian folder from an EPUB card book. Each EPUB正文 card becomes one Markdown file. The output uses the four-table HyperCard format:

Luhmann/code + card title
Card content
Index-card hyperlinks
Previous/home/next navigation

Use this skill for EPUBs generated from project notes, Luhmann/Zettelkasten chunks, chapter cards, keyword index cards, or book-check editions that need to become clickable Obsidian Markdown.

Quick Start

Run the generator:

python3 scripts/epub_to_hypercard_obsidian.py INPUT.epub --out OUTPUT_DIR --zip

Recommended portable mode:

python3 scripts/epub_to_hypercard_obsidian.py INPUT.epub --out 3.4-centaur-hypercard-obsidian-portable --zip --portable

The script writes:

index.md: stack home and chapter directory
card-*.md: one正文 card per EPUB article/chapter
keyword-index.md: keyword directory
key-*.md: one keyword index card per keyword
OUTPUT_DIR.zip: shareable zip, when --zip is set

Workflow

Inspect the EPUB before converting.
Confirm it has META-INF/container.xml, OEBPS/content.opf, XHTML text files, and a spine.
Treat Text/toc.xhtml or the first non-article spine item as the directory card.
Treat Text/index.xhtml or the XHTML with .index-card sections as the keyword index card.
Treat XHTML files with <article> as正文 HyperCards.

Generate Markdown card files.
Use p.code text for the card code, such as 3.4.1｜113字.
Use h1 as the visible card title.
Put body paragraphs into table 2 as one cell, separated with <br><br>.
Link keyword occurrences to key-*.md.
Keep Markdown table links as label to avoid Obsidian heading-anchor drift.

Generate keyword cards.
Parse index.xhtml sections into K001, keyword, weight, and target cards.
Make one key-*.md per keyword.
Add previous/home/next navigation across keyword cards.

Verify all links.
Every label must resolve to a file in the output folder.
Do not rely on [[#heading]] same-file anchors for this workflow.
Prefer --portable for sharing with AI tools, GitHub, macOS Finder, Windows, or zip upload workflows.

Deliver the folder and zip.
Give the user the output folder path and zip path.
Report card count, keyword count, and link verification result.

Filename Modes

| Mode | Shape | Use |

|---|---|---|

| --portable | card-3-4-1.md, key-k001.md | Default recommendation for zip/GitHub/AI upload |

| no --portable | 3.4.1-標題.md, K001-關鍵字.md | More human-readable inside Obsidian, less portable across zip tools |

Four-Table Card Contract

| 魯曼編號 | 卡片標題 |
|---|---|
| `{{code}}` | **{{title}}** |

| 內容 |
|---|
| {{content_with_links}} |

| 索引 |  |  |  |
|---|---|---|---|
| {{keyword_link_1}} | {{keyword_link_2}} | {{keyword_link_3}} | {{keyword_link_4}} |

| ← 上一張 | Card {{n}} / {{total}} | 下一張 → |
|---|---|---|
| {{previous_card}} | [Home](index.md) | {{next_card}} |

Link Rules

Use relative Markdown file links: TARS.
Do not use Obsidian alias wikilinks inside tables, because [[target|alias]] contains | and can break table columns.
Do not use same-file heading anchors for card navigation when the user wants a folder or zip.
Escape Markdown table pipes in extracted text as \|.

Validation Output

Before finishing, run or report the script validation:

cards: ...
keywords: ...
missing_links: 0
zip: ...

If missing_links is not zero, fix the generated links or parser before delivery.

Other skills for the same job

different authors, same section of the catalogue

DOCX

by anthropics

vendor ×16

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

3k tokens

How to use it

Copy the folder

Take twhsi/epub-hypercard-obsidian from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.