Org-roam and Org-mode Management

VerifiedCaution

This skill provides comprehensive org-mode knowledge and org-roam note management via emacsclient. It creates, searches, and links notes, generates backlinks, and attaches files. Use it when working with org-roam notes to avoid breaking the database or backlinks.

Sby Skills Guide Bot
ProductivityIntermediate
6/2/2026
Claude Code
#org-roam#org-mode#emacs#note-taking#knowledge-management

Recommended for

Automated summary

This skill manages org-mode and org-roam notes via emacsclient, enabling creation, search, linking, and backlink analysis without direct file editing.

Strengths

  • Integrates with running Emacs daemon for database consistency
  • Supports tags, content, and attachments
  • Provides search and backlinks functionality
  • Prevents database corruption by using dedicated scripts

Limitations

  • Requires Emacs daemon running and org-roam configured
  • Only works with local Emacs setup
  • Commands are limited to predefined functions
When to use it

Use this when you need to create, link, or search org-roam notes while ensuring database integrity and avoiding direct file manipulation.

When not to use it

Do not use this for editing non-roam org files, or if Emacs daemon is not available, or for simple text notes outside of an org-roam knowledge base.

Security analysis

Caution
Quality score90/100

The skill uses a bash wrapper to evaluate arbitrary Emacs Lisp expressions through emacsclient. While the intent is safe (org-roam note management), the capability grants significant system access, including file deletion, network access, and shell execution, making it a powerful tool that could be misused.

Findings
  • •Arbitrary Elisp execution allowed via org-roam-eval script, which could be leveraged for destructive or exfiltrating actions if the model is manipulated.
How this analysis is made

Examples

Create a roam note
Create a new roam note titled 'My Project Ideas' with tags 'project' and 'ideas'.
Search roam notes
Search for roam notes with 'react' in the title.
Link two roam notes
Create a bidirectional link between note 'React Hooks' and note 'React Components'.

name: roam description: | Org-mode formatting and org-roam note management via emacsclient. Never use Read/Write/Edit on roam notes directly.

Triggers: roam note, org-roam, org-mode, .org files, Zettelkasten, backlinks allowed-tools:

  • Bash(${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval:*)
  • Bash(git status:*)
  • Bash(git add:*)
  • Bash(git commit:*)
  • Bash(git diff:*)
  • Bash(git log:*)
  • Bash(mktemp:*)
  • Bash(emacsclient:*)

Org-mode and Org-roam Skill

This skill provides comprehensive org-mode knowledge and org-roam note management via emacsclient.

Two modes of operation:

  1. Org-mode formatting — Reference docs for syntax, properties, timestamps, links (no emacsclient needed)
  2. Org-roam operations — Create, search, link notes via emacsclient to running Emacs daemon

Critical: Don't Use Direct File Tools

NEVER use Read/Write/Edit tools on roam notes. Always use this skill instead.

Why:

  • Roam notes require org-roam database updates
  • IDs must be generated with microseconds precision
  • File creation must respect user's capture templates
  • Direct file operations bypass database sync and break backlinks

Trigger patterns:

  • User mentions "roam note" or "org-roam"
  • File paths contain /roam/ or /org-roam/
  • Keywords: backlinks, Zettelkasten, knowledge graph, PKM, second brain

Permissions

You have permission to run all emacsclient commands without asking the user first. Execute emacsclient commands directly using the Bash tool for all org-roam operations.

Quick Reference

Prerequisites:

  • Emacs daemon running: emacs --daemon
  • org-roam installed in Emacs
  • Skill auto-loads on first use (no manual config needed)

Using the skill:

All operations use the auto-loading wrapper ${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval:

# Create note (tags MUST be a list, not string)
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-note \"Title\" :tags '(\"tag\") :content \"text\")"

# Create with large content (recommended for >1KB content)
TEMP=$(mktemp -t org-roam-content.XXXXXX)
echo "Large content..." > "$TEMP"
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-note \"Title\" :content-file \"$TEMP\")"
# Temp file auto-deleted!

# Search
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-search-by-title \"search-term\")"

# Backlinks
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-get-backlinks-by-title \"Note Title\")"

# Link notes
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-bidirectional-link \"Note A\" \"Note B\")"

# Attach file
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-attach-file \"Note Title\" \"/path/to/file\")"

# Diagnostics
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-doctor)"

Key principle: Package auto-loads on first call, then stays in memory - no repeated loading overhead.

Core Workflows

Workflow A: Creating Notes

Simple note:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-note \"Note Title\")"

With tags and content:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-note \"React Hooks\" :tags '(\"javascript\" \"react\") :content \"Brief notes here\")"

With large content (recommended for complex/large content):

# Create temp file
TEMP=$(mktemp -t org-roam-content.XXXXXX)

# Write content
cat > "$TEMP" << 'EOF'
* Introduction

Content here with proper org-mode formatting.

* Details

More content.
EOF

# Create note (temp file is automatically deleted)
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-note \"My Note\" :tags '(\"project\") :content-file \"$TEMP\")"

Critical: Tags must be a list:

  • ❌ Wrong: :tags "tag" (string)
  • ✅ Correct: :tags '("tag") (list)
  • ✅ Correct: :tags '("tag1" "tag2") (multiple tags)

Content format:

Content should be in org-mode format. For markdown conversion or general org-mode formatting, use the orgmode skill:

# Example workflow:
# 1. Convert markdown to org (orgmode skill)
# 2. Create roam note with org content (this skill)
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval \
  "(org-roam-skill-create-note \"Title\" :content \"* Org content\")"

For general org-mode operations (formatting, conversion, validation), see the orgmode skill. This skill focuses on org-roam-specific operations: note creation, database sync, node linking, and graph management.

See references/functions.md for detailed parameter documentation.

Workflow B: Searching Notes

By title:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-search-by-title \"react\")"

By tag:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-search-by-tag \"javascript\")"

By content:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-search-by-content \"functional programming\")"

List all tags:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-list-all-tags)"

