obsidian-workflows_skill

Overview

This skill explains how to build and maintain a second brain in Obsidian using the PARA method, progressive summarization, and practical PKM workflows. It focuses on action-oriented organization, linking strategies, and review cadences to keep a vault useful and low-maintenance. Use it to create predictable capture, processing, and expression routines that scale with your work.

How this skill works

The skill inspects your workflow patterns and recommends folder layouts, tagging conventions, and linking habits that align with PARA (Projects, Areas, Resources, Archives). It guides note construction (atomic and evergreen notes), MOC creation, and progressive summarization layers to distill value over time. It also prescribes review cadences and templates to automate daily/weekly processing and maintain link health.

When to use it

• Setting up a new Obsidian vault or migrating an existing one
• Designing capture and weekly processing workflows
• Creating Maps of Content (MOCs) or vault dashboards
• Improving note discoverability and reducing orphaned notes
• Standardizing templates, tags, and metadata

Best practices

• Use a simple PARA folder hierarchy with an Inbox capture zone and numeric prefixes for sidebar order
• Create one atomic idea per note; use descriptive titles and 100–500 word evergreen structure
• Apply the 2-link rule: link every new note to at least two existing notes to avoid orphans
• Use MOCs for curated navigation and dashboards for automated system views; keep them separate
• Run regular review cadences: daily quick checks, weekly inbox processing, monthly area review, quarterly cleanup

Example use cases

• Weekly /process-inbox routine: empty Inbox, enrich notes, move to Projects/Areas/Resources
• Create an evergreen note template to track definition, related links, and encounters
• Build a Master MOC that links key areas and entry points for onboarding or research
• Use progressive summarization to turn long highlights into a 2–3 sentence executive summary at the top of each note
• Daily-startup pattern: open daily note, link active projects, and capture quick tasks