Gestion Org-roam et Org-mode

VérifiéPrudence

Cette compétence offre une gestion complète des notes org-roam et du formatage Org-mode via emacsclient. Elle permet de créer, rechercher et lier des notes, générer des rétroliens et attacher des fichiers. Utilisez-la lorsque vous travaillez avec des notes org-roam pour éviter d'endommager la base de données ou les rétroliens.

Spar Skills Guide Bot
ProductiviteIntermédiaire
02/06/2026
Claude Code
#org-roam#org-mode#emacs#note-taking#knowledge-management

Recommandé pour

Synthèse automatique

Cette compétence gère les notes org-mode et org-roam via emacsclient, permettant la création, la recherche, la liaison et l'analyse de backlinks sans édition directe des fichiers.

Points forts

  • S'intègre avec le démon Emacs en cours pour la cohérence de la base de données
  • Prend en charge les tags, le contenu et les pièces jointes
  • Offre la recherche et les backlinks
  • Évite la corruption de la base de données en utilisant des scripts dédiés

Limites

  • Nécessite que le démon Emacs soit en cours d'exécution et org-roam configuré
  • Ne fonctionne qu'avec une configuration Emacs locale
  • Les commandes sont limitées aux fonctions prédéfinies
Quand l'utiliser

Utilisez cette compétence lorsque vous devez créer, lier ou rechercher des notes org-roam tout en garantissant l'intégrité de la base de données et en évitant la manipulation directe des fichiers.

Quand l'éviter

Ne l'utilisez pas pour modifier des fichiers org non-roam, ou si le démon Emacs n'est pas disponible, ou pour de simples notes textuelles en dehors d'une base de connaissances org-roam.

Analyse de sécurité

Prudence
Score qualité90/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.

Points d'attention
  • •Arbitrary Elisp execution allowed via org-roam-eval script, which could be leveraged for destructive or exfiltrating actions if the model is manipulated.
Comment cette analyse est faite

Exemples

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

Du fichier au premier essai

Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.

Consulter la source et ses fichiers annexes

Ce téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.

1. Télécharger le fichier

Télécharger SKILL.md

Depuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.

Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.

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. Vérifier les prérequis

Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.

Extrait original : 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.

Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.

3. Charger la skill

Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.

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 doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.

Installation officielle d’OpenSkills
openskills install './.skill-downloads/org-roam-and-org-mode-management-mm8o51j1'

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

La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.

Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.

openskills sync

Mode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.

4. Faire un premier essai

Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :

Lis .skill-downloads/org-roam-and-org-mode-management-mm8o51j1/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.

Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.

Skills similaires