Agent skill · writing content · aiskillstore
para-skill
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.
Why this skill is useful
Provides specific PARA classification heuristics and decision logic for organizing notes in Obsidian that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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): 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, historical) 3. Check conventions — respect existing paratype frontmatter; existing folder placement is a strong signal 4. Classify with a confidence level: high, medium, or low 5. Plan frontmatter additions — only add fields from the schema, never overwrite non-PARA fields 6. Propose routing — suggest the target path 7. Assess risk — only act directly when confidence is high AND the user has given explicit permission or the mode is balanced/aggressive 8. Log changes when writing anything When in doubt: set needsreview: true, place in Inbox, and explain why. See references/classification-rules.md for the full decision tree. --- Available Actions capture — Process new content Accept raw text, meeting notes, ideas, or document descriptions. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/para-skill