Agent skill · steipete
knowledge-entities
Resolve and enrich Knowledge people, companies, projects, and concepts during an authorized ingestion or entity update, with sourced State, source notes, and links. Read-only identity questions do not authorize writes.
What it needs
About 3k tokens when loaded.
What this skill does
Resolve and enrich entities Find who or what an entity is before asking, decide whether it deserves a page, then write a sourced profile, its source note and links. Read a reference only when its step needs it. Shared references are identical across Knowledge skills; if another Knowledge skill brought you here, don't reread ones you already read. setup: always, first (status, ontology, search) identity: resolving an entity; whether to create a page enrichment: tiers, what to extract, external lookups, bulk runs profiles: page structure, creating or updating writing: before writing page prose sources: retaining sources and citing them assertions: claims and relationships about the entity publish: page writes and batches recovery: any uncertain, rejected or conflicting write verify: verification and report evidence repair: only for an authorized evidence-set repair Contract Check Knowledge before asking the user or searching externally. Ask only with a hypothesis. No stubs or placeholders: every page's first line says who or what it is. Every fact has an inline citation. The source links to every enriched page, and each enriched page has a source note: its relationship with the source. Scale effort to importance. When in doubt, don't create a page. Never overwrite user-written assessments; flag contradictions with both citations. Steps 1. Identify entities List the people, companies, projects and concepts in the source. Separate actual participants from third parties mentioned in passing. Done when: each entity is marked participant, substantive or incidental. 2. Resolve each one Run the resolve chain in identity. Reuse an existing page's ID. Decide create, update or skip using its page-creation rules, and pick the best-fitting declared ontology type. Done when: each entity has an existing ID, a create decision with a type, or is skipped; ambiguous identities are recorded as partial or unresolved. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/knowledge-entities