Obsidian

Custom skills and prompts for Claude Code based on my personal workflows.

Install

npx -y skills add Sean-Michael/skills --skill obsidian

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Interact with an Obsidian vault using the official Obsidian CLI. Trigger when asked to read, write, search, or organize vault content, capture a decision or gotcha, log to a daily note, or reorganize notes. Also trigger on "make a note of that", "log that", "update my vault".

SKILL.md

3.1 KB, as published. Nobody here has run it

Obsidian CLI

Always use the CLI over direct .md file edits — it runs through Obsidian's runtime so move updates links, create applies templates, property:set writes valid frontmatter.

Run obsidian help to discover commands. Run obsidian help <command> for params.

file=<n> resolves like a wikilink — no path or extension needed.
path=<path> requires exact path from vault root.

Vault Structure (PARA)

Organize vaults using PARA:

Vault/
├── Projects/    # active work with a defined end state
├── Areas/       # ongoing responsibilities, no end date
├── Resources/   # reference material, things learned
├── Archive/     # completed or dead projects
├── Daily Notes/
├── Templates/
└── Attachments/

Projects vs Areas: Projects have a finish line and move to Archive when done. Areas are permanent responsibilities that never "end".

Meeting notes live inside the relevant project folder, not a global folder.

Project Note Structure

Path: Projects/<Project>/<Project>.md

---
project: <name>
status: active
updated: <YYYY-MM-DD>
tags: [project]
---

# <Project Name>

## What & Why
What this is and why it exists.

## Current Status
Where things are right now.

## Decisions & Tradeoffs
- **<decision>** — why, and what was rejected

## Gotchas & Lessons
- Things that bit you or future-you needs to know

## Open Questions
- Unresolved things

Daily Note

Append tasks and quick references rather than creating new notes for small things:

obsidian daily:append content="- [ ] Task here"
obsidian daily:append content="- [[Project]] — note for references section"

PKM Conventions

Wikilink liberally. Any time a known project, person, or concept appears in a note, link it: [[Project Name]], [[Person]].

Check before creating. A note may already exist:

obsidian search query="<topic>" limit=5

Shallow structure. No nesting beyond Projects/<Project>/ except a Meeting Notes/ subfolder per project if needed.

Small tag set. Stick to: project, area, resource, decision, gotcha, question. Don't invent tags without a clear reason.

Archiving. Move don't delete:

obsidian move file="<Project>" to="Archive/"
obsidian property:set name=status value=done file="<Project>"

When "Make a Note of That"

Identify type:
- Decision/tradeoff/gotcha → append to project note
- Task → obsidian daily:append
- Meeting → Projects/<Project>/Meeting Notes/<date> <topic>.md
- Reference → Resources/<topic>.md
Check the target exists before appending
Create if missing, append if it exists
Update updated frontmatter with today's date
Confirm what was written and where