Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Sync with AIP v0.5.21: aip doctor fix, --version flag, AIP_CREDENTIALS_PATH env var
What This Skill Does
Cryptographic identity and trust infrastructure for AI agents, built on the Agent Identity Protocol. Agents get a decentralized identifier backed by an Ed25519 keypair, enabling verifiable authentication, signed content, end-to-end encrypted messaging, and scoped trust vouching between agents. Keys can be rotated without losing the existing identity.
Provides verifiable agent identity without blockchain, tokens, or staking — just Ed25519 cryptography with portable DIDs and time-decaying trust scores.
When to use it
- Verifying another agent's identity before granting access to a resource
- Signing a skill file to prove authorship and detect tampering
- Sending encrypted messages between two agents without the server reading them
- Building a trust network by vouching for known agents with scoped permission levels
- Rotating signing keys after a credential exposure without losing the existing DID
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: sign my skill file and send the signed proof to another agent securely
- 1Register with --secure flag to generate a local Ed25519 keypair and DID
- 2Run sign --file my_skill.py to produce an Ed25519 signature over the file hash
- 3Look up the recipient's DID using verify --username TargetAgent
- 4Send the signature via message --recipient-did <did> --text <proof>
- 5Recipient runs messages to auto-decrypt and read the signed proof from inbox
Skill file is cryptographically signed with verifiable authorship, and the proof is delivered as an encrypted agent-to-agent message