How do I install the Obsidian skill?

Run npx skillmds@latest add justincordova/obsidian in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Obsidian safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Obsidian?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Obsidian free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Obsidian?

justincordova (@justincordova) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Obsidian by justincordova — Agent Skill

Name: Obsidian
Author: justincordova

Obsidian

Use when creating, editing, or organizing notes in the Obsidian vault — daily notes, meeting notes, project notes, or links between them. Covers naming, structure, linking, and when a note is worth writing at all.

File contents

Obsidian Notes

Vault Location

All notes live in the Obsidian vault. Don't create notes outside it unless explicitly asked.

Naming Conventions

Use lowercase with hyphens: project-planning.md, not Project Planning.md
Be descriptive: api-rate-limiting-design.md, not notes.md
Date-prefix daily/weekly notes: 2026-04-17.md
Date-prefix meeting notes: 2026-04-17-design-review.md

Structure

One idea per note. If a note covers two things, split it.
Lead with context: what is this, why does it exist.
Use headings for scanning. Keep paragraphs short.

Linking

Link liberally: [[note-name]] for any concept or project mentioned.
Don't orphan notes. Every note should link to or be linked from something.
Use MOCs (Maps of Content) for broad topics that tie many notes together.

Project Notes

Create a project note for any project that spans more than one session.
Include: goal, key decisions, architecture overview, links to related notes.
Update the project note as the project evolves — it's the living summary.

Meeting Notes

Capture decisions and action items, not transcripts.
Format action items as checkboxes: - [ ] Action item here
Link to project notes and people notes.

When to Create Notes

After a design decision is made
When learning something non-obvious
When a debugging session reveals something worth remembering
When a project's scope or direction changes
When context is getting large and needs to be offloaded

When NOT to Create Notes

For trivial information easily googled
For things already well-documented elsewhere
During active implementation (notes are for after, not during)

---name: obsidiandescription: Use when creating, editing, or organizing notes in the Obsidian vault — daily notes, meeting notes, project notes, or links between them. Covers naming, structure, linking, and when a note is worth writing at all.---# Obsidian Notes## Vault LocationAll notes live in the Obsidian vault. Don't create notes outside it unless explicitly asked.## Naming Conventions- Use lowercase with hyphens: `project-planning.md`, not `Project Planning.md`- Be descriptive: `api-rate-limiting-design.md`, not `notes.md`- Date-prefix daily/weekly notes: `2026-04-17.md`- Date-prefix meeting notes: `2026-04-17-design-review.md`## Structure- One idea per note. If a note covers two things, split it.- Lead with context: what is this, why does it exist.- Use headings for scanning. Keep paragraphs short.## Linking- Link liberally: `[[note-name]]` for any concept or project mentioned.- Don't orphan notes. Every note should link to or be linked from something.- Use MOCs (Maps of Content) for broad topics that tie many notes together.## Project Notes- Create a project note for any project that spans more than one session.- Include: goal, key decisions, architecture overview, links to related notes.- Update the project note as the project evolves — it's the living summary.## Meeting Notes- Capture decisions and action items, not transcripts.- Format action items as checkboxes: `- [ ] Action item here`- Link to project notes and people notes.## When to Create Notes- After a design decision is made- When learning something non-obvious- When a debugging session reveals something worth remembering- When a project's scope or direction changes- When context is getting large and needs to be offloaded## When NOT to Create Notes- For trivial information easily googled- For things already well-documented elsewhere- During active implementation (notes are for after, not during)

Frequently asked questions