Skip to content
Skills Library
Documents & office · Review & audit

knowledge-correct

/knowledge-correct

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.

Repository
clawdis ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
19
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Triggers from the description

thatretract that
Original author description

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.

How it works

  1. Identify the owning record
  2. Apply the right operation
  3. Resolve a handle or mistaken identity
  4. Inspect propagation and report honestly
Original SKILL.md headings · 111 lines, 949 words
SKILL.md preview
---
name: knowledge-correct
description: 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.
---

# Correct saved knowledge through agent tools

Read [setup](references/setup.md) first. Read the rest only when a step needs
it, and don't reread one after compaction unless you are about to use it:
[assertions](references/assertions.md) for claim and relationship fields,
[publish](references/publish.md) and [subject pages](references/profiles.md) for
page prose, [sources](references/sources.md) for retaining a user's statement,
[recovery](references/recovery.md) for any uncertain, rejected or conflicting
write, and [verify](references/verify.md) for readback.

## Identify the owning record

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
([assertions](references/assertions.md#before-creating-reuse-or-reconcile)). Do not manufacture a stored “guard fact” when no
record exists or treat a retraction as evidence for its opposite.

## Apply the right operation

- **Claim or explicit relationship correction:** call `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.
- **Replaced by a claim that already exists:** call `knowledge_supersede` with
  the existing claim as `by` and the earlier claims' fences in `superseded`
  instead of correcting, which would write a duplicate of the replacement. The
  claims must share a linked page. Undo a mistaken supersession with the same
  call and `undo: true`.
- **Withdrawal without a replacement:** call `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.
- **Page prose correction:** use ordinary revision-fenced `knowledge_save_page`
  or `knowledge_edit_body`, changing only the text the correction affects and
  preserving unrelated authored material, sources and every other citation.
  Rewrite the affected State topic so it reads as current; don't append a
  dated correction section to an entity page. Page corrections are
  revisions, not replacement entity identities.
- **Two pages for one entity:** call `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.

## Resolve a handle or mistaken identity

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 and relationships, including source notes, 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
[recovery](references/recovery.md) for retries and conflicts; a receipt in accepted/conflict state is not a completed repair.

## Inspect propagation and report honestly

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.
Files in this package (19)
  • SKILL.md 7 KB
  • references/assertions.md 5 KB
  • references/conventions.md 14 KB
  • references/identity.md 5 KB
  • references/layout-company.md 1 KB
  • references/layout-concept.md 1 KB
  • references/layout-person.md 1 KB
  • references/layout-project.md 2 KB
  • references/meeting-entity-example.md 7 KB
  • references/profiles.md 7 KB
  • references/publication.md 23 KB
  • references/publish.md 6 KB
  • references/recovery.md 2 KB
  • references/retire-dated.md 4 KB
  • references/setup.md 2 KB
  • references/source-notes.md 1 KB
  • references/sources.md 3 KB
  • references/verify.md 3 KB
  • references/writing.md 2 KB

Versions

RepositoryScoreLicence
This page · steipete/clawdis90MIT
openclaw/openclaw90MIT

Database snapshot: 13.11.2026 · package version 9edff36a4ca6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90knowledge-claim-consolidation
    Review and consolidate Knowledge claims over a chosen scope - the unlinked residue after relinking, the claims on one hub or over-budget page, or the claims about one subject since a date. File claims on their most specific subject page, create pages for substantial subjects,…
  • 100knowledge-contradiction-auditor
    Knowledge Contradiction Auditor: Group statements by entity, time period and scope before comparing them. Use when the user asks for knowledge contradiction auditor work, or mentions knowledge, contradiction, auditor.
  • 90brain-knowledge
    Statements and corrections in Brain — the individual subject-predicate-object claims extracted from memories, their provenance, and their supersession history. Use when a stored fact is wrong, outdated or disputed, when the user asks where something came from or what changed and…
  • 90knowledge-recall
    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.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.