Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From mem8
Expert guidance for working with Obsidian vaults including Obsidian Flavored Markdown (OFM) syntax, organization best practices, daily/weekly task workflows, vault maintenance, and automation. This skill should be used when working with Obsidian notes, organizing vault structure, setting up task management workflows, or integrating with Obsidian tooling.
npx claudepluginhub killerapp/mem8-plugin --plugin mem8How this skill is triggered — by the user, by Claude, or both
Slash command
/mem8:obsidian-skillThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides expert guidance for working with Obsidian vaults, enabling effective knowledge management through proper syntax usage, organizational best practices, and workflow automation. It covers Obsidian Flavored Markdown (OFM), modern organization methodologies, task management workflows, and integration with Claude Code.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
This skill provides expert guidance for working with Obsidian vaults, enabling effective knowledge management through proper syntax usage, organizational best practices, and workflow automation. It covers Obsidian Flavored Markdown (OFM), modern organization methodologies, task management workflows, and integration with Claude Code.
Use this skill when:
Obsidian extends standard Markdown with wiki-inspired features:
Wikilinks (Internal Linking):
[[Note Name]] - Link to another note[[Note Name|Display Text]] - Custom display text[[Note#Heading]] - Link to specific heading[[Note^block-id]] - Link to specific block^block-id at end of any line to create referenceable blocksEmbeds (Transclusion):
![[Note]] - Embed entire note![[Note#Heading]] - Embed from heading onwards![[Note^block-id]] - Embed specific block![[Image.jpg]] - Embed media filesCallouts:
> [!note] Optional Title
> Content here
Types: note, tip, info, todo, warning, danger, error, bug, example, abstract, success, question, failure, important, quote
Collapsible: [!tip]+ (expanded) or [!tip]- (collapsed)
Tags:
#tag - Basic tag#parent/child/grandchild - Nested hierarchyComments:
%% Hidden comment %% - Obsidian-only, not portableHighlights:
==highlighted text== - Obsidian-specificProperties/Frontmatter:
---
title: Note Title
date: 2025-11-12
tags: [tag1, tag2]
status: active
---
Math (LaTeX):
$E = mc^2$$$equation$$Diagrams (Mermaid):
```mermaid
graph LR
A --> B --> C
```
Dataview Queries (if plugin installed):
```dataview
TABLE rating, date
FROM #books
SORT rating DESC
```
For complete syntax details, refer to references/ofm-syntax.md.
ACE Framework (Recommended):
Atlas/ # Knowledge maps, ideas, reference materials
Calendar/ # Daily notes, periodic notes, time-based entries
Efforts/ # Projects, goals, active work
FINVA System (Workflow-based):
Fleeting/ # Quick rough notes (weekly review)
In Progress/ # Projects needing work
Notes/ # Permanent completed notes
Views/ # MOCs and organizational notes
Archives/ # Old projects
Zettelkasten (Research-focused):
Fleeting/ # Temporary captures
Permanent/ # Atomic evergreen notes
MOCs are index notes that link to related notes:
# Topic Name
## Overview
Brief description
## Subtopic 1
- [[Note 1]]
- [[Note 2]]
## Subtopic 2
- [[Note 3]]
- [[Note 4]]
Create MOCs when:
For detailed organization strategies, refer to references/organization-guide.md.
Daily note template available at assets/templates/daily-note.md
Weekly review template available at assets/templates/weekly-review.md
Project template available at assets/templates/project.md
- [ ] Basic task
- [ ] Task with due date =Å 2025-11-15
- [ ] High priority task ë
- [ ] Recurring task = every week
Use Day Planner plugin with 24-hour format:
## Today's Schedule
- [ ] 07:00 Morning Routine
- [ ] 08:00 Deep Work - Project X
- [ ] 10:00 Team Meeting
For complete workflow details, refer to references/task-workflows.md.
When performing vault health checks:
Find broken links:
[[wikilinks]]Find orphaned notes:
Check frontmatter completeness:
Find duplicate titles:
Identify stubs:
Use scripts/vault_health.py for automated health checks.
When organizing notes:
Analyze content:
Suggest improvements:
Get approval:
When performing batch operations:
Always preview changes first:
Process in batches:
Preserve Obsidian syntax:
Backup reminder:
Always ensure:
Frontmatter is present and complete:
---
title: Note Title
created: YYYY-MM-DD
tags: [relevant, tags]
---
First heading matches title:
# Note Title
Wikilinks are properly formatted:
[[Note Name]] not [Note Name](note-name.md)Appropriate callouts for key info:
> [!important]
> Critical information here
Related notes are linked:
Tags follow convention:
#category/subcategoryFor AI-assisted vault management:
npx -y @smithery/cli install mcp-obsidian --client claudeRecommend users create CLAUDE.md in vault root with:
Example vault context file available at assets/templates/CLAUDE.md
obsidian_read_note - Read content and metadataobsidian_global_search - Search entire vaultobsidian_update_note - Append, prepend, or overwriteobsidian_manage_frontmatter - Get/set YAML metadataobsidian_manage_tags - Add/remove tagsFor complete tooling reference, see references/tools-and-automation.md.
obsidian-metadata CLI for bulk updates, enforce template usageFor comprehensive details on specific topics, refer to:
references/ofm-syntax.md - Complete OFM syntax guidereferences/organization-guide.md - Detailed organization strategiesreferences/task-workflows.md - Complete workflow implementationsreferences/tools-and-automation.md - CLI tools and automation guideTemplates and assets available in assets/templates/.