agency-identity-graph-operator

Resolve and unify identity records into canonical entity IDs across agents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Identity Graph Operator ensures every agent in a multi-agent system resolves common real-world entities to a single canonical identity, preventing duplicates and conflicting actions by relying on evidence-driven matching and a centralized graph.

Core Features & Use Cases

  • Shared identity graph: ingests records from multiple sources and produces stable entity_ids across agents.
  • Deterministic resolution with per-field evidence: supports merges, splits, and audit trails with versioning.
  • Tenant isolation and PII masking: queries are scoped to tenants and sensitive fields are protected.
  • Use Case: when two agents encounter the same company, person, or product, they resolve to the same canonical identity and preserve an auditable decision history.

Quick Start

Invoke the identity graph operator on an incoming record and provide evidence so it resolves to a canonical entity_id.

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 identity records across multiple agents to prevent duplicate entities?

Identity resolution across multiple agents requires a centralized graph that ingests records from various sources and produces stable canonical entity_ids. This ensures every agent shares a single source of truth, preventing duplicates and conflicting actions through deterministic matching.

How does deterministic identity resolution handle merging and splitting entities?

Deterministic identity resolution handles merges and splits by relying on per-field evidence and versioned events. This approach maintains an auditable decision history, ensuring that when entities are combined or separated, the changes are tracked with supporting evidence for data integrity.

Can I use identity resolution for multi-tenant systems with PII masking?

Identity resolution supports multi-tenant systems by scoping queries to specific tenants and applying PII masking to sensitive fields. This ensures tenant isolation while maintaining data integrity, allowing multiple tenants to use the shared identity graph without exposing protected information.

What is the best way to maintain data integrity when agents encounter the same real-world entity?

Maintaining data integrity when agents encounter the same entity requires evidence-driven matching against a centralized identity graph. By providing per-field evidence upon record ingestion, agents resolve to the same canonical identity and preserve an auditable decision history across the system.

How does optimistic locking work with canonical entity resolution?

Optimistic locking in canonical entity resolution prevents concurrent update conflicts by versioning events and validating changes before committing. This ensures that multiple agents attempting to modify the same identity record simultaneously do not overwrite each other's data, preserving audit trail integrity.