agentleFS
shaii819shaii819/reading-assistant-for-claude/skills/reading-assistant/obsidian-zettelkasten/SKILL.md

obsidian-zettelkasten

Skill3 starsChanged 8 months agoMITView on GitHub

Obsidian note templates, naming conventions, and wikilink rules for Zettelkasten output

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. dailyherold/skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every note MUST have YAML frontmatter with:

    line 22
  2. Very specific:

    All cross-references use [[slug]] syntax

    line 36
  3. Very specific:

    When obsidian_vault is configured:

    line 44
  4. Distinctive:

    Do NOT delete user-added files

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Obsidian Zettelkasten Conventions

Naming Convention

Note typeFilename patternWikilink pattern
MOCMOC-{book-slug}.md[[MOC-{book-slug}]]
Chapter{book-slug}-ch{NN}-{title-slug}.md[[{book-slug}-ch01-intro]]
Concept{concept-slug}.md[[concept-slug]]
Quote{book-slug}-q{NNN}.md[[{book-slug}-q001]]

Concept notes have NO book prefix — they are cross-book by design.

Frontmatter Fields

Every note MUST have YAML frontmatter with:

  • type: moc | chapter | concept | quote
  • book: full book title
  • author: author name
  • tags: array of tags
  • created: ISO date

Additional per-type:

  • Chapter notes: chapter (number)
  • Quote notes: chapter, speaker, verified
  • Concept notes: chapter (where first seen)

Wikilink Rules

  • All cross-references use [[slug]] syntax
  • MOC links to chapters and concepts
  • Chapters link to MOC and concepts
  • Concepts link to MOC, chapter, and related concepts
  • Quotes link to MOC and chapter

Vault Integration

When obsidian_vault is configured:

  1. Copy obsidian/ contents to {vault}/{book-slug}/
  2. Overwrite existing generated files (idempotent)
  3. Do NOT delete user-added files

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.