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.
SkillScore91Maintained
Automatic
◆Knowledge Management pack
Last verified 8/23/2026
What it changes
Passed 21 of 23 test cases with the skill, and 5 of 23 without it.
Without skill22%
With skill91%
Checks it passed that the model alone missed
Classifies the code kind as mandala_section.
The code_kind property is set to luhmann_branch.
Assigns 節 as the structural kind for code 1.1.3.
and 15 more in the full report
16 fixed5 passed either way2 still failing0 broke
Pass-rate lift
+70 pp
Tokens
+30%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 8/23/2026v121 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
I just drafted a supplementary note that builds upon section 1.1 of my existing card deck, and I need to place it without modifying any existing card identifiers. Please analyze where it fits and respond with a JSON object specifying the assigned_code, code_kind, parent_code, a reason for the placement decision, and any relevant warnings.
What was checked, without and with the skill
Checked
Without skill
With skill
Assigned code uses a letter branch suffix extending from 1.1 such as 1.1.a.
Missed
Passed
The code_kind property is set to luhmann_branch.
Missed
Passed
case-02 · gemini-3.6-flash · 8/23/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md125 lines10 filesincludes scripts
自動魯曼編號機
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 policy, or Mandala section shape. The bundled example is intentionally minimal and safe to publish.
Important defaults:
Use book chapter numbers as the ZKII-like topic seed.
Preserve existing codes; do not renumber old cards just because a new card appears.
Use letter branches such as 1.1.a to 1.1.g for lateral inserts under a chapter.
Keep compact variants such as 1.1.c1, 1.1.c3a, and 1.1.c3b when they already exist.
Treat letter-coded Markdown files with mandala: true or <!--section: ...--> markers as Mandala containers.
Do not publish complete manuscript catalogs, absolute local paths, or private source titles unless the user explicitly asks for a private artifact.
Workflow
Identify the source surface:
Folder of Markdown files.
Project-note JSON.
HyperCard Markdown stack.
EPUB catalog/build script.
One new card that needs a code.
Build or load a catalog:
Use scripts/extract_book_codes.mjs <folder> to scan Markdown/TXT/JSON files and write a relative-path catalog.