identity-graph-operator

Resolve records against a shared identity graph with evidence-based matching.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/Likas07/t3code-skills --skill identity-graph-operator-likas07
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: identity-graph-operator
Source: https://github.com/Likas07/t3code-skills/tree/main/skills/identity-graph-operator
Command: npx skills add https://github.com/Likas07/t3code-skills --skill identity-graph-operator-likas07

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that multiple AI agents in a system consistently identify and refer to the same real-world entities, preventing data duplication and conflicts.

Core Features & Use Cases

  • Canonical Identity Resolution: Guarantees that any agent asking about a person, company, or product receives the same unique identifier.
  • Merge & Split Coordination: Manages the process of merging duplicate records or splitting incorrectly combined ones, with clear evidence.
  • Use Case: In a customer service system, when a new support ticket arrives, this Skill ensures it's linked to the correct, existing customer record, even if the ticket uses a slightly different name or contact information than previous records.

Quick Start

Use the identity-graph-operator skill to resolve the provided record against the shared identity graph.

Frequently Asked Questions about identity-graph-operator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does deterministic entity resolution work in multi-agent systems?

Deterministic entity resolution operates a shared identity graph to ensure multiple AI agents consistently identify real-world entities. It uses evidence-based matching to guarantee canonical identification and prevent data duplication across the system.

What is the best way to prevent duplicate records when AI agents use different contact information?

Canonical identity resolution prevents duplicate records by linking new entries to the correct existing entity. It evaluates per-field evidence to match records even when a ticket uses slightly different names or contact information than previous records.

How do I manage merging duplicate records and splitting incorrectly combined ones?

Merge and split coordination manages duplicate record merging and incorrectly combined record splitting. The process relies on clear evidence to propose merges and detect conflicts, ensuring data governance across the identity graph.

Does identity resolution require tenant isolation for multi-agent data governance?

Yes, tenant isolation is required for identity resolution in multi-agent environments. The shared identity graph requires a robust identity engine with per-field evidence and tenant isolation to maintain secure and accurate entity matching.

When do I need a shared identity graph for entity matching?

You need a shared identity graph when multiple AI agents must consistently refer to the same real-world entities. It ensures canonical identification for people, companies, or products, preventing data conflicts and duplication across agents.