Menu
Use when after nn new or nn update to discover notes that should be linked to the modified note. Load with `nn skills get nn-link-suggester`.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when you need to look up an nn command, flag, or usage pattern. Load with `nn skills get nn-guide`.
Use when cleaning up a specific note or before promoting it — runs atomicity, link, and title checks. Load with `nn skills get nn-refine`.
Use when ending a session to consolidate captures, assess promotion eligibility, and update the daily page. For weekly review use --weekly; for daily page only use --daily; for lightweight mid-session capture use --partial. Load with `nn skills get nn-session-debrief`.
Use when asked to organise, capture, or link notes in the Zettelkasten. Load with `nn skills get nn-workflow`.
Use when about to take any action that introduces new information not already in the conversation. Load with `nn skills get nn-capture-discipline`.
Use when running a hygiene pass across multiple notes at once — drafts, orphans, long notes, or a topic cluster. Load with `nn skills get nn-refine-workflow`.
| name | nn-link-suggester |
| description | Use when after nn new or nn update to discover notes that should be linked to the modified note. Load with `nn skills get nn-link-suggester`. |
| when_to_use | After nn new or nn update, to discover notes that should be linked to the newly created or modified note. Invoke with /nn-link-suggester. |
After any capture, surface candidate notes and propose nn link commands with annotations.
Invoke after nn new or nn update to discover notes that should be linked to the newly created or modified note.
Get candidates — run nn suggest-links <id> to get a BM25-ranked list of candidate notes. The output includes already-linked notes (marked) and notes with no term overlap (excluded with count).
Inspect candidates — read the candidate summaries. For each candidate, assess whether a meaningful relationship exists.
Filter already-linked — the output marks notes already linked; skip those unless an additional link type is warranted.
Propose links — for each accepted candidate, name the relationship type and write an annotation explaining why. Use nn bulk-link for multiple targets (single commit):
nn bulk-link <id> \
--to <id1> --annotation "..." --type <type> \
--to <id2> --annotation "..." --type <type>
Or single links:
nn link <id> <other-id> --annotation "..." --type <type>
Bidirectional check — consider whether the target note should also link back. If so, add reverse links with appropriate types.
Tag suggestions — run nn suggest-tags <id> and apply any tags appearing in ≥2 similar notes that the note lacks:
nn update <id> --tags "existing-tag,new-tag" --no-edit
nn suggest-links <id> [--limit N]
nn suggest-tags <id> [--json]
nn link <from> <to> --annotation "..." --type TYPE
nn bulk-link <from> --to <id> --annotation "..." --type TYPE [--to <id> --annotation "..." --type TYPE]...
nn update-link <from> <to> --annotation "..." --type TYPE [--status reviewed]
nn update <id> --tags "..." --no-edit
refines | contradicts | source-of | extends | supports | questions | governs | requires
nn suggest-links is run on the focal notenn link includes both --annotation and --type