mikonos/zettelkasten-agent-skills · Archived

index-note

Create an index / entry-point note (MOC-like). Use when asked to build a directory, navigation, or “best starting points”.

First seen May 17, 2026

Installation

$ npx skills add mikonos/zettelkasten-agent-skills --skill index-note

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mikonos/zettelkasten-agent-skills.

npx skills add mikonos/zettelkasten-agent-skills

Browse all from mikonos/zettelkasten-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,764 B
  • docs SUMMARY.md 144 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Index Note

Principle

An index is an entry point, not a taxonomy. Be selective and keep it short.

Quick start

  • Pick an index type (keyword / structure / thinking trail).
  • Select only 3–5 best entry notes.
  • Immediately add bidirectional links (index ↔ entry notes).

Index types

  • Hub note: stable top-level entry for a domain
  • Structure note: project outline / argument structure
  • Thinking trail: chronological evolution of a line of thought

Workflow

Step 1: Collect

  1. Choose index type
  2. Search related notes
  3. Extract 3–5 core concepts
  4. Pick 1–2 best entry notes per concept

Step 2: Shape the structure

  • Separate primary vs secondary concepts
  • Use indentation to show relationships
  • Keep it within one screen

Step 3: Link & maintain

  • Index → entries: [[Note]]
  • Entries → index: add backlink
  • Mark created/updated time

Output template

# Index: [Topic]

## Overview
- **Type**: Hub / Structure / Trail
- **Status**: SEED / EVERGREEN
- **Created**: YYYY-MM-DD

## Core entry points
- [[Best starting note]] — why it’s the best start
- [[Second entry]] — why

## Quick navigation
- **Start here**: [[Best starting note]]
- **Go deeper**: [[Advanced note]]

## Related indexes
- [[Related index]]

Common mistakes

  • Treating the index as a full catalog → keep only the best entry points
  • Too much hierarchy → keep it readable
  • Never updating → review periodically

Quality checks

  • Entry points are truly “best starts”
  • Navigation is clear
  • Fits within one screen