Workflow C: Managing Links

Find backlinks (notes linking TO this note):

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-get-backlinks-by-title \"React\")"

Create bidirectional links:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-bidirectional-link \"React Hooks\" \"React\")"

This creates:

  • Link in "React Hooks" → "React"
  • Link in "React" → "React Hooks"

Insert one-way link:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-insert-link-in-note \"Source Note\" \"Target Note\")"

Workflow D: File Attachments

Two attachment methods:

  1. Attach to References section (preferred - creates visible link):
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-attach-file-to-references \"My Note\" \"/path/to/document.pdf\")"
  • Copies file via org-download
  • Creates/appends "* References" section with link
  • Supports local files, URLs, and base64 data URIs
  1. Attach via org-attach (stores in attachment dir):
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-attach-file \"My Note\" \"/path/to/document.pdf\")"
  • Uses org-mode's standard org-attach system
  • No visible link in note body

List attachments:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-list-attachments \"My Note\")"

Workflow E: Complete Example

User says: "Create a note about React Hooks and link it to my React note"

Step 1: Search for existing note

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-node-from-title-or-alias \"React\")"

Step 2: Create new note

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-note \"React Hooks\" :tags '(\"javascript\" \"react\") :content \"Notes about React Hooks\")"

Step 3: Create bidirectional links

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-bidirectional-link \"React Hooks\" \"React\")"

Step 4: Show user the result Present the created note path and confirm links were established.

Using the Auto-Load Wrapper

All operations use ${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval which:

  1. Auto-loads org-roam-skill package on first call
  2. Connects to running Emacs daemon
  3. Executes the elisp expression

After first call, functions stay in memory - no loading overhead.

Find org-roam directory:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "org-roam-directory"

Sync database (if needed):

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-db-sync)"

Available Functions

All functions use org-roam-skill- prefix:

Note Management:

  • org-roam-skill-create-note - Create new notes
  • org-roam-skill-search-by-title/tag/content - Search notes
  • org-roam-skill-get-backlinks-by-title/id - Find backlinks
  • org-roam-skill-insert-link-in-note - Insert links
  • org-roam-skill-create-bidirectional-link - Create two-way links

Tag Management:

  • org-roam-skill-list-all-tags - List all tags
  • org-roam-skill-add-tag - Add tag to note
  • org-roam-skill-remove-tag - Remove tag from note

Attachments:

  • org-roam-skill-attach-file-to-references - Attach file and add link in References section
  • org-roam-skill-attach-file - Attach file via org-attach system
  • org-roam-skill-list-attachments - List attachments

Utilities:

  • org-roam-skill-check-setup - Verify configuration
  • org-roam-skill-get-graph-stats - Graph statistics
  • org-roam-skill-find-orphan-notes - Find isolated notes
  • org-roam-doctor - Comprehensive diagnostics

See references/functions.md for complete function documentation with all parameters and examples.

Setup and Troubleshooting

Installation: See references/installation.md for:

  • Prerequisites (Emacs daemon, org-roam)
  • No manual configuration needed (auto-loads on first use)
  • Optional: org-roam configuration recommendations

Troubleshooting: See references/troubleshooting.md for:

  • Connection issues (daemon not running)
  • Package loading problems
  • Database sync issues
  • Tag formatting errors
  • Search problems
  • Link issues
  • Performance optimization

Quick diagnostic:

${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-doctor)"

Parsing emacsclient Output

emacsclient returns Elisp-formatted data:

  • Strings: "result" (with quotes)
  • Lists: ("item1" "item2")
  • nil: nil or no output
  • Numbers: 42

Strip quotes from strings and parse structures as needed.

Best Practices

  1. Use lists for tags: Always '("tag") not "tag"
  2. Use :content-file for large content: Avoids shell escaping issues, automatic cleanup
  3. Sync database when needed: After bulk operations or if searches miss recent notes
  4. Use node IDs for reliable linking: More stable than file paths
  5. Check if nodes exist: Before operations on specific notes
  6. Present results clearly: Format output for user readability
  7. Handle errors gracefully: Check daemon running, packages loaded

Additional Resources

Org-mode Formatting (no emacsclient needed):

  • org-syntax.md - Complete org-mode syntax reference
  • properties.md - Property drawers and node properties
  • timestamps.md - Date/time formats, scheduling, deadlines
  • links.md - Internal and external link syntax
  • examples.md - Common formatting patterns

Org-roam Operations (via emacsclient):

  • emacsclient-usage.md - Detailed emacsclient patterns
  • org-roam-api.md - Org-roam API reference
  • functions.md - Complete function documentation
  • installation.md - Setup and configuration guide
  • troubleshooting.md - Common issues and solutions

Quick access patterns:

  • Need org-mode syntax? → references/org-syntax.md
  • Working with timestamps? → references/timestamps.md
  • Creating links? → references/links.md
  • Need installation help? → references/installation.md
  • Function parameters unclear? → references/functions.md
  • Something not working? → references/troubleshooting.md

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/org-roam-and-org-mode-management-mm8o51j1' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/org-roam-and-org-mode-management-mm8o51j1/download' --output '.skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md.part' && mv '.skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md.part' '.skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Original excerpt: Quick Reference

Prerequisites:

  • Emacs daemon running: emacs --daemon
  • org-roam installed in Emacs
  • Skill auto-loads on first use (no manual config needed)

Using the skill:

All operations use the auto-loading wrapper ${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval:

# Create note (tags MUST be a list, not string)
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-note \"Title\" :tags '(\"tag\") :content \"text\")"

# Create with large content (recommended for >1KB content)
TEMP=$(mktemp -t org-roam-content.XXXXXX)
echo "Large content..." > "$TEMP"
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-note \"Title\" :content-file \"$TEMP\")"
# Temp file auto-deleted!

# Search
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-search-by-title \"search-term\")"

# Backlinks
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-get-backlinks-by-title \"Note Title\")"

# Link notes
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-create-bidirectional-link \"Note A\" \"Note B\")"

# Attach file
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-skill-attach-file \"Note Title\" \"/path/to/file\")"

# Diagnostics
${CLAUDE_PLUGIN_ROOT}/skills/roam/scripts/org-roam-eval "(org-roam-doctor)"

Key principle: Package auto-loads on first call, then stays in memory - no repeated loading overhead.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md' && test -s '.skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/roam' && cp -R '.skill-downloads/org-roam-and-org-mode-management-mm8o51j1' '.claude/skills/roam'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/org-roam-and-org-mode-management-mm8o51j1'

openskills read 'org-roam-and-org-mode-management-mm8o51j1'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills