agency-identity-graph-operator

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

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-identity-graph-operator-immamdouhaboammar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-identity-graph-operator
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/identity-graph-operator
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-identity-graph-operator-immamdouhaboammar

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 Entity Resolution: Normalizes fields (emails, E.164 phones, nickname expansion), blocks candidates, scores field-level matches, and returns a canonical entity_id with confidence scores. - Evidence-Based Merge Proposals: Proposes merges and splits with per-field evidence and reason codes so other agents or humans can review before execution. - Conflict Detection & Audit Trail: Flags conflicting proposals between agents, tracks every mutation with optimistic locking, event history, and rollback support. - Use Case: A billing agent and a support agent both encounter "Bill Smith" and "William Smith" at the same email. The operator resolves both to one canonical entity with 0.94 confidence, preventing a duplicate customer record and double charge. ## 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 agency-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 then receive the same canonical entity_id for the same real-world entity, eliminating duplicates.

How does fuzzy entity matching handle nicknames like Bill and William?▼

The matcher normalizes names through a nickname expansion map before comparison, so Bill maps to William. Combined with exact email and phone matches, this produces a high-confidence match with per-field evidence scores.

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

Direct merges are appropriate for single-agent scenarios with confidence above 0.95. In multi-agent settings with moderate confidence, the agent should propose the merge with per-field evidence so other agents or humans can review before execution.

Can the identity graph isolate data between different tenants?▼

Yes, every query is scoped to a tenant and entities never leak across tenant boundaries. PII is masked by default and only revealed when explicitly authorized by an admin.

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

Both proposals are flagged as conflicts and neither is executed automatically. Agents add comments with counter-evidence, and the strongest evidence-based case wins, with human review for unresolved disputes.

What are the limitations of automated entity resolution?▼

False merges can occur with common names or recycled phone numbers, and missed matches happen when blocking keys are absent. Low-confidence matches below the auto-merge threshold require proposal review rather than automatic resolution.