Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Zettelkasten

ASecurity

Practice the Zettelkasten method: atomic notes, unique IDs, linking, and building a thinking partner from your notes. Use when doing research, writing, or long-term knowledge work.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoreact

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill zettelkasten --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Zettelkasten?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Zettelkasten
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-zettelkasten/badge)](https://www.skillsdirectory.com/skills/aicodedecode-zettelkasten)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: zettelkasten
description: Practice the Zettelkasten method: atomic notes, unique IDs, linking, and building a thinking partner from your notes. Use when doing research, writing, or long-term knowledge work.
category: productivity
---

# Zettelkasten

## Overview

The Zettelkasten ('slip box') is a note-taking method for thinking: atomic notes, densely linked, that surprise you with connections.

Developed by sociologist Niklas Luhmann, who credited it for his extraordinary output — the box became a conversation partner.

Principles: one idea per note, every note linkable, links that explain the relationship, and writing in your own words.

Tools don't matter much — index cards work. What matters is atomicity, linking discipline, and regular revisiting.

## When to use

- Academic research, thesis, or dissertation work
- Writing books, long essays, or substantial articles
- Building deep expertise in a field over years
- Any knowledge work where ideas need to connect and compound
- Moving beyond highlighting to genuine thinking in notes

## Core concepts

- **Atomicity.**
  One idea per note. If a note contains two ideas, split it. Atomic notes link cleanly; compound notes link messily.
- **Unique addresses.**
  Every note gets a unique ID (timestamp, sequence). Links point to IDs, so notes can move and rename without breaking.
- **Own words.**
  Rewrite everything in your language. Copy-paste is collecting; restating is thinking. Luhmann's rule: the box contains your thoughts, not quotes.
- **Link with context.**
  Don't just link — say why: 'contradicts', 'extends', 'example of', 'prerequisite for'. The relationship is the knowledge.
- **Fleeting -> literature -> permanent.**
  Fleeting notes (raw capture) -> literature notes (source summaries) -> permanent notes (your ideas, atomic, linked). Only permanent notes live in the box.
- **Branching, not filing.**
  New notes attach to existing ones via links, forming branches of thought. No fixed hierarchy — structure emerges from connections.
- **The box as partner.**
  Revisit randomly and by following links. Serendipitous encounters with old notes generate new ideas — if notes are atomic and well-linked.
- **Write from the box.**
  Outlines assemble from linked note sequences. Writing becomes arranging existing thoughts, not generating from blank pages.

## Practical workflow

1. **Set up the box.**
   Any tool with unique IDs and backlinks (Obsidian, plain files, even cards). One inbox for fleeting notes, one home for permanent notes.
2. **Capture fleeting notes.**
   Read with pen: jot raw reactions, quotes with page numbers, questions. Messy is fine — these are temporary.
3. **Write literature notes.**
   After reading: summarize the source's argument in your words, one note per idea-cluster, with full reference.
4. **Create permanent notes.**
   Convert: one idea per note, your words, unique ID, descriptive title. Link to 2-3 related notes with the relationship stated.
5. **Link deliberately.**
   Each new note: which existing notes does it contradict, extend, exemplify, or depend on? Write the link sentence explicitly.
6. **Follow the branches.**
   Weekly: pick a note, follow its links for 20 minutes. Add new links and notes as connections occur to you.
7. **Harvest for writing.**
   When writing: gather the branch, arrange note sequences into an outline, draft from the notes. Cite the box, not memory.
8. **Maintain the garden.**
   Monthly: merge duplicates, split compound notes, fix dead links, strengthen weak link-descriptions. The box improves with tending.

## Common pitfalls

- **Collecting without atomicity.**
  Long multi-idea notes that can't link precisely. Split ruthlessly — atomicity is the whole game.
- **Link-stuffing.**
  Ten unexplained links per note. Links without stated relationships are noise, not knowledge.
- **Skipping your own words.**
  Boxes full of quotes and highlights. If it's not in your words, it's not your thought.
- **No literature notes.**
  Permanent notes without source grounding become unsourced opinions. Keep the chain: fleeting -> literature -> permanent.
- **Filing instead of linking.**
  Elaborate folder hierarchies with few links. The Zettelkasten's power is the graph, not the folders.
- **Never revisiting.**
  Writing notes and never returning. The serendipity engine needs regular visits — schedule them.
- **Perfectionist IDs.**
  Agonizing over numbering schemes. Timestamps work fine; the ID just needs uniqueness, not meaning.
- **Tool-first adoption.**
  Spending months configuring software before writing ten notes. Start with any tool; the method is the skill.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →