save
/save
Zapisuje dobrą odpowiedź lub dyskusję z sesji jako stronę syntezy w wiki w vaultcie, z cytowaniami i linkami. Przydaje się, gdy wynik warto zachować w bazie wiedzy.
- Autor
- erayozenn ↗
- Repozytorium
- BigHead-2ndBrain ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zapisuje dobrą odpowiedź lub dyskusję z sesji jako stronę syntezy w wiki w vaultcie, z cytowaniami i linkami. Przydaje się, gdy wynik warto zachować w bazie wiedzy.
Wyzwalacze z opisu
Argumenty
/save [title or what to save]
Oryginalny opis (EN)
Save a good answer, comparison or discussion from this session into the vault's wiki as a synthesis page (or extend an existing one) — with citations and uncertainty markers kept, sources collected, links from related pages, and index, log and hot cache updated. Use when the user asks to save, keep, file or "wiki" an answer, or accepts a save offer from the query skill.
Jak działa
- 1. Pick the content
- 2. New page, extension, or nothing
- 3. Plan, then write or wait
- 4. Write the page
- 5. Link it
- 6. System files
- 7. Verify and report
Podgląd SKILL.md
---
name: save
description: Save a good answer, comparison or discussion from this session into the vault's wiki as a synthesis page (or extend an existing one) — with citations and uncertainty markers kept, sources collected, links from related pages, and index, log and hot cache updated. Use when the user asks to save, keep, file or "wiki" an answer, or accepts a save offer from the query skill.
argument-hint: "[title or what to save]"
---
# Save an answer as a synthesis
Arguments: `$ARGUMENTS` — optional title, or a pointer to what to save ("the RAG comparison").
Default: the last answer in this session that came from the vault (usually a query answer).
The vault's `CLAUDE.md` is the authority for rules (frontmatter, summary callout, freshness,
citation, markers, autonomy). This skill is the procedure; where they differ, the vault's
CLAUDE.md wins. Talk to the user in the vault's chat language; write the page in the wiki
language.
**Preconditions.** Use the vault that encloses the current directory: a folder whose `CLAUDE.md`
starts with `# Vault Schema & Rules` and that holds `index.md`. If there is none, use the
configured vault folder `${user_config.vault_path}`; if that is empty, an unreplaced placeholder or
not such a folder, stop and say so (the user can set it in `/config`, under this plugin's options).
One synthesis per run.
**Outside the vault** (the current directory is not inside it): every vault path below, such as
`wiki/syntheses/` or `log.md`, means that path under the vault folder, written as an absolute path
with forward slashes. `hot.md` is not loaded there; read it when a step uses it. Read the vault's
`CLAUDE.md` before the first write and follow it. Pass the vault folder wherever a command says
`--vault .`. Run vault git commands as `git -C "<vault>" …`, never in the current repo, and push the
vault only when the user asks. Never copy vault content into the current repo, its commits, PRs or
issues unless the user asks.
## 1. Pick the content
- No argument: the last vault-based answer in this session. If the session has several
candidates, or the last answer is not vault-based, list them in one line each and ask.
- Content can be a query answer, a comparison, or a discussion worth keeping (e.g. a design
argument). Not: raw source summaries (that is ingest), the user's own notes (author: me),
or chat that has no claims.
## 2. New page, extension, or nothing
Read `index.md` (Syntheses section and related concepts). First sort the answer's claims by
support: cited wiki pages, cited raw files, (unsupported) / "(not in the vault)".
- **Core is unsupported** (the main answer is general knowledge, the vault only has passing
mentions) → no synthesis: it would put an unsourced core into the wiki and be rewritten once
a real source is ingested. Instead add the vault-backed parts that carry lasting value to the
related concept page(s), cited, and propose ingesting a source for the core.
- **Restates an existing synthesis** → say so, do not save a new page. If there is a small new
detail, add just that to the existing page (step 3 decides whether to ask first); if nothing is
new, say so and stop.
- **Overlaps an existing synthesis but adds something** (new axis, new evidence, an answered open
question) → extend that page.
- **New question** → new page `wiki/syntheses/<slug>.md`. Slug: English, ASCII, lowercase
kebab-case, named after the question (e.g. `metric-choice-by-error-cost`). Check that the
basename is unique vault-wide (Glob `**/<slug>.md`).
## 3. Plan, then write or wait
State in a few lines: new page or which page is extended, title, the 1–3 related pages that will
get a link, and the system files (index, log, hot). Then:
- **Write now** when the user's own message asked to save ("save it", "keep this", "kaydet",
"sakla") and every file in the plan is one the vault's CLAUDE.md lets Claude write freely
(wiki pages, index, log, hot). Take your recommended option, write it, and in the report say
which option you took, the alternative, and that the change is uncommitted, so `git diff`
shows it and `git checkout -- <file>` undoes it.
- **Wait for approval** otherwise: the save was only your own offer, the plan touches a path the
vault's CLAUDE.md marks ask-first, or the user's message is unclear about saving.
## 4. Write the page
Frontmatter per CLAUDE.md with `type: synthesis`, `status: draft`, `author: claude`; then the
"For future agent" summary callout. Body:
- **Question.** One sentence, as the user meant it.
- **Short answer.** 2–4 sentences, markers included.
- **Body.** The answer's support, reorganised for reading later (sections, a table for
comparisons). Not a transcript of the chat.
- **Open questions.** Gaps the answer exposed.
Rules while converting chat into a page:
- **Citations:** keep every `[[link]]`. Cite the wiki pages the answer used; raw files as
`[[raw/<full path>]]` with page numbers where the answer had them.
- **`sources:` frontmatter:** the union of the `sources:` of every cited wiki page, plus raw files
cited directly. Read only the frontmatter heads of those pages for this.
- **Markers:** carry (provisional), (disputed), (unsupported) over unchanged; never upgrade one.
- **General knowledge** that the answer labelled "(not in the vault)" stays, marked
**(unsupported)**, and goes into "Open questions" as something a source should confirm.
- **Freshness:** every changing fact dated ("as of YYYY-MM", or the date of the cited source).
- **Interpretation** (your own reasoning in the answer) is labelled "(interpretation)".
- **Quotes:** only text copied from a source read in this session; otherwise paraphrase
without quote marks.
- Chat-language search terms go into `aliases`.
Extending an existing synthesis — or, for small additions, a concept page (one bullet or
sentence where the topic is discussed, cited): add a section or rows, update `updated:`, keep its structure,
do not rewrite parts that did not change. If the new content contradicts it, keep both sides,
cite both, mark (disputed).
## 5. Link it
Add a link to the synthesis from the 1–3 most related concept pages (their "Related" section,
or one sentence where the topic is discussed). Read budget: at most 5 existing pages in total,
including any page being extended.
## 6. System files
- `index.md`: one line under Syntheses — `- [[slug]] — <summary from the callout>`; for an
extension, update that line if its summary changed.
- `log.md`: `## [YYYY-MM-DD] save | <title> → [[slug]] (new | extended)`; when no synthesis was
written, say why and which page got the addition.
- `hot.md`: "Recent changes" (keep ~5); "Key facts" only if the synthesis settles something
lasting. Keep hot.md ≤ 500 words.
## 7. Verify and report
Run the ingest skill's verifier (`../ingest/scripts/` next to this skill's directory):
```
python <ingest scripts>/verify_ingest.py --vault . --pages <synthesis> <every page you changed>
```
Fix every ERROR; check each quote WARN (paraphrase in quote marks → remove the marks). Report:
created/changed files, verification result, open questions. Propose a commit in the vault repo
(`save: <title> → <slug>`); do not commit without approval.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · erayozenn/BigHead-2ndBrain | 100 | MIT |
| nigelng/nng-kit | 100 | MIT |
| agricidaniel/claude-obsidian | 100 | MIT |
| NourEldinShobier/handoff | 100 | MIT |
| arcfjmt/handoff | 100 | MIT |
| ryanonline1234/smart-compact | 100 | MIT |
| xtsoftwarelabs/neatcontext-plugins | 100 | MIT |
| ARCASSystems/FounderOS | 90 | MIT |
| adb-software-solutions/contextbrain-plugins | 82 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 5c5c1f1ce1a0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100query
Odpowiada na pytania na podstawie wiki w vaultcie, z cytatami, znacznikami niepewności i informacją, gdy wiki nie wystarcza. - 90wiki-query
Odpowiada na pytania na podstawie wiki w Obsidianie, podaje cytowania i może zapisać syntezę jako nową stronę. - 100wiki-query
Przeszukuje wiki Obsidian etapami: od pliku hot, przez podsumowania, do pełnej strony, by oszczędzić kontekst. - 90query-wiki
Odpowiada na pytanie na podstawie wiki OKF, syntetyzując koncepcje z cytatami, i może zapisać odpowiedź jako wielokrotnie użyteczną stronę. - 90wiki-query
Odpowiada na pytania z operacji LLM Wiki na podstawie stron wiki i surowych źródeł, z cytowaniami, jawnie wskazuje luki i proponuje zapis trwałej syntezy. - 100wiki-query
Odpowiada na pytania na podstawie wiki: przeszukuje strony, syntetyzuje odpowiedź z cytatami i opcjonalnie zapisuje wartościowe odpowiedzi jako nowe strony.