# Organize Obsidian Notes with PARA Method

Claude users struggle to organize their Obsidian notes consistently. This skill provides automated PARA classification, routing, and vault hygiene reviews to keep knowledge bases organized without manual effort.

## Install

```bash
npx skillstore add scifishelf/para-skill
```

## Metadata

- - Slug: scifishelf-para-skill
- - Version: 1.0.0
- - Author: scifishelf
- - GitHub username: scifishelf
- - License: MIT
- - Repository: https://github.com/scifishelf/para-skill/tree/main/
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: safe
- - Risk factors: external\_commands, network
- - Quality score: 82
- - Quality tier: silver
- - Public page: https://skillstore.pages.dev/skills/scifishelf-para-skill
- - Manifest: https://skillstore.pages.dev/api/skills/scifishelf-para-skill/manifest

## Capabilities

- Classify any note into PARA categories \(Projects, Areas, Resources, Archive\) with confidence scoring
- Route notes to correct vault folders with optional dry-run mode
- Normalize frontmatter with PARA-specific fields without touching existing content
- Run vault hygiene reviews to identify stale notes, inbox backlogs, and archiving candidates
- Perform full vault audits for missing metadata, wrong placement, and orphaned notes
- Suggest defensive archiving with proper metadata preservation

## Use Cases

- Organize Meeting Notes Automatically: Capture new meeting notes and have Claude classify them into the correct PARA category, add appropriate frontmatter, and route to the right folder in the vault.
- Quarterly Vault Cleanup: Run a comprehensive hygiene review to identify stale projects, outdated areas, and archiving candidates. Get a prioritized action list for vault maintenance.
- Note Classification Assistant: Ask Claude where a specific note belongs in the PARA structure. Get classification reasoning with confidence level before any changes are made.

## Prompt Templates

### Classify a Note

```
Classify this note into the correct PARA category. Read the note content and determine if it belongs in Projects, Areas, Resources, or Archive. Explain your reasoning with at least 2 supporting signals.

Note content:
{NOTE_CONTENT}
```

### Run Vault Review

```
Run a PARA hygiene review on my Obsidian vault. Check for: projects without next steps, stale areas, inbox backlog, and archiving candidates. Provide a prioritized action list.
```

### Capture New Note

```
Process this new content using the PARA method. Classify it, suggest the correct folder path, and create appropriate frontmatter.

Content to capture:
{CONTENT}
```

### Normalize Frontmatter

```
Normalize the frontmatter of this note. Add missing PARA-specific fields (para_type, status, confidence, needs_review) without removing or modifying existing non-PARA fields.

Note path: {NOTE_PATH}
```

## Limitations

- Does not create or modify note body content - only handles classification and frontmatter
- Requires existing Obsidian vault structure - cannot initialize a new vault from scratch
- Depends on note content quality for accurate classification - ambiguous notes need manual review
- Cannot access or manage Dataview queries, plugins, or Obsidian-specific configurations

## Best Practices

- Use cautious mode \(default\) for the first few interactions to understand the classification logic before enabling automatic moves
- Review the classification reasoning to learn what signals the skill uses - this improves your note-writing for future classifications
- Run quarterly hygiene reviews to prevent vault drift and maintain long-term organization

## Anti Patterns

- Using aggressive mode without understanding the classification criteria first - may misclassify ambiguous notes
- Ignoring the confidence score and forcing classifications when confidence is low
- Running full vault audits on very large vaults without breaking into smaller sections first

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-03-17T15:45:15.034\+00:00
- - Summary: All 205 static findings are false positives. The skill is a documentation-only PARA method implementation for Obsidian vault organization. Detected patterns \(backtick formatting, URLs, audit keywords\) are all benign documentation elements. No actual code execution, malicious network calls, or cryptographic operations exist in this skill.

## Stats

- - Views: 269
- - Downloads: 7
- - Favorites: 0
- - Popularity score: 0