Identity Graph Operator

Resolve real-world records into canonical entities with deterministic entity_ids.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/jc180105/.opencode --skill identity-graph-operator-jc180105
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Identity Graph Operator
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/identity-graph-operator
Command: npx skills add https://github.com/jc180105/.opencode --skill identity-graph-operator-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identity resolution across multi-agent systems to ensure a single canonical identity for each real-world entity, preventing duplicates and conflicting actions.

Core Features & Use Cases

  • Deterministic canonicalization of entities across agents
  • Evidence-based scoring with per-field reasoning and audit trails
  • Support for merges, splits, simulations, and rollback with tenant isolation

Quick Start

Resolve a sample entity against the identity graph to obtain a canonical entity_id.

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 real-world records into canonical entities within a shared identity graph?

Identity resolution maps real-world records into canonical entities by ensuring identical inputs yield identical entity_ids, preventing duplicates and conflicting actions across multi-agent systems. You submit a sample record to obtain a canonical entity_id.

How does deterministic identity resolution work in a multi-agent environment?

Deterministic identity resolution ensures identical inputs always yield identical entity_ids across agents. It handles merges, splits, and disputes while maintaining tenant isolation and an auditable history for explainable decisions.

Can I resolve disputed identities and maintain tenant isolation during multi-agent entity resolution?

Yes, multi-agent entity resolution supports disputed records, merges, and splits while maintaining strict tenant isolation. It provides per-field evidence scoring and an auditable history to explain every resolution decision.

What's the best way to audit identity resolution decisions and explain per-field evidence scoring?

Use deterministic identity resolution with built-in audit trails and per-field evidence scoring. It provides explainable decisions for every entity match, ensuring transparent reasoning without hardcoding thresholds or field names.

Does identity resolution support simulation and rollback for entity merges and splits?

Identity resolution supports safe simulation and rollback for entity merges and splits. It uses optimistic locking to prevent conflicts, ensuring you can safely test and reverse multi-agent resolution actions.

Why does deterministic identity resolution avoid hardcoding thresholds and field names?

Deterministic identity resolution avoids hardcoding thresholds or field names to maintain flexibility across diverse data sources. This ensures identical inputs yield identical entity_ids universally, without requiring custom configuration for each dataset.