obsidian-vault-management
Creates, edits, and manages Obsidian vault content including notes, templates, daily notes, and dataview queries. Use when working with markdown files in an Obsidian vault, creating notes, writing templates, building dataview queries, or organizing knowledge management content.
What this skill does
# Obsidian Vault Management
## Vault Structure (PARA-Based)
This vault uses a PARA-like organization:
| Folder | Purpose |
|--------|---------|
| `00 - Maps of Content` | Index notes linking related topics |
| `01 - Projects` | Active project notes |
| `02 - Areas` | Ongoing responsibilities |
| `03 - Resources` | Reference materials |
| `04 - Permanent` | Evergreen/zettelkasten notes |
| `05 - Fleeting` | Quick capture notes |
| `06 - Daily` | Daily notes (YYYY/MM/YYYYMMDD.md) |
| `07 - Archives` | Completed/inactive content |
| `08 - books` | Book notes and clippings |
| `99 - Meta` | Templates, settings |
| `Clippings` | Web clips and imports |
## Quick Reference
### Linking Syntax
```markdown
[[Note Name]] # Basic wikilink
[[Note Name|Display Text]] # Aliased link
[[Note Name#Heading]] # Link to heading
[[Note Name#^block-id]] # Link to block
![[Note Name]] # Embed note
![[image.png]] # Embed image
![[Note Name#Heading]] # Embed section
```
### Frontmatter Template
```yaml
---
created: {{date:YYYY-MM-DDTHH:mm}}
updated: {{date:YYYY-MM-DDTHH:mm}}
title: "Note Title"
type: note
status: draft
tags:
- tag1
- tag2
aliases:
- "Alternate Name"
cssclasses:
- custom-class
---
```
### Callouts
```markdown
> [!note] Title
> Content
> [!warning] Important
> Warning content
> [!tip] Helpful tip
> Tip content
> [!info]+ Collapsible (open by default)
> Content
> [!danger]- Collapsed by default
> Content
```
**Available callout types**: note, abstract, info, todo, tip, success, question, warning, failure, danger, bug, example, quote
## Creating Notes
### Daily Note
Create in `06 - Daily/YYYY/MM/` with filename `YYYYMMDD.md`:
```yaml
---
created: 2025-12-09T09:00
updated: 2025-12-09T09:00
title: "20251209"
type: daily-note
status: true
tags:
- daily
- journal
- 2025
- 2025-12
aliases:
- "2025-12-09"
date_formatted: 2025-12-09
topics:
- "[[daily]]"
- "[[journal]]"
related:
- "[[2025-12-08]]"
- "[[2025-12-10]]"
cssclasses:
- daily
---
# Daily Note - 2025-12-09
### Tasks
- [ ] Task 1
### Journal
...
### Navigation
<< [[2025-12-08]] | **Today** | [[2025-12-10]] >>
```
### Zettelkasten Note
Create in `04 - Permanent/`:
```yaml
---
created: {{date}}
type: zettelkasten
tags:
- permanent
- topic
---
# Note Title
## Main Insight
**Key Idea**: [Main point]
## Connections
- [[Related Note 1]]
- [[Related Note 2]]
## References
- Source citation
```
## Dataview Queries
For dataview query syntax, see [references/dataview.md](references/dataview.md).
**Quick examples:**
```dataview
LIST FROM "06 - Daily" WHERE file.cday = date(today) SORT file.ctime DESC
```
```dataview
TABLE status, tags FROM "01 - Projects" WHERE status != "completed"
```
## Templates
Templates location: `99 - Meta/00 - Templates/`
For Templater syntax, see [references/templater.md](references/templater.md).
**Common Templater variables:**
```markdown
<% tp.file.title %> # Current file name
<% tp.date.now("YYYY-MM-DD") %> # Current date
<% tp.file.cursor(1) %> # Cursor position
<% tp.system.prompt("Question") %> # User input prompt
```
## Installed Plugins
| Plugin | Purpose |
|--------|---------|
| **Dataview** | Query and display data from notes |
| **Templater** | Advanced templates with scripting |
| **Auto Note Mover** | Auto-organize notes by tags |
| **Periodic Notes** | Daily/weekly/monthly notes |
| **Kanban** | Kanban boards in markdown |
| **Tag Wrangler** | Bulk tag management |
| **Table Editor** | Markdown table editing |
| **Advanced URI** | Deep links to notes |
| **Local REST API** | External API access |
## File Operations
### Creating a Note
1. Determine appropriate folder based on note type
2. Add proper frontmatter
3. Use consistent naming conventions
4. Include relevant tags for auto-organization
### Best Practices
- Use descriptive filenames (avoid special characters except hyphens)
- Always include `created` and `updated` timestamps
- Tag notes for discoverability
- Link to related notes bidirectionally
- Use callouts for important information
- Include navigation links in daily notes
## Advanced Features
- **Dataview queries**: [references/dataview.md](references/dataview.md)
- **Templater scripting**: [references/templater.md](references/templater.md)
- **Canvas diagrams**: [references/canvas.md](references/canvas.md)
- **Plugin configurations**: [references/plugins.md](references/plugins.md)
---
## Gotchas
- **Bulk operations outside Obsidian don't trigger link-rebuilding** — external scripts must signal a `:Reindex` or wait for the next vault open.
- **Dataview cache is per-vault and per-session** — CLI script-based DQL queries may see stale state if Obsidian was last open with different filters.
- **Templater scripts via CLI run in a different context than the UI** — many `tp.system.*` functions return nil (no UI to prompt against).
- **PARA folder moves break tag-based queries** — if your queries hardcode folder paths, refactor them to use tags or properties before reorganizing.
- **Daily note rotation: changing the daily-note format mid-vault leaves old notes orphaned** — they don't auto-migrate to the new format; a rename pass is needed.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.