home / skills / michaelvessia / nixos-config / obsidian-save

obsidian-save skill

safe

/modules/programs/claude-code/skills/obsidian-save

This skill helps you save current session insights to Obsidian by creating a structured note in your vault.

npx playbooks add skill michaelvessia/nixos-config --skill obsidian-save

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

3.2 KB

---
name: obsidian-save
description: |
  Save current session context to Obsidian vault. INVOKE THIS SKILL when user:
  - Says "save to obsidian", "note this to obsidian", "add to vault"
  - Wants to capture session insights to their notes
  - Says "save this session", "dump to obsidian"
  - Asks to "create a note from this conversation"
  - Mentions wanting to remember or archive the current discussion
  Trigger phrases: "save to obsidian", "note this", "add to vault", "save session", "dump to notes", "obsidian note"
allowed-tools: Bash, Write
---

# obsidian-save - Save Session to Obsidian

Capture current session context as a note in the Obsidian vault.

## When to Use

Use when user wants to save conversation insights, decisions, or context to their Obsidian knowledge base.

## Process

1. **Parse user prompt**: The text accompanying the skill invocation guides the note:
   - **Focus areas**: "just the debugging steps", "only architecture decisions"
   - **Exclusions**: "skip the failed attempts", "don't include the tangents"
   - **Structure**: "as a how-to guide", "as bullet points", "as a decision log"
   - **Title**: Extract explicit title if given, otherwise derive from topic

2. **Generate filename**: `YYYY-MM-DDTHH-MM-SS-<slug>.md`
   - Use provided title as slug, or derive from session topic
   - Slugify: lowercase, hyphens for spaces, no special chars

3. **Summarize session** based on user's direction:
   - Default (no direction): decisions, solutions, key insights, action items
   - With direction: prioritize what user asked for, shape content accordingly
   - Use concise bullet points unless user requests different structure

4. **Create note** at `~/obsidian/Notes/<filename>`:

```markdown
---
date: <ISO8601 timestamp>
daily: [[YYYY-MM-DD]]
tags:
  - claude-session
source: claude-code
---

# <Title>

## Summary

<Bulleted summary of session>

## Details

<Any additional context, code snippets, or specifics worth preserving>
```

5. **Confirm**: Echo the full path and brief summary of what was captured.

## Prompt Steering

The user's prompt is your primary guide. Examples:
- **Title**: "save to obsidian: webpack config fixes" → title is "webpack-config-fixes"
- **Focus**: "just the solution" → skip context, emphasize what worked
- **Format**: "as a checklist" → use `- [ ]` items instead of prose
- **Filter**: "only the API changes" → exclude unrelated discussion

When no direction given, default to a balanced summary of key outcomes.

## Examples

| User says | Action |
|-----------|--------|
| "save this to obsidian" | Summarize full session, auto-generated title |
| "note this discussion about auth" | Save with title "auth" as slug |
| "save to obsidian, focus on the fix we found" | Emphasize the solution, minimize context |
| "add to vault as a how-to guide for setting up the dev env" | Structure as step-by-step guide, not bullet summary |
| "dump to obsidian, just the architecture decisions we made" | Filter to only architectural choices |
| "save session, skip the debugging tangents" | Omit failed attempts, focus on outcomes |

## Notes

- Always include `daily: [[YYYY-MM-DD]]` for today's date to create backlink
- Keep summaries focused on actionable/memorable content
- Include code snippets only if they're the key takeaway

Overview

This skill saves the current conversation context as a well-structured note in your Obsidian vault. It extracts a title, produces a timestamped filename, summarizes key outcomes, and writes a Markdown note ready for your personal knowledge base. The skill confirms the saved path and a brief summary after creating the note.

How this skill works

When invoked, the skill parses the user's prompt for explicit instructions (title, focus, exclusions, and desired structure). It generates a slugified filename with an ISO timestamp and formats a Markdown note including frontmatter (date, daily backlink, tags, source). The content is summarized according to the user's direction—defaulting to decisions, solutions, key insights, and action items—and code snippets are included only when essential. Finally, it writes the file to the vault path and returns the file location with a short summary of what was captured.

When to use it

You want to archive the current discussion in Obsidian for later reference.
You need a concise record of decisions, action items, or solutions from a session.
You want to convert the conversation into a how-to, checklist, or decision log.
You asked to remember or persist important insights into your notes.
You want filtered output (e.g., only architecture decisions or only debugging steps).

Best practices

Give an explicit title when possible to produce a clean slug and predictable filename.
Specify the desired structure (bullets, checklist, how-to, decision log) to control formatting.
Request exclusions if you want to omit tangents or failed attempts.
Ask to include code snippets only if they are the key takeaway to keep notes focused.
Review the confirmation (path and summary) to verify the saved content and make edits in Obsidian if needed.

Example use cases

"Save to Obsidian: webpack config fixes" — saves focused troubleshooting steps and the final working config snippet.
"Add to vault as a how-to guide for setting up dev environment" — creates a step-by-step setup note with actionable steps.
"Dump to notes, just the architecture decisions" — stores only high-level tradeoffs and chosen patterns.
"Note this: meeting recap and action items" — captures decisions, owners, and next steps as a checklist.
"Save session, skip debugging tangents" — produces a concise summary of outcomes and remaining tasks.

FAQ

How is the filename generated?

A timestamped slug is created like YYYY-MM-DDTHH-MM-SS-<slug>.md using an explicit title or a derived topic, with lowercase hyphenated slugification.

Where is the note stored?

Notes are placed under ~/obsidian/Notes/ with frontmatter including date and daily backlink so Obsidian can link and index it.

Can I control what gets included?

Yes. Use short directives in your invoke phrase (e.g., "just the solution", "as a checklist", "skip failed attempts") and the skill will prioritize that guidance.