Agent skill · Design & Presentation

auto-luhmann-numberer

Assign, validate, normalize, and explain Luhmann/Zettelkasten-style project-note codes for Chinese book manuscripts, Obsidian Markdown folders, Mandala-Grid section files, HyperCard Markdown stacks, and project-note JSON to EPUB workflows. Use when Codex needs to scan folders for 部/章/節/項/目 numbering, generate stable card ids, insert branch codes without renumbering existing notes, map letter-coded branches to Obsidian Mandala sections, preserve K### keyword index cards, sanitize private catalogs into public examples, or prepare card IDs for EPUB and HyperCard output.

twhsigithub.com/twhsiGitHub ↗
claude-codecodexships scripts
Install
npx skills add twhsi/skills --skill auto-luhmann-numberer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 11
SKILL.md size: 6 KB
Bundled scripts: yes
Path: skills/auto-luhmann-numberer/SKILL.md
Open the folder on GitHub →
Where it comes from
Source: twhsi/skills
Stars: 256
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 自動魯曼編號機 Use this skill to manage stable writing-system addresses for book manuscripts and card boxes. Prefer the active book outline as the topic-number seed, then let Luhmann-style branches grow inside the outline without renumbering existing notes. When publishing the skill or sharing outputs, reduce real catalogs to a small public example. ## Core Model Use four separate namespaces: - `book_topic_code`: pure numeric book addresses, at most five levels: 部、章、節、項、目. Examples: `1`, `1.1`, `1.1.3`, `1.1.3.2.1`. - `luhmann_branch_code`: letter or mixed suffixes that grow from a book address. Examples: `1.1.a`, `1.1.E`, `1.1.c3b`, `1.1.d.1`. - `mandala_section_code`: local Obsidian Mandala-Grid section comments inside one Markdown file. Examples: `<!--section: 1-->`, `<!--section: 1.7-->`, `<!--section: 1.8.8-->`. - `keyword_index_code`: index-card ids such as `K001`, kept separate from topic codes. Never merge these namespaces. A `K001` card is not a chapter. A local `section: 1.7` is not the book's `1.7` chapter unless the source explicitly says so. ## Default Preferences Read `references/public-numbering-rules.json` when you need the numbering taste, output schema, public-case pol

What's inside
Steps it walks through
  1. Core Model
  2. Default Preferences
  3. Workflow
  4. Common Requests
  5. Output Shape
  6. Public Sharing Rule
  7. Bundled Resources
Ships with 10 files
  • agents/openai.yaml
  • assets/download.epub
  • assets/epub-validation-report.json
  • assets/自動魯曼編號機_使用手冊_公開版_2026-06-17_03.epub
  • references/book-chapter-card-catalog.json
  • references/book-chapter-card-catalog.md
  • references/public-numbering-rules.json
  • scripts/build_skill_guide_epub.py
  • scripts/extract_book_codes.mjs
  • scripts/validate_luhmann_catalog.py
More from skills
All skills →
About this skill
What does the auto-luhmann-numberer skill do?

Assign, validate, normalize, and explain Luhmann/Zettelkasten-style project-note codes for Chinese book manuscripts, Obsidian Markdown folders, Mandala-Grid section files, HyperCard Markdown stacks, and project-note JSON to EPUB workflows. Use when Codex needs to scan folders for 部/章/節/項/目 numbering, generate stable card ids, insert branch codes without renumbering existing notes, map letter-coded branches to Obsidian Mandala sections, preserve K### keyword index cards, sanitize private catalogs into public examples, or prepare card IDs for EPUB and HyperCard output.

How do I install it?

Run `npx skills add twhsi/skills --skill auto-luhmann-numberer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From twhsi/skills, a repository with 256 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going