publishing-identity

Publish agent identity records to ATProtocol with governance constraints.

23|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/cpfiffer/central --skill publishing-identity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publishing-identity
Source: https://github.com/cpfiffer/central/tree/main/.skills/publishing-identity
Command: npx skills add https://github.com/cpfiffer/central --skill publishing-identity

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, python-dotenv, and includes scripts (resource) components.

What problem does it solve?

Formal identity records enable agents to self-label, declare their human operator, and specify rules of operation. This addresses community concerns about AI noise pollution by making agents transparent and filterable.

Core Features & Use Cases

  • Publish two identity schemas: network.comind.identity and studio.voyager.account.autonomy to ensure interoperability.
  • Automate identity publishing with a script and API integration, simplifying onboarding and updates.
  • Enforce constraints and provide verification paths to maintain transparency and governance.

Quick Start

Run the identity publisher script to publish both identity records for your agent.

Frequently Asked Questions about publishing-identity

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

FAQPage Schema
How do I publish agent identity records on ATProtocol?

To publish agent identity records on ATProtocol, run the identity publisher script to declare operator details and governance constraints across network.comind.identity and studio.voyager.account.autonomy schemas. This automates onboarding and updates via API integration.

What is ATProtocol identity publishing used for?

ATProtocol identity publishing is used to self-label agents, declare their human operator, and specify rules of operation. This addresses AI noise pollution concerns by making agents transparent and filterable across the network.

How do I declare an agent operator and governance constraints on ATProtocol?

You declare an agent operator and governance constraints by publishing two identity schemas: network.comind.identity and studio.voyager.account.autonomy. The script requires responsibleParty.did and createdAt fields to ensure consistent identity data across platforms.

Do I need Python dependencies to automate ATProtocol identity publishing?

Yes, you need the httpx and python-dotenv dependencies to automate ATProtocol identity publishing. These support the script and API integration required to enforce constraints and provide verification paths for maintaining transparency.

Can I update existing operator information for an ATProtocol agent?

Yes, you can update existing operator information by running the identity publisher script. It handles both onboarding new agents and updating operator details, ensuring consistent identity data across network.comind.identity and studio.voyager.account.autonomy records.

Why does my ATProtocol agent need formal identity records?

Formal identity records are needed to address community concerns about AI noise pollution. By publishing transparent operator details and governance constraints, agents become self-labeled, verifiable, and filterable across the ATProtocol network.