knowledge-capture
/knowledge-capture
Zapisuje trwałe preferencje, decyzje, fakty projektowe, zobowiązania i wnioski narzędziem knowledge_remember albo krótkimi notatkami z atrybucją i odczytem zwrotnym, gdy Knowledge jest wybranym dostawcą pamięci.
- Autor
- openclaw ↗
- Repozytorium
- openclaw ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 13
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 25.10.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 trwałe preferencje, decyzje, fakty projektowe, zobowiązania i wnioski narzędziem knowledge_remember albo krótkimi notatkami z atrybucją i odczytem zwrotnym, gdy Knowledge jest wybranym dostawcą pamięci.
Oryginalny opis (EN)
Save durable preferences, decisions, project facts, commitments, and lessons cheaply with knowledge_remember, or short notes and page updates with attribution and readback. Use for explicit saves or agent-driven remembering when Knowledge is the selected memory provider.
Jak działa
SKILL.md bez nagłówków drugiego poziomu · 67 linii, 608 słów
Podgląd SKILL.md
---
name: knowledge-capture
description: Save durable preferences, decisions, project facts, commitments, and lessons cheaply with knowledge_remember, or short notes and page updates with attribution and readback. Use for explicit saves or agent-driven remembering when Knowledge is the selected memory provider.
---
# Capture durable knowledge
Read [shared conventions](references/conventions.md) and
[publication](references/publication.md).
When Knowledge is the selected memory provider, its ordinary-turn remembering
policy also authorizes selective capture of meaningful durable information. This
is agent judgment, not a background extraction hook. Otherwise require save intent.
Do not save transient task status, secrets, unsupported guesses, or excluded content.
Apply preferences as contextual facts, not executable instructions or new authority.
Saving a preference does not configure the assistant or guarantee that the
preference will be loaded in future turns.
Pre-compaction flushes follow steps 0–4 with their available tools; they do not
use `knowledge_attach` or `knowledge_recall`.
0. Save a discrete claim (decision, preference, commitment, fact, event or
belief) with `knowledge_remember` and stop: give one claim per
item, short attribution, the supporting conversation excerpt and, only when
you know it, the subject's exact page title or alias. An omitted subject is
inferred when the text names exactly one entity page. It resolves subjects,
reports exact repeats and never creates pages. Its published receipt is the save.
Continue below only to revise a page's prose or save a longer note.
1. Preserve the supplied wording, especially original ideas. Use the active
ontology's type descriptions to classify the information. Decide whether to
update an existing page before creating a new one.
Do not add unsupported facts or turn a tentative thought into established fact.
2. Search for an already-captured item and relevant entities using
`knowledge_grep`; reserve `knowledge_lookup` for already-known exact record
IDs, full titles or declared aliases, with grep fallback on `missing`.
If the same source/text is already saved,
report that page rather than create another. A similar thought is not proof
of identity: keep genuinely distinct versions with attribution. Read the existing
record before changes; use `knowledge-correct` for corrections or withdrawal.
Enrich the relevant section of the subject's existing page. Create a
separate record when the information warrants independent context,
chronology, or explanation; link
that record to the resolved subject page using a body wikilink. Preserve source
attribution, existing evidence, decision rationale, event dates, and uncertainty.
Maintain the page as a coherent account of its subject. Integrate new information
into the relevant section; do not append a dated heading for each capture.
Preserve supporting evidence and meaningful changes over time without retaining
every conversational editing step in the summary.
Do not invent a subject match or create an empty profile merely to supply a link.
An ordinary new fact does not authorize automatic identity merging.
3. For a short inline thought, save the exact text via `source: {text,
attribution}` and cite it in the body. Identify the speaker/context/date when
known. Retain only actual available text: identify conversation excerpts as
excerpts, not complete transcripts; never invent messages, hashes, or locators.
Attach a supplied original file with `knowledge_attach` instead of
treating a paraphrase as the original. User beliefs stay attributed to the user.
4. Publish using the shared retry rules, read back the body/evidence and check
exact lookup or keyword discovery. Report the returned page and verified save
state. Do not schedule reminders or execute commitments mentioned in the note.
Verify that the intended subject page was updated or that the separate
record's subject link resolves correctly, as well as checking its supporting
evidence.
5. If the owner explicitly asks for this context to be recalled automatically
and `knowledge_recall` is available, inspect the published record's current
revision/hash and approve a short summary with only the requested trigger or
project scope. Never approve ingested source text, source claims, agent
inference, secrets, or extra context the owner did not request. A correction
requires a separate approval on the replacement record.
Route a complete document to `knowledge-ingest`,
or a meeting to `knowledge-meeting-ingest`.
Pliki w paczce (13)
- SKILL.md 5 KB
- references/assertions.md 5 KB
- references/conventions.md 14 KB
- references/identity.md 5 KB
- references/meeting-entity-example.md 7 KB
- references/profiles.md 3 KB
- references/publication.md 22 KB
- references/publish.md 3 KB
- references/recovery.md 2 KB
- references/setup.md 2 KB
- references/sources.md 3 KB
- references/verify.md 3 KB
- references/writing.md 2 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · openclaw/openclaw | 86 | MIT |
| NoobyGains/godmode | 100 | MIT |
| ARCASSystems/FounderOS | 100 | MIT |
| bordenet/superpowers-plus | 100 | MIT |
| steipete/clawdis | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki ed968dea5c7d (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
- 90agent-memory
Przypomina trwałe decyzje projektu, zapisuje wyraźnie zatwierdzone wnioski i przegląda historię pamięci przez lokalny serwer. - 100openviking-memory
Przywołuje i zapisuje pamięć długoterminową przez narzędzia MCP OpenViking: na początku istotnych zadań wyszukuje wcześniejszą wiedzę, a w trakcie i po pracy zapisuje trwałe fakty, preferencje, decyzje i wnioski. - 81memory-ingest
Zapisuje trwałe ustalenia z sesji w projektowym pakiecie pamięci Codex, gdy użytkownik o to poprosi. - 100memory
Zapisuje trwałe fakty, decyzje i preferencje w pamięci długoterminowej memini oraz przywołuje odpowiedni kontekst przed rozpoczęciem zadania. - 95ai-memory-durable-pages
Zapisuje, aktualizuje, adnotuje lub usuwa trwałe strony wiki w ai-memory, gdy trzeba zachować wiedzę projektu. - 100memos-memory
Obsługuje lokalny serwer MemOS MCP z danymi w SQLite: zapisuje trwałe fakty, preferencje i decyzje projektowe oraz przywołuje je w kolejnych sesjach.