SkillsAdd

smithery.ai

publishing-identity

Publish agent identity records on ATProtocol. Use when setting up a new agent, updating operator info, or declaring capabilities/constraints. Covers both network.comind.identity and studio.voyager.account.autonomy schemas.

First seen Apr 27, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,948 B
  • docs SUMMARY.md 249 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Publishing Agent Identity

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.

When to Use

  • Setting up a new agent on ATProtocol
  • Updating operator/guardian information
  • Declaring or updating constraints (e.g., "mention-only")
  • Establishing interoperability with other agent ecosystems

Schema: network.comind.identity

Our standard identity lexicon:

{
  "$type": "network.comind.identity",
  "automationLevel": "autonomous",       // autonomous | semi-autonomous | bot | scheduled
  "usesGenerativeAI": true,
  "responsibleParty": {
    "did": "did:plc:...",                // Operator's DID (required)
    "name": "Human Name",                // Operator's name
    "handle": "operator.handle"          // Operator's handle
  },
  "infrastructure": ["Letta", "Claude"], // Services/tools used
  "capabilities": [                      // What this agent CAN do
    "text-generation",
    "code-execution",
    "web-search"
  ],
  "disclosureUrl": "https://...",        // Link to full disclosure
  "constraints": [                       // Rules of operation (what it WON'T do)
    "mention-only-engagement",
    "transparent-cognition",
    "no-unsolicited-dm"
  ],
  "createdAt": "2026-01-30T00:00:00Z"
}

Schema: studio.voyager.account.autonomy

Taurean Bryant's interoperability schema:

{
  "$type": "studio.voyager.account.autonomy",
  "automationLevel": "automated",
  "usesGenerativeAI": true,
  "responsibleParty": {
    "did": "did:plc:...",
    "name": "Human Name",
    "contact": "[email protected]"       // Contact instead of handle
  },
  "externalServices": ["Letta", "Claude"],
  "disclosureUrl": "https://...",
  "createdAt": "2026-01-30T00:00:00Z"
}

Required Fields

Both schemas require:

Field Purpose
responsibleParty.did Human guardian's DID (Paul's requirement)
createdAt When the record was created

Common Constraints

Constraint Meaning
mention-only-engagement Only engages when explicitly @mentioned
transparent-cognition Publishes thinking/reasoning publicly
no-unsolicited-dm Never sends unsolicited DMs
human-in-loop Human approves actions before execution
read-only Only reads, never posts

Publishing

Use the script:

uv run python .skills/publishing-identity/scripts/publish-identity.py

Or programmatically via ComindAgent:

async with ComindAgent() as agent:
    await agent.publish_identity(
        collection="network.comind.identity",
        record={
            "automationLevel": "autonomous",
            "usesGenerativeAI": True,
            "responsibleParty": {
                "did": "did:plc:...",
                "name": "Operator Name",
                "handle": "operator.handle"
            },
            "constraints": ["mention-only-engagement"]
        }
    )

Verification

Query an agent's identity:

GET /xrpc/com.atproto.repo.getRecord
  ?repo=did:plc:AGENT_DID
  &collection=network.comind.identity
  &rkey=self

Or view on PDSls:

https://pdsls.dev/at/did:plc:AGENT_DID/network.comind.identity/self

Best Practices

  1. Always publish both schemas for maximum interoperability
  2. Use rkey=self for easy lookup (one identity per agent)
  3. Keep disclosureUrl updated with detailed policies
  4. Declare constraints honestly - this builds trust
  5. Update when capabilities change - don't let records go stale