← ClaudeAtlas

para-skilllisted

PARA method knowledge management for Obsidian vaults. Use this skill whenever the user wants to organize notes using PARA (Projects, Areas, Resources, Archive), classify a note into a PARA category, route a note to the right vault folder, normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit vault structure, or process new knowledge inputs into an existing PARA-based vault. Also trigger when the user mentions inbox processing, vault cleanup, note classification, PARA review, or asks "where does this note belong?". Works with existing Obsidian skills (obsidian-markdown, obsidian-cli) — never replaces them.
aiskillstore/marketplace · ★ 329 · Data & Documents · score 79
Install: claude install-skill aiskillstore/marketplace
# PARA Obsidian Skill ## What this skill does This skill provides PARA-method decision logic for Obsidian vaults. It decides **where** notes belong, **when** to archive, and **how** to keep the vault healthy — while leaving file creation, markdown formatting, and Obsidian syntax to the installed base skills. PARA is an organizational framework by Tiago Forte that structures information by **action relevance**, not topic: - **Projects** — concrete initiatives with a goal and an endpoint - **Areas** — ongoing responsibilities with no fixed end date - **Resources** — reference knowledge for potential future use - **Archive** — completed, paused, or inactive content Read `references/classification-rules.md` for detailed classification heuristics. --- ## Vault Configuration Default paths for this vault (override in conversation if different): ```yaml paths: inbox: "0_Inbox" # created on demand if missing projects: "1_Projects" areas: "2_Areas" resources: "3_Resources" archive: "4_Archives" ``` Default mode: **cautious** — suggest first, act only when confident or explicitly asked. --- ## Core Workflow For every PARA-related task, follow this sequence: 1. **Read** the note content, title, existing frontmatter, tags, and current file path 2. **Collect signals** — look for project indicators (deadlines, tasks, goals), area indicators (ongoing, recurring), resource indicators (reference, no action pressure), archive indicators (done, cancelled, historic