Correct or withdraw a specific Knowledge claim, relationship, or page when asked. Preserve evidence and history, inspect affected records, and report what was repaired or remains unresolved; this does not erase originals or automatically resolve conflicts.
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.
Run score Not tested
See how to installWhen asked, this skill corrects or withdraws specific claims and explicit relationships stored in Knowledge. It can also revise page text or merge duplicate pages that represent the same person or entity. It preserves the original sources and change history, checks records affected by the change, and reads the result back to confirm that the replacement or withdrawal took effect. If the user's explanation is retained as evidence, it is kept distinct from facts verified by independent sources.
Use it when you find an error in saved content, want to withdraw a claim or relationship, or discover duplicate pages for the same subject. If you can identify the relevant Knowledge record, the skill can inspect and update it.
Changes are made in response to an explicit user request. Conflicting information alone does not trigger an automatic correction. The skill does not physically erase originals or backups.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
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).
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.
Review the instructions the agent will receive before you install.
Read shared conventions and publication before writes.
Use a supplied structured record/claim ID and revision as the primary target,
not just its display label. Read knowledge_record with metadata and evidence;
confirm its current revision/hash. A referenced revision that changed requires
rereading and reconciling the request, not silently acting on a new assertion.
Without an exact reference, use lookup/search, inspect candidates, and ask only
when the requested target or correction remains materially ambiguous.
Distinguish an erroneous saved assertion from an unsupported answer, conflicting source statements, and a fact that changed over time. Contradiction alone does not authorize supersession; the one non-user case is a standing statement its own holder explicitly replaced, per publication. Do not manufacture a stored “guard fact” when no record exists or treat a retraction as evidence for its opposite.
knowledge_correct with
the exact ID, observed expectedRevision and expectedHash, reason, observed
vault UUID and ontology fingerprint, and a complete replacement of the same
kind. Replacement fields use the create-claim/create-relationship contract;
there is one outer request ID, not a second replacement request. Preserve
supported context, attribution, precise dates and evidence; remove or revise
what the correction actually changes. The operation publishes the replacement
and supersedes the old assertion together, with links in both directions.knowledge_withdraw with the
exact ID, revision/hash, reason and vault UUID. It accepts pages, claims and
explicit relationships. An edge is identified by its own ID, not its endpoint
pair. It preserves original evidence/history and is not file deletion.knowledge_save_page,
preserving unrelated authored material and sources. Page corrections are
revisions, not replacement entity identities.knowledge_merge with the surviving page,
the duplicate, both pages' current revision/hash and a reason. Keep the page
with the fuller identity (real name, more connections) as the survivor; pass
title to rename it and body when the combined page should say more than
the survivor's current prose. The duplicate's ID, title, aliases, claims,
relationships and links then resolve to the survivor; nothing is corrected one
by one. Undo a mistaken merge with knowledge_unmerge.An explicit user correction can supply evidence: retain their exact statement
with knowledge_attach, attribute it to the user, and reference its verified
locator. Use assertion_origin: user_belief to distinguish a user assertion from
an independently sourced statement; do not claim documentary verification.
Agent inference still needs retained premise evidence, not an invented quote.
Use knowledge-entities to find and read the handle profile, the established
person and their connected records. Retain the user's exact identification as
evidence. Update supported aliases and identity context on the existing pages;
preserve unrelated content and describe the connection to the established person.
Use that person's existing ID for future enrichment. When the handle already has
its own page, merge it into the established person's page with knowledge_merge
instead of writing a pointer page, withdrawing it, or correcting its claims one by
one. Merge only on identity evidence (the user's statement, a self-introduction, a
shared stable account ID), never on name similarity; knowledge_diagnostics
mergeCandidates lists pages to check, not pages to merge. Retain the identity
evidence with knowledge_attach and pass it as evidence.
Inspect affected prose, claims, timelines and relationships within the correction scope. Correct mistaken attribution and unresolved identity where the new evidence supports it, using the page/assertion operations above; preserve source labels, verbatim quotes, event dates and correction provenance. A confirmed author identity does not independently verify that author's factual claims.
Changes go through these tools, not manual Markdown edits, browser forms, SQL, or separate “create then withdraw” calls. No additional approval ritual applies to an unambiguous user-authorized correction. Follow publication retry/conflict handling; a receipt in accepted/conflict state is not a completed repair.
The receipt's impact.items identifies known scoped direct/transitive dependents
at acceptance. It does not update them. Read affected records by exact ID and
inspect their evidence. Repair only supported changes within the request's scope;
do not blindly replace dependency IDs or source quotes with the new claim.
Records depending on an inactive assertion are withheld from current discovery
until repaired; exact record/history inspection remains available.
Search for plausible prose copies as a supplementary check. Search misses, unlinked prose, hidden scopes and incomplete indexes prevent a universal “all copies fixed” promise. Do not alter unrelated memory or identity systems as an automatic consequence of a Knowledge correction.
Read back the original and replacement (or withdrawn target), verify lifecycle and evidence, and verify current lookup excludes the old assertion. Reply with the receipt/request ID, affected record IDs, the correction/retraction reason, and repaired versus unresolved dependencies. Mention retained history only when relevant; never promise erasure from originals, exports or backups.
No reviews yet. Tell others what you thought.
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.
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.
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.
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.
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.
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.
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.