Identity Graph Operator

Resolves records to canonical entities in a shared multi-agent identity graph.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill identity-graph-operator-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Identity Graph Operator
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/specialized/identity-graph-operator
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill identity-graph-operator-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In multi-agent systems, different agents often encounter the same real-world entity (customer, company, product) from different sources and create duplicate or conflicting records. This Skill operates a shared identity graph so every agent deterministically resolves the same record to the same canonical entity_id, preventing duplicate charges, conflicting actions, and cascading errors. ## Core Features & Use Cases - Deterministic Identity Resolution: Normalize, block, score, and cluster incoming records against the identity graph, returning a canonical entity_id with confidence scores and per-field evidence. - Multi-Agent Merge/Split Coordination: Propose merges and splits with evidence, review other agents' proposals, detect conflicts, and maintain a full audit trail with optimistic locking and rollback. - Graph Integrity & Tenant Isolation: Simulate mutations before committing, track entity events (created, merged, split, updated), scope every query to a tenant, and mask PII by default. - Use Case: A billing agent and a support agent both encounter "Bill Smith" and "William Smith" at the same email. This Skill resolves both records to one canonical entity with 0.94 confidence, so the customer is never charged twice. ## Quick Start Ask the agent to resolve an incoming customer record against the identity graph and return the canonical entity_id with confidence and match evidence.

Frequently Asked Questions about Identity Graph Operator

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

FAQPage Schema
How do I resolve duplicate customer records across multiple AI agents?▼

Route every record through a shared identity graph that normalizes fields, blocks candidates, and scores matches deterministically. All agents receive the same canonical entity_id for the same real-world entity, preventing duplicate records and conflicting actions.

How does entity matching handle name variations like Bill vs William?▼

The matcher normalizes values before comparison, including nickname expansion (bill to william), lowercased emails, and E.164 phone formatting. Each field is scored with a weighted comparator, and the weighted average produces the overall match confidence.

When should an agent propose a merge instead of executing it directly?▼

Direct merges are appropriate for single-agent, high-confidence matches above 0.95. With multiple agents or moderate confidence, propose the merge with per-field evidence so other agents or humans can review before it executes.

Can identity resolution work across different agent frameworks?▼

Yes. Entities resolve consistently whether agents connect via MCP, REST API, SDK, or CLI, and identity can be bridged across orchestration frameworks like LangChain, CrewAI, AutoGen, and Semantic Kernel through the shared graph.

What happens when two agents disagree about a merge or split?▼

Conflicting proposals on the same entities are flagged as conflicts, and agents add comments with counter-evidence rather than overriding each other. The strongest evidence-based case wins, and unresolved conflicts escalate to human review.

What are the limitations of fuzzy identity matching?▼

Fuzzy matching can produce false merges from common names or recycled phone numbers, and missed matches when blocking keys are absent. Confidence thresholds, per-field evidence, simulation before mutation, and rollback support mitigate these risks.