obsidian-organize

Organize Obsidian notes according to clawd's preferences. Use when user asks to "organize notes", "move notes to right folder", "clean up vault", "tidy vault", "file this note", or when creating new notes in the Obsidian vault. Also use when moving, renaming, or categorizing notes, or when the vault root has stray files.

6 stars

Best use case

obsidian-organize is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Organize Obsidian notes according to clawd's preferences. Use when user asks to "organize notes", "move notes to right folder", "clean up vault", "tidy vault", "file this note", or when creating new notes in the Obsidian vault. Also use when moving, renaming, or categorizing notes, or when the vault root has stray files.

Teams using obsidian-organize should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/obsidian-organize/SKILL.md --create-dirs "https://raw.githubusercontent.com/edwinhu/workflows/main/skills/obsidian-organize/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/obsidian-organize/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How obsidian-organize Compares

Feature / Agentobsidian-organizeStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Organize Obsidian notes according to clawd's preferences. Use when user asks to "organize notes", "move notes to right folder", "clean up vault", "tidy vault", "file this note", or when creating new notes in the Obsidian vault. Also use when moving, renaming, or categorizing notes, or when the vault root has stray files.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Obsidian Note Organization

Clawd's Obsidian vault follows the PARA method. Every note belongs in a specific folder — nothing lives in the vault root.

## Folder Structure

```
Vault/
├── 0. Inbox/              # Unsorted captures, quick notes
├── 1. Projects/           # Active projects with deadlines
├── 2. Areas/              # Ongoing responsibilities
├── 3. Resources/          # Reference material
│   ├── People/            # Notes about individuals
│   ├── References/        # Technical references (APIs, tools, comparisons)
│   ├── Concepts/          # Ideas, frameworks, mental models
│   └── ...                # Other resource categories as needed
├── 4. Archive/            # Completed/inactive items
└── Templates/             # Note templates
```

## Placement Rules

| Note Type | Folder | Example |
|-----------|--------|---------|
| Person (colleague, contact, public figure) | `3. Resources/People/` | `Jeffrey Peck - PSLRA Lobbyist.md` |
| API docs, tool guides, tech comparisons | `3. Resources/References/` | `Claude API - Streaming Responses.md` |
| Concepts, frameworks, mental models | `3. Resources/Concepts/` | `Efficient Market Hypothesis.md` |
| Active project with a deadline | `1. Projects/` | Current research, course prep |
| Ongoing responsibility (no end date) | `2. Areas/` | Teaching, health, finances |
| Quick capture, unsorted | `0. Inbox/` | To be filed later |
| Done, no longer active | `4. Archive/` | Past projects, old references |

## Naming Conventions

Titles should be descriptive and include context so they're findable without opening the note:

- **People**: `Full Name - Role or Context.md` (e.g., `Jeffrey Peck - PSLRA Lobbyist.md`)
- **References**: `Tool/Topic - Specific Aspect.md` (e.g., `jq - Container Compatibility Notes.md`)
- **Projects**: Use the project's natural name

Avoid generic titles like `Meeting Notes.md` or `Ideas.md` — add the date, person, or topic.

## Vault Hygiene

- The vault root directory should contain **only folders**, never loose notes
- If a note doesn't clearly fit a subcategory, place it in the parent PARA folder (e.g., `3. Resources/`) rather than the root
- When in doubt, `0. Inbox/` is the right temporary home — but follow up by filing it properly
- Periodically move completed projects from `1. Projects/` to `4. Archive/`

Related Skills

writing

6
from edwinhu/workflows

This skill should be used when the user asks to 'write a paper', 'start a writing project', 'draft an article', 'write about', 'brainstorm writing topics', 'gather sources for a paper', 'what should I write about', or needs the writing workflow entry point for any writing task.

writing-validate

6
from edwinhu/workflows

Validate draft sections cover all PRECIS claims before review.

writing-setup

6
from edwinhu/workflows

Internal skill for creating PRECIS.md, OUTLINE.md, and ACTIVE_WORKFLOW.md. Called after brainstorm sources are gathered.

writing-revise

6
from edwinhu/workflows

This skill should be used when the user asks to 'revise writing', 'fix review issues', 'polish draft', 'apply review feedback', 'complete writing workflow', or after /writing-review produces REVIEW.md with issues to fix.

writing-review

6
from edwinhu/workflows

Internal skill for hierarchical document review. Called by writing-validate after claim validation passes.

writing-precis-reviewer

6
from edwinhu/workflows

Internal skill used by writing-setup at exit gate. Dispatches a reviewer subagent to verify PRECIS.md quality before outlining. NOT user-facing.

writing-outline

6
from edwinhu/workflows

Internal skill for creating detailed section outlines. Called by /writing workflow after PRECIS and master OUTLINE are complete.

writing-outline-reviewer

6
from edwinhu/workflows

Internal skill used by writing-outline at exit gate. Dispatches a reviewer subagent to verify OUTLINE.md quality before drafting. NOT user-facing.

writing-lit-review

6
from edwinhu/workflows

Internal skill for literature review and source materialization. Called after brainstorm, before setup. NOT user-facing.

writing-legal

6
from edwinhu/workflows

Internal skill for academic legal writing. Loaded by /writing when style=legal. Based on Volokh's "Academic Legal Writing".

writing-handoff

6
from edwinhu/workflows

Create structured handoff document for writing workflow session pause/resume.

writing-general

6
from edwinhu/workflows

Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.