specialized-identity-graph-operator

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

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/30eggis/walwal-harness --skill specialized-identity-graph-operator-30eggis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specialized-identity-graph-operator
Source: https://github.com/30eggis/walwal-harness/tree/main/HR-Resource/specialized-identity-graph-operator
Command: npx skills add https://github.com/30eggis/walwal-harness --skill specialized-identity-graph-operator-30eggis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In multi-agent systems, different agents 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 gets the same canonical entity_id for the same entity, deterministically, even under concurrent writes. ## Core Features & Use Cases - Deterministic Identity 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, with conflict detection between agents. - Graph Integrity & Auditability: Routes all mutations through a single engine with optimistic locking, simulation previews, event history (entity.created, entity.merged, entity.split), and rollback support. - 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, preventing double charges and duplicate customer records. ## Quick Start Ask the identity graph operator to resolve an incoming customer record against the shared identity graph and return the canonical entity_id with confidence and per-field match evidence.

Frequently Asked Questions about specialized-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 by keys like email domain, and scores matches field-by-field. All agents receive the same canonical entity_id for the same real-world entity, preventing duplicates.

How does fuzzy name matching work in identity resolution?▼

Names are normalized through nickname expansion (Bill to William, Bob to Robert) and lowercasing before comparison. The matcher combines name scores with exact email and normalized phone matches to produce a weighted confidence score.

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

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

Can identity resolution handle concurrent writes from multiple agents?▼

Yes. All mutations go through a single engine with optimistic locking using expected_version checks. Mutations can be simulated before committing, and conflicts between agents proposing opposite actions are flagged for review.

What happens when two agents disagree about an entity merge?▼

Both proposals 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 automated entity matching?▼

False merges can occur with common names or recycled phone numbers, and missed matches happen when blocking keys are absent. Records below the auto-match threshold require proposal review, and PII stays masked unless an admin authorizes access.