Skip to content
cccskills
FreePublished on GitHub

knowledge-capture

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (3)

  • SKILL.md4.6 KB
  • references/conventions.md14.3 KB
  • references/publication.md20.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Capture durable knowledge

Read shared conventions and publication.

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Create scheduled Knowledge ingestion automations with a verified worker, private-vault authority, and an end-to-end scheduled run. Use when asked to schedule or repair recurring ingestion from any source.

The English summary is being prepared. Showing the original description.

openclaw/knowledge2Updated Oct 21, 2026

Correct or withdraw specific saved Knowledge claims, explicit relationships, or pages at the user's request, preserving provenance and inspecting affected knowledge. Use for “that's wrong”, “retract that”, or a Knowledge chat reference; not automatic contradiction resolution or physical erasure.

The English summary is being prepared. Showing the original description.

openclaw/knowledge2Updated Oct 21, 2026

Resolve and enrich Knowledge people, companies, projects, and concepts during an authorized ingestion or entity update, with sourced State, timelines, and back-links. Read-only identity questions do not authorize writes.

The English summary is being prepared. Showing the original description.

openclaw/knowledge2Updated Oct 21, 2026

Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links. Routes meetings to knowledge-meeting-ingest and short thoughts to knowledge-capture.

The English summary is being prepared. Showing the original description.

openclaw/knowledge2Updated Oct 21, 2026

Ingest meeting transcripts from any recorder into Knowledge with attendee enrichment, timeline merge, supported decisions and commitments, and verification of substance and sequence. Summary-only input is not a verified meeting ingestion.

The English summary is being prepared. Showing the original description.

openclaw/knowledge2Updated Oct 21, 2026

Find and answer from saved Knowledge vault pages with source citations. Use for questions about stored documents, meetings, people, or projects; not for recalling conversation history or searching the web.

The English summary is being prepared. Showing the original description.

openclaw/knowledge2Updated Oct 21, 2026

See all skills by openclaw

Report a problem with this skill