Skip to content
cccskills
Official · OpenClawFreePublished on GitHubEnglish overview

knowledge-capture

Capture durable preferences, decisions, facts, commitments, and lessons in Knowledge with attribution and supporting evidence. Save a single claim quickly or update a relevant page, then read back the result to verify the intended information and subject link.

OriginalShow the original 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.

openclaw/openclaw393,141 stars(GitHub 393,141 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Saving a decision or preference with its context
  • Adding a supported fact to an existing Knowledge page
  • Recording a short thought with attribution
  • Checking that a saved note and its evidence are retrievable

Overview

What it does

When Knowledge is the selected memory provider, this skill records preferences, decisions, facts, commitments, and lessons that may be useful later. It can save one concise claim with knowledge_remember, including attribution, supporting conversation text, and an exact subject page title or alias when known. For longer notes or page updates, it searches for existing records and relevant pages, preserves the source and any uncertainty, and updates the appropriate section. After publishing, it reads back the text and evidence and checks that the subject link resolves.

When it helps

Use it to preserve a decision made in conversation, a preference that may come up again, or an important project fact or lesson. It can add useful information to an existing page while avoiding duplicate records. Temporary task status and unsupported guesses are not saved. A saved preference remains contextual information; it does not change assistant settings or guarantee that it will be loaded in a future conversation.

Example requests

  • “Record this decision with the supporting statement and project page.”
  • “Save this preference in Knowledge and check that it can be found later.”
  • “Add this short note to the existing page and keep the speaker attribution.”

Notes

Knowledge must be the selected memory provider. Saving a commitment does not carry it out, and this skill does not schedule reminders. Longer notes and page edits require checking existing records, sources, and relevant pages before writing.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt excludes secrets, transient status, and guesses, and does not execute commitments or set reminders.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodThe only stated prerequisite is that Knowledge is the selected memory provider.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 26, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

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

Files included (13)

  • SKILL.md4.6 KB
  • references/assertions.md4.6 KB
  • references/conventions.md14.3 KB
  • references/identity.md4.8 KB
  • references/meeting-entity-example.md6.8 KB
  • references/profiles.md2.8 KB
  • references/publication.md22.1 KB
  • references/publish.md3.0 KB
  • references/recovery.md2.0 KB
  • references/setup.md1.7 KB
  • references/sources.md3.0 KB
  • references/verify.md2.7 KB
  • references/writing.md1.9 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

1password

Official · OpenClawFreeSummary

Set up and authenticate the 1Password CLI, then supply stored passwords and API keys to commands or configuration. The skill covers desktop integration, service accounts, and interactive sign-in while keeping secrets out of chat and logs.

  • Setting up the 1Password CLI
  • Supplying API keys to commands
  • Using service account authentication in CI
openclaw/openclaw393.1KUpdated Oct 26, 2026

acp-router

Official · OpenClawFreeSummary

Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.

  • Starting a Claude Code session in a thread
  • Continuing work with an external coding agent
  • Relaying prompts directly through acpx
openclaw/openclaw393.1KUpdated Oct 26, 2026

add-model-provider

Official · OpenClawFreeSummary

Add a model provider to OpenClaw and verify it with a real response. The skill validates configuration, keeps credentials in environment or file references, and reports test results and any default model changes.

  • Adding a model provider to OpenClaw
  • Configuring credentials through environment or file references
  • Checking whether a model returns a real response
openclaw/openclaw393.1KUpdated Oct 26, 2026

agent-transcript

Official · OpenClawFreeSummary

Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.

  • Preparing an agent activity record for a pull request
  • Extracting task-relevant prompts and results from local logs
  • Previewing a transcript with sensitive information removed
openclaw/openclaw393.1KUpdated Oct 26, 2026

apple-notes

Official · OpenClawFreeSummary

Manage Apple Notes on macOS through memo, a command-line tool. Create, browse, search, edit, delete, and move notes between folders, or export selected notes to HTML or Markdown for use outside the app.

  • Creating notes with titles
  • Finding notes by folder or approximate search
  • Editing notes and organizing them into folders
openclaw/openclaw393.1KUpdated Oct 26, 2026

apple-reminders

Official · OpenClawFreeSummary

Manage Apple Reminders from your Mac with remindctl, a terminal tool. View tasks by date, add or edit reminders, organize lists, and mark tasks complete or delete them, including personal to-dos that sync to iOS.

  • Review today’s tasks and overdue reminders
  • Add personal to-dos with due dates
  • Organize tasks visible on an iPhone or iPad
openclaw/openclaw393.1KUpdated Oct 26, 2026

See all skills by openclaw

Report a problem with this skill