Agent skill · steipete
knowledge-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, retire duplicates, supersede status snapshots and replaced claims by an existing claim, and fold durable outcomes into page State. Use for claim cleanup, consolidation, or the Knowledge Consolidation scribe.
What it needs
About 8k tokens when loaded.
What this skill does
Claim consolidation review Read shared conventions and publication before writes. Claims accumulate faster than pages are curated. knowledgeremember saves a claim without a subject page when no name in it matches exactly one page, and scheduled maintenance's knowledgerelink links only claims whose source page is an entity page or whose text names exactly one page. Linked claims pile up too: a hub page collects status snapshots, duplicates and claims that belong on a more specific subject. This review runs one procedure over a chosen scope. Work in this order: choose the scope, link, then duplicates, replaced claims and snapshot series, then page prose. 1. Choose the scope and enumerate it Call knowledgestatus for the intended scope and knowledgeontology for the current fingerprint. Then enumerate exactly one starting set: Unlinked residue (the default, and the only scope of scribe runs). Run knowledgerelink without dryRun first so every remembered claim it can link is linked. Then list the residue with knowledgerelink dryRun: true, include: "all" and limit: 10, following nextCursor: every current claim with no linked page and no source page, whichever tool saved it. Each call reports at most 10 examples per outcome, so a limit of 10 returns every claim it examined. One page, for a hub page or a page over its size budget. List its current claims with knowledgeconnections id, direction: "claims", view: "full" and includeCards: true, following nextOffset with the same filters. Restart when snapshot changes. On a hub, group from the cards first and work one group at a time; do not read every claim in full up front. One subject, optionally since a date. When the subject has a page, list its claims with knowledgetimeline entity, timeField: "recordedat" and since, following nextOffset. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/knowledge-claim-consolidation