From skills
Files the current conversation answer as a permanent, self-contained Obsidian wiki page. Supports title inference, similarity search, and index updates.
How this skill is triggered — by the user, by Claude, or both
Slash command
/skills:save-note [title — omit to infer from context][title — omit to infer from context]The summary Claude sees in its skill listing — used to decide when to auto-load this skill
File this session's answer as a permanent wiki page in Obsidian. The note must be self-contained — a
File this session's answer as a permanent wiki page in Obsidian. The note must be self-contained — a reader with no context should be able to understand it.
If $ARGUMENTS provides a title, use it. Otherwise ask: "What should this note be titled, and which
folder?" using AskUserQuestion.
Default subfolders in 3 - Resources/:
| Subfolder | When to use |
|---|---|
Coding/ | Engineering patterns, technical decisions, API notes |
Reflections/ | Personal insights, mental models, lessons learned |
Concepts/ | General concepts, frameworks, ideas |
Communication/ | Leadership, writing, comms patterns |
qmd query "<topic>" --json -n 8 2>/dev/null
New page:
obsidian create path="3 - Resources/<subfolder>/<title>.md" content="<note>"
Append to existing:
obsidian append path="3 - Resources/<subfolder>/<existing>.md" \
content="\n## Update — $(date +%Y-%m-%d)\n\n<content>"
Frontmatter for new pages:
---
source: claude-memory
created: YYYY-MM-DD
aliases: [<acronyms, alternate names, spelling/casing variants>]
tags: [claude-memory, <topic-tags>]
---
Generate 2–6 aliases: off-title terms someone would search to find this page (acronyms, alternate
names, "X vs Y" framings). This is what makes the page recall-able from queries that don't match the
title. Skip only when the title is the sole term anyone would use.
Body: the synthesized answer from this session. Neutral, reference-focused voice — no "I learned that..." framing. Should make sense to a reader with no context.
Add to index.md under the ## Concept notes (claude-memory) heading. The CLI has no patch, so
this section-targeted insert means either the MCP obsidian_patch_content tool (target the heading,
operation: append) or read + create ... overwrite. Ask the user which. Entry format:
- **<Title>** ($(date +%Y-%m-%d)) — [[<stem>]] (<path>). _<one-line summary>_
Append to log.md (chronological — append is fine):
obsidian append path="3 - Resources/log.md" content="\n## $(date +%Y-%m-%d)\nsave-note | <title>"
npx claudepluginhub kriscard/skillsFiles conversation insights into an Obsidian wiki vault as structured notes. Detects note type, generates frontmatter, and updates index/log/hot cache.
Processes Obsidian Inbox items into a knowledge base: reads source, discusses key ideas, then files synthesized notes. Also saves conversation answers as permanent wiki pages.
Creates dated Markdown notes with YAML frontmatter, tags, summaries, and references in .claude/data/notes/ for secondbrain. Activates on 'create note', 'capture thought', 'save this', etc.