3ad61b984d
Skills (new): - skills/obsidian-markdown/ — full Obsidian Flavored Markdown syntax reference (wikilinks, embeds, callouts, properties, math, Mermaid) - skills/obsidian-bases/ — Obsidian Bases (.base files) with correct filters/views/ formulas syntax (sourced from kepano/obsidian-skills authoritative spec) - skills/defuddle/ — web page cleaner; strips ads/nav before URL ingestion, saves 40-60% tokens on web articles wiki-ingest upgrades: - URL ingestion: pass https:// directly, auto-fetches + runs defuddle if available - Image/vision ingestion: .png/.jpg/.gif etc → Claude reads → description saved to .raw/ → standard ingest pipeline - Delta tracking: .raw/.manifest.json tracks hash per source, skips unchanged files wiki-query upgrades: - Quick mode (query quick:) — hot.md + index only, ~1500 tokens - Standard mode — existing behaviour, 3-5 pages - Deep mode (query deep:) — full wiki + optional web search supplement hooks: - PostToolUse auto-commit: every Write/Edit to wiki/ or .raw/ triggers git add + commit automatically, vault always versioned fixes: - Removed invalid allowed-tools field from all 10 SKILL.md files (not a valid skill frontmatter attribute per spec; was silently ignored) - Canvas SKILL.md now references json-canvas open standard and kepano/obsidian-skills wiki research: - Ecosystem research: 16+ Claude+Obsidian projects mapped and filed - New pages: comparisons/claude-obsidian-ecosystem, concepts/cherry-picks, entities/ (6 new), sources/claude-obsidian-ecosystem-research - Cherry-picks roadmap filed at wiki/concepts/cherry-picks.md Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
116 lines
3.7 KiB
Markdown
116 lines
3.7 KiB
Markdown
---
|
|
name: save
|
|
description: >
|
|
Save the current conversation, answer, or insight into the Obsidian wiki vault as a
|
|
structured note. Analyzes the chat, determines the right note type, creates frontmatter,
|
|
files it in the correct wiki folder, and updates index, log, and hot cache.
|
|
Triggers on: "save this", "save that answer", "/save", "file this",
|
|
"save to wiki", "save this session", "file this conversation", "keep this",
|
|
"save this analysis", "add this to the wiki".
|
|
---
|
|
|
|
# save — File Conversations Into the Wiki
|
|
|
|
Good answers and insights shouldn't disappear into chat history. This skill takes what was just discussed and files it as a permanent wiki page.
|
|
|
|
The wiki compounds. Save often.
|
|
|
|
---
|
|
|
|
## Note Type Decision
|
|
|
|
Determine the best type from the conversation content:
|
|
|
|
| Type | Folder | Use when |
|
|
|------|--------|---------|
|
|
| synthesis | wiki/questions/ | Multi-step analysis, comparison, or answer to a specific question |
|
|
| concept | wiki/concepts/ | Explaining or defining an idea, pattern, or framework |
|
|
| source | wiki/sources/ | Summary of external material discussed in the session |
|
|
| decision | wiki/meta/ | Architectural, project, or strategic decision that was made |
|
|
| session | wiki/meta/ | Full session summary — captures everything discussed |
|
|
|
|
If the user specifies a type, use that. If not, pick the best fit based on the content. When in doubt, use `synthesis`.
|
|
|
|
---
|
|
|
|
## Save Workflow
|
|
|
|
1. **Scan** the current conversation. Identify the most valuable content to preserve.
|
|
2. **Ask** (if not already named): "What should I call this note?" Keep the name short and descriptive.
|
|
3. **Determine** note type using the table above.
|
|
4. **Extract** all relevant content from the conversation. Rewrite it in declarative present tense (not "the user asked" but the actual content itself).
|
|
5. **Create** the note in the correct folder with full frontmatter.
|
|
6. **Collect links**: identify any wiki pages mentioned in the conversation. Add them to `related` in frontmatter.
|
|
7. **Update** `wiki/index.md` — add the new entry at the top of the relevant section.
|
|
8. **Append** to `wiki/log.md` — new entry at the TOP:
|
|
```
|
|
## [YYYY-MM-DD] save | Note Title
|
|
- Type: [note type]
|
|
- Location: wiki/[folder]/Note Title.md
|
|
- From: conversation on [brief topic description]
|
|
```
|
|
9. **Update** `wiki/hot.md` to reflect the new addition.
|
|
10. **Confirm**: "Saved as [[Note Title]] in wiki/[folder]/."
|
|
|
|
---
|
|
|
|
## Frontmatter Template
|
|
|
|
```yaml
|
|
---
|
|
type: <synthesis|concept|source|decision|session>
|
|
title: "Note Title"
|
|
created: YYYY-MM-DD
|
|
updated: YYYY-MM-DD
|
|
tags:
|
|
- <relevant-tag>
|
|
status: developing
|
|
related:
|
|
- "[[Any Wiki Page Mentioned]]"
|
|
sources:
|
|
- "[[.raw/source-if-applicable.md]]"
|
|
---
|
|
```
|
|
|
|
For `question` type, add:
|
|
```yaml
|
|
question: "The original query as asked."
|
|
answer_quality: solid
|
|
```
|
|
|
|
For `decision` type, add:
|
|
```yaml
|
|
decision_date: YYYY-MM-DD
|
|
status: active
|
|
```
|
|
|
|
---
|
|
|
|
## Writing Style
|
|
|
|
- Declarative, present tense. Write the knowledge, not the conversation.
|
|
- Not: "The user asked about X and Claude explained..."
|
|
- Yes: "X works by doing Y. The key insight is Z."
|
|
- Include all relevant context. Future sessions should be able to read this page cold.
|
|
- Link every mentioned concept, entity, or wiki page with wikilinks.
|
|
- Cite sources where applicable: `(Source: [[Page]])`.
|
|
|
|
---
|
|
|
|
## What to Save vs. Skip
|
|
|
|
Save:
|
|
- Non-obvious insights or synthesis
|
|
- Decisions with rationale
|
|
- Analyses that took significant effort
|
|
- Comparisons that are likely to be referenced again
|
|
- Research findings
|
|
|
|
Skip:
|
|
- Mechanical Q&A (lookup questions with obvious answers)
|
|
- Setup steps already documented elsewhere
|
|
- Temporary debugging sessions with no lasting insight
|
|
- Anything already in the wiki
|
|
|
|
If it's already in the wiki, update the existing page instead of creating a duplicate.
|