Agent skill · steipete
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.
What it needs
About 3k tokens when loaded.
What this skill does
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 knowledgeattach or knowledgerecall. 0. Save a discrete claim (decision, preference, commitment, fact, event or belief) with knowledgeremember 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 knowledgegrep; reserve knowledgelookup 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/knowledge-capture