Zk

zettlekasten

Install

npx -y skills add colchuck-ai/zettlekasten --skill zk

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Maintains a Zettelkasten—atomic linked markdown notes as an on-disk knowledge graph and agent memory extension: inbox → permanent notes, date+slug IDs, markdown links with explicit context, object tags, structure and buffer notes. Use when the user wants zettelkasten, slip-box, linked notes, persistent agent memory, knowledge capture, or initializing a notes-only layout; when working in any directory that holds the slip-box layout (`template-zettel.md`, `inbox/`, and `YYYY-MM-DD-slug.md` permanent notes); when copying the zk-template assets to bootstrap a slip-box.

The file declares its own license as GPL-3.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

5.3 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

Zettelkasten (ZK) as memory extension

Treat the note archive as durable hypertext: small files, stable filenames as IDs, meaningful links (always say why a link matters). Agents use it to accumulate structured knowledge across sessions without stuffing context—retrieve by path/tag and follow links like a graph.

This skill is the single source of truth for slip-box conventions and procedures. Slip-boxes hold only notes; there is no per-slip-box AGENTS.md or agent-facing procedure doc—apply this skill wherever the layout is detected.

Where the slip-box lives

No fixed path. The slip-box root is whichever directory holds the Zettel layout: template-zettel.md, inbox/, and permanent notes named YYYY-MM-DD-slug.md in that directory's root. Users may place that folder anywhere (e.g. docs/zk/, knowledge/notes/, zettelkasten/). There is no separate config key—the chosen path is the contract.

Resolve the slip-box by user instruction, by opening a file whose sibling files match the layout above, or by project docs that state the path. When operating in a nested repo, still read parent AGENTS.md files from repo root down; this skill refines slip-box behavior on top of them.

Conventions (quick reference)

IDs / filenames: YYYY-MM-DD-slug.md (kebab-case slug). Markdown links only: [text](path/to/note.md)—no [[wikilinks]].
Permanent notes: root of the slip-box folder. inbox/ for fleeting captures; process regularly into permanent notes or discard.
Tags: include #YYYY/MM/DD for creation date; prefer object tags (concrete concept) over broad topic tags. See references/zettelkasten.md.
New notes: use assets/zk-template/template-zettel.md; link to at least one existing note with context; avoid orphans.

Source lines (provenance)

When a note records where content was captured:

Use *Source: …* (italic line).
Hyperlink the originating artifact—never prose-only dates. Example: *Source: [design review](../meetings/2026-05-01.md).*
Multiple origins → multiple links, comma-separated.

Procedures

Create a permanent note

Name the file YYYY-MM-DD-slug.md (date + kebab-case slug).
Fill from template-zettel.md: title, tags (include #YYYY/MM/DD), Summary, Notes, Links.
Body in your own words; every link states why it matters.
Save in the slip-box root (not inbox/).
Link to at least one existing note; avoid orphans.

Process the inbox

Open each item in inbox/.
Promote to a permanent note (steps above), merge into an existing note, or discard. When promoting, preserve or add a hyperlinked *Source:* line pointing at the originating artifact.
Remove processed items so inbox/ stays for quick capture only.

Summary for agents

Decision	Prefer
Linking	Always add link context (why this link).
Note size	One thought per note; split when a note is hard to use or mixes ideas.
Organization	Object tags (not topic); structure notes that emerge; no upfront categories.
New material	Process into notes and links soon; avoid collecting without processing.
Note content	Your own words; add context and relevance.
Structure	Let layers emerge (content → structure notes → main structure); buffer notes for project staging.
Evidence layers	Keep phenomenon, interpretation, and synthesis distinct in or between notes; check primary sources.
Writing	Outline first (attach note refs), then paste and rewrite; separate research and drafting; outlines/buffers per project.

When in doubt, favor connection with explicit meaning over more notes or more links without context. Principles over techniques; less clutter, more clarity.

Full method

Principles (connectivity, atomicity, no collector's fallacy, structure over time, buffer notes, writing workflow) live in references/zettelkasten.md. Read when editing note quality, splits/merges, or structure-note strategy.

Bootstrap from template

Copy the contents of assets/zk-template/ into the user-chosen directory, preserving inbox/ and template-zettel.md.
Do not copy AGENTS.md, README.md, or the full method into the slip-box—this skill owns them, and duplicating invites drift. If a human-facing overview is wanted, add a short README.md that describes only what the folder is (do not restate conventions).

Agents pick up this skill from the layout itself or from the user mentioning a Zettelkasten. No breadcrumb snippet in the repo root AGENTS.md is required.

See assets/README.md.

Gives 0 of the 12 instructions most note taking skills give in ~1.1k tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06

include a visual element on every slidein 44 of 686, across 13 files
use wikilinks for internal vault linksin 35 of 686, across 11 files
commit to a single visual motif across every slidein 34 of 686, across 9 files
read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
keep 0.5 inch minimum marginsin 30 of 686, across 7 files
use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
re-verify affected slides after every fixin 27 of 686, across 5 files
run content QA checks before declaring successin 26 of 686, across 3 files
Use Markdown links for external URLs onlyin 26 of 686, across 10 files
pick a bold topic specific color palettein 24 of 686, across 2 files
read editing guide before editing existing presentationsin 23 of 686, across 1 file
use one dominant color across all slidesin 23 of 686, across 1 file

Said here and by no other author read

use date and slug for filenames
use markdown links not wikilinks
explain why each link matters
apply object tags for concrete concepts
save permanent notes in the slip-box root
process inbox items regularly

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.