orgmode

Provide concise org-mode syntax guidance for writing and formatting .org files.

35|8|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/majorgreys/claude-orgmode --skill orgmode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orgmode
Source: https://github.com/majorgreys/claude-orgmode/tree/main/skills/orgmode
Command: npx skills add https://github.com/majorgreys/claude-orgmode --skill orgmode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Org-mode users need quick, reliable guidance on writing and formatting .org files, including headings, lists, links, properties, and timestamps.

Core Features & Use Cases

  • Comprehensive org-mode syntax reference for headings, lists, links, properties, timestamps, blocks, and tables.
  • Quick-instruction style examples for everyday note-taking, outlining, and project planning with org-roam or vulpea integration.
  • Real-world scenarios showing how to apply org-mode formatting to notes, tasks, and documentation.

Quick Start

Describe how to format a three-level heading in org-mode with a TODO on the second level.

Frequently Asked Questions about orgmode

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

FAQPage Schema
How do I format headings and TODO items in org-mode?

Org-mode formatting uses asterisks for headings, with TODO keywords placed immediately after the asterisks. A three-level heading requires three asterisks, and a TODO item is created by adding TODO before the heading text for plain-text task tracking.

What is the correct syntax for creating links and lists in .org files?

Org-mode links use double square brackets like `[[target][description]]` for URLs or internal references. Lists are created with hyphens, plus signs, or numbers followed by a space, maintaining plain-text readability while supporting structured notes.

How do I add properties and timestamps to org-mode notes?

Org-mode properties are defined within `:PROPERTIES:` drawers beneath headings using key-value pairs. Timestamps use angle brackets like `<2024-01-15 Mon>` for scheduling, enabling quick-reference usage and integration with org-roam or vulpea for project planning.

Can I create tables and code blocks in org-mode for documentation?

Org-mode tables use pipe characters to define columns and rows for structured data. Code blocks are enclosed within `#+begin_src` and `#+end_src` tags, supporting language-specific syntax highlighting and edge-case formatting rules for comprehensive documentation.

What are common pitfalls when writing org-mode syntax?

Common org-mode pitfalls include missing spaces after list markers, incorrect property drawer placement, and malformed link syntax. The syntax requires strict adherence to plain-text formatting rules, ensuring quick-reference usability and compatibility with org-roam or vulpea integrations.

Does org-mode syntax work with org-roam and vulpea for note-taking?

Org-mode syntax fully supports org-roam and vulpea integration for everyday note-taking and outlining. The plain-text formatting rules for headings, links, and properties apply directly, enabling real-world scenarios for networked notes and project planning without syntax conflicts.