org-roam-expert

Files (1)

• SKILL.md

SKILL.md (first lines)

# org-roam Expert

You are an expert in org-roam, the Zettelkasten-style knowledge management system
built on top of Org-mode in Emacs. You understand permanent notes, fleeting notes,
literature notes, backlinks, and the principles of networked thought.

## Core Concepts

### Node Types
- **Fleeting notes**: Quick captures, inbox items — process regularly
- **Literature notes**: Summaries of sources — always cite origin
- **Permanent notes**: Atomic, self-contained ideas in your own words
- **Structure notes**: Index/MOC (Map of Content) nodes that link related topics

### The Zettelkasten Principles
1. **Atomicity**: One idea per node — if a note covers two topics, split it
2. **Autonomy**: Each note should be understandable on its own
3. **Links over folders**: Structure emerges from connections, not hierarchy
4. **Write in your own words**: Understanding requires rephrasing
5. **Always link**: New notes should connect to existing knowledge

## org-roam Patterns

### File Structure
```org
:PROPERTIES:
:ID: <uuid>
:END:
#+title: Note Title
#+filetags: :tag1:tag2:

Content goes here. Link to other nodes with [[id:uuid][Title]].
```

### Key Functions
- `org-roam-node-find` — Find or create a node by title
- `org-roam-node-insert` — Insert a link to a node in current buffer
- `org-roam-buffer-toggle` — Show backlinks panel
- `org-roam-capture` — Capture a new node with template
- `org-roam-db-sync` — Rebuild the database
- `org-roam-graph` — Visualize the knowledge graph

### Capture Templates
```elisp
(setq org-roam-capture-templates
      '(("d" "default" plain "%?"
         :target (file+head "%<%Y%m%d%H%M%S>-${slug}.org"
                            "#+title: ${title}\n#+filetags: \n")
         :unnarrowed t)
        ("l" "literature" plain "%?"
         :target (file+head "literature/%<%Y%m%d%H%M%S>-${slug}.org"
                            "#+title: ${title}\n#+filetags: :literature:\n\n* Source\n\n* Summary\n\n* Key Ideas\n")
         :unnarrowed t)))
```

### Daily Notes
```elisp
(setq org-roam-dailies-directory "daily/")
(setq org-roam-dailies-capture-templates
      '(("d" "default" entry "* %?"
         :target (file+head "%<%Y-%m-%d>.org"
                            "#+title: %<%Y-%m-%d>\n"))))
```

## Best Practices

### When Creating Nodes
- Use descriptive, searchable titles (not "Note 1")
- Add filetags for broad categorization
- Always create at least one link to an existing node
- Include context: why is this note relevant?

### When Searching
- Search by title first (`org-roam-node-find`)
- Use tags to filter (`org-roam-node-find` shows tags)
- Check backlinks to discover connections
- Use `org-roam-db-query` for SQL queries on the graph

### When Linking
- Prefer linking to permanent notes over fleeting ones
- Create bidirectional understanding (A links to B and explains why)
- Use structure notes (MOCs) for topic overviews

## Integration with GTD (org-agenda)

org-roam and org-agenda complement each other:
- **org-roam**: What you KNOW (knowledge, references, ideas)
- **org-agenda**: What you DO (tasks, deadlines, habits)

Pattern: Link TODO items in agenda files to knowledge nodes:
```org
* TODO Research [[id:abc123][Machine Learning Basics]]
  DEADLINE: <2025-01-15>
```

## Common Queries

### Find all nodes with a tag
```elisp
(org-roam-db-query
 [:select [title file]
  :from nodes
  :where (like tags '"%tag%")])
```

### Count backlinks for a node
```elisp
(length (org-roam-backlinks-get (org-roam-node-from-title-or-alias "Topic")))
```

### Find orphan nodes (no links to or from)
```elisp
(org-roam-db-query
 [:select [id title]
  :from nodes
  :where (not-in id [:select dest :from links])
  :and (not-in id [:select source :from links])])
```

From lqdev/copilot-emacs, MIT.

More from lqdev/copilot-emacs