denote-org

Parse Denote filenames and frontmatter into structured JSON metadata.

12|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/junghan0611/org-mode-skills --skill denote-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: denote-org
Source: https://github.com/junghan0611/org-mode-skills/tree/main/.
Command: npx skills add https://github.com/junghan0611/org-mode-skills --skill denote-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires orgparse, pypandoc, pyyaml, networkx, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Without this skill, Claude struggles to navigate large Denote-based Personal Knowledge Management (PKM) systems, understand complex Org-mode structures, and efficiently manage thousands of interlinked notes. This leads to slow searches, token-heavy operations, and errors in knowledge graph traversal or code execution. This skill provides Claude with the specialized domain knowledge and executable tools to automate these complex tasks, saving you significant time and reducing cognitive load.

Core Features & Use Cases

  • Denote Knowledge Management: Efficiently find files by ID or tags, resolve [[denote:ID]] links, and manage multiple knowledge silos (e.g., ~/org/, ~/claude-memory/).
  • Knowledge Graph Navigation: Build and traverse knowledge graphs across thousands of Org files, revealing hidden connections and insights within your personal knowledge base.
  • Literate Programming: Safely execute Org-mode code blocks with :tangle and :results options, automating tasks directly within your notes and ensuring structural integrity.
  • Use Case: Ask Claude to "Find all files linked to 20251021T105353" or "Execute the bash blocks in this Org file" to instantly get results and automate complex knowledge operations across your 3,000+ file PKM system.

Quick Start

To find a Denote file by its identifier in your main Org silo: from scripts.denote_finder import find_denote_file filepath = find_denote_file("20251021T105353", silos=["~/org/"]) # Returns: ~/org/llmlog/20251021T105353--full-filename.org

Frequently Asked Questions about denote-org

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search and retrieve files from a large Denote PKM system with thousands of notes?

Denote file retrieval automates finding notes by ID or tags across your knowledge base. This Skill parses Denote filenames and frontmatter to extract structured metadata, then returns matching files as JSON—enabling fast lookups across multi-silo setups like ~/org/notes, ~/org/bib, and ~/org/journal without manual searching.

Can I traverse knowledge graphs and follow [[denote:ID]] links across my Org files?

Knowledge graph navigation resolves denote: links and builds interconnected maps across your Org-mode repository. This Skill follows link relationships to surface hidden connections, extract org TOCs, and reveal insights within your PKM system—essential for understanding how thousands of interlinked notes relate.

How do I automate code execution from Org-mode files with :tangle and :results options?

Literate programming execution safely runs code blocks embedded in Org files with :tangle and :results directives. This Skill parses and executes bash and other blocks while preserving structural integrity, automating complex knowledge operations directly from your notes.

What file formats and metadata do I need to prepare before using this Skill?

Org-mode files with Denote naming conventions (timestamp--title--tags.org) and frontmatter are required input. The Skill handles Unicode and Korean filenames, parses YAML/org frontmatter, and outputs JSON metadata—no special preprocessing needed beyond standard Denote repository structure.

Does this Skill integrate with downstream RAG pipelines and batch processing workflows?

Yes, CLI-driven scripts output structured JSON metadata designed for batch processing and RAG integration. The Skill supports multi-silo configurations and scales to 3,000+ file repositories, feeding extracted knowledge graphs and structured data into downstream analysis and retrieval pipelines.

Why would parsing Denote filenames and org-mode structure reduce token usage in Claude interactions?

Manual exploration of large PKM systems requires Claude to read raw files, losing efficiency through redundant parsing and token-heavy operations. Extracting lightweight org TOCs and structured metadata upfront reduces the input needed per query, saving tokens while improving search accuracy across your knowledge base.