obsidian-1-vault-structure-and-organization

Sub-skill of obsidian: 1. Vault Structure and Organization (+1).

5 stars

Best use case

obsidian-1-vault-structure-and-organization is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of obsidian: 1. Vault Structure and Organization (+1).

Teams using obsidian-1-vault-structure-and-organization should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/1-vault-structure-and-organization/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/business/productivity/obsidian/1-vault-structure-and-organization/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/1-vault-structure-and-organization/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How obsidian-1-vault-structure-and-organization Compares

Feature / Agentobsidian-1-vault-structure-and-organizationStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Sub-skill of obsidian: 1. Vault Structure and Organization (+1).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 1. Vault Structure and Organization (+1)

## 1. Vault Structure and Organization


**PARA Method Structure:**
```markdown
# Vault Organization with PARA Method
#
# Projects/ - Active projects with deadlines
# Areas/    - Ongoing responsibilities
# Resources/- Reference materials
# Archive/  - Completed or inactive items

# Example folder structure:
ObsidianVault/
├── Daily Notes/           # Daily journal entries
├── Inbox/                 # Quick capture, process later
├── Projects/
│   ├── Project-Alpha/
│   │   ├── Overview.md
│   │   ├── Tasks.md
│   │   └── Meeting Notes/
│   └── Project-Beta/
├── Areas/
│   ├── Health/
│   ├── Finance/
│   ├── Career/
│   └── Learning/
├── Resources/
│   ├── Books/
│   ├── Courses/
│   ├── Articles/
│   └── Recipes/
├── Archive/
│   └── 2025-Q1/
├── Templates/
│   ├── Daily Note.md
│   ├── Meeting Note.md
│   ├── Project.md
│   └── Book Note.md
└── Attachments/
    └── images/
```

**Zettelkasten Structure:**
```markdown
# Zettelkasten-style vault
ObsidianVault/
├── 0-Inbox/               # Fleeting notes
├── 1-Literature Notes/    # Notes from sources
├── 2-Permanent Notes/     # Your own ideas
├── 3-Structure Notes/     # MOCs (Maps of Content)
├── 4-Projects/            # Project-specific notes
└── Templates/
```

**Naming Conventions:**
```markdown
# Date-based naming for daily notes
Daily Notes/2025-01-17.md

# Timestamp-based for Zettelkasten
202501171430 - Concept Name.md

# Descriptive naming for permanent notes
How to Structure a Knowledge Base.md

# Project-prefixed naming
Project-Alpha - Meeting 2025-01-17.md

# Use lowercase with hyphens for consistency
my-note-about-something.md
```


## 2. Linking and Backlinking


**Basic Linking:**
```markdown
# Internal links
[[Note Name]]
[[Note Name|Display Text]]
[[Folder/Subfolder/Note Name]]

# Link to heading
[[Note Name#Heading Name]]
[[Note Name#Heading Name|Custom Text]]

# Link to block
[[Note Name#^block-id]]

# Embed notes
![[Note Name]]
![[Note Name#Heading]]
![[image.png]]
![[document.pdf]]

# External links
[External Link](https://example.com)
```

**Block References:**
```markdown
# In source note (Source Note.md)
This is an important concept. ^important-concept

This paragraph explains something crucial about the topic.
It spans multiple lines. ^key-explanation

# In referencing note
As mentioned in [[Source Note#^important-concept]], this concept is key.

# Embed the block
![[Source Note#^important-concept]]
```

**Linking Best Practices:**
```markdown
# Note: The Power of Compound Interest.md

Related Skills

repo-structure

5
from vamseeachanta/workspace-hub

Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.

github-issue-structure-for-personal-finance-tracking

5
from vamseeachanta/workspace-hub

Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)

repo-cleanup-structure-section-updates

5
from vamseeachanta/workspace-hub

Sub-skill of repo-cleanup: Structure Section Updates (+1).

discipline-refactor-target-repository-structure

5
from vamseeachanta/workspace-hub

Sub-skill of discipline-refactor: Target Repository Structure.

discipline-refactor-standard-folders-module-structure

5
from vamseeachanta/workspace-hub

Sub-skill of discipline-refactor: Standard Folders → Module Structure (+1).

mkdocs-3-navigation-structure

5
from vamseeachanta/workspace-hub

Sub-skill of mkdocs: 3. Navigation Structure (+2).

interactive-menu-builder-1-basic-menu-structure

5
from vamseeachanta/workspace-hub

Sub-skill of interactive-menu-builder: 1. Basic Menu Structure.

repo-structure-never-tests-inside-src

5
from vamseeachanta/workspace-hub

Sub-skill of repo-structure: NEVER: tests/ inside src/ (+7).

repo-structure-gitignore-enforcement-root-level-output-artifacts

5
from vamseeachanta/workspace-hub

Sub-skill of repo-structure: Gitignore Enforcement: Root-Level Output Artifacts.

repo-structure-compliance-quick-check

5
from vamseeachanta/workspace-hub

Sub-skill of repo-structure: Compliance Quick-Check.

repo-structure-canonical-structure

5
from vamseeachanta/workspace-hub

Sub-skill of repo-structure: Canonical Structure (+1).

repo-structure-allowed-in-docs

5
from vamseeachanta/workspace-hub

Sub-skill of repo-structure: Allowed in docs/ (+1).