AI Agent Hub
Back to skills
Obsidian PARA Diary & Share Workflow icon

Obsidian PARA Diary & Share Workflow

Knowledge Management Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please install @user_788b463f/obsidian-cli-skill according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem It Solves

Obsidian vaults often fail less because notes are hard to capture and more because files scatter across projects, diary entries, references, and audience-facing copies. obsidian-cli-skill turns PARA, Diary, and Share into an executable workflow: locate the vault, then route content by purpose to 000-Sketch, 100-Projects, 200-Area, 300-Resources, 400-Archives, 900 - Diary, or Share.

How It Works

The skill first checks the Obsidian CLI environment, then provides concrete commands and Markdown templates. Typical steps include using obsidian vaults verbose to identify the target vault, initializing folder structure for a new vault, keeping the latest diary under 900 - Diary/, archiving older diary entries by month, placing outcome-driven work in 100-Projects/<project>/, distilling reusable knowledge into 200-Area or 300-Resources, and creating audience-ready copies in Share/ with source references.

Scope and Cautions

It is useful for CLI-assisted vault maintenance in engineering knowledge bases, not for generic note-taking advice. Move, overwrite, delete, restore, and bulk operations should be confirmed before execution. Share is an outward-facing copy area and should not replace the canonical note in Projects, Areas, or Resources.

Use Cases

  • Initialize a new Obsidian vault with PARA, Diary, and Share folders plus index notes.
  • Route a messy note to Sketch, Project, Area, or Resource based on its intended purpose.
  • Create a project workspace, entry template, and task-tracking notes for a new delivery.
  • Append weekly diary entries and archive diary files older than one month.

Best For

  • Engineers managing project knowledge in Obsidian and wanting PARA-based routing.
  • Knowledge managers turning project experience into reusable documentation.
  • Developers maintaining vaults via CLI and wanting fewer manual folder operations.
  • Technical writers converting internal notes into audience-ready share copies.