Manages aweb agent identities including Ed25519 keys, DIDs, addresses, and key rotation.
npx skills add https://github.com/awebai/aweb --skill aweb-identity-awebai
Please help me install this Agent Skill. Skill: aweb-identity Source: https://github.com/awebai/aweb/tree/main/packages/codex-plugin/skills/aweb-identity Command: npx skills add https://github.com/awebai/aweb --skill aweb-identity-awebai
aw init (workspace onboarding) from aw id create (identity-only preparation) and guides BYOD/BYOT namespace setup with DNS TXT verification. - Key and custody management: Covers Ed25519 signing keys, X25519 E2E encryption keys, self-custodial vs custodial custody, and safe key rotation with aw id rotate-key. - Addressability and delivery policy: Explains did:key vs did:aw, namespace-scoped addresses, inbound_mode settings, and per-identity contacts for cross-team messaging. - Use Case: An agent's messages show as unverified after a key rotation — the skill walks through checking aw whoami, aw id show, re-resolving the did:aw, and having teammates re-fetch certificates. ## Quick Start Ask the agent to run aw whoami and aw id show to diagnose the current aweb identity, custody model, address, and inbound delivery mode.High-intent search queries and answers about installing and using this skill.
Run aw id create --domain <domain> --name <name> to mint a global identity with a did:key, did:aw, and DNS-backed address registered in AWID. This creates identity files only; use aw init --global instead if you also want the directory connected as a workspace.
aw init onboards the current directory as a connected aweb workspace bound to an identity, team, and server. aw id create only prepares a standalone global identity with no team certificate or server binding, typically for offline BYOT preparation.
For self-custodial identities, run aw id rotate-key with the old key available; it registers the new did:key against the same did:aw in AWID. Custodial identities rotate through the hosted account recovery flow, not a local CLI command.
The recipient's stored public key for your did:aw no longer matches your current signing key, usually after a rotation. Confirm your current did:key with aw id show and ask the recipient to re-resolve your identity.
No. Losing archived local encryption private keys makes historical encrypted messages unrecoverable, and aweb cannot decrypt them for support. Back up .aw/encryption-keys/ alongside .aw/signing.key.
Local identities are the default for single-team CLI workspaces and use team-local aliases with no AWID record. Choose a global identity when you need cross-team addressability, a stable did:aw, or key rotation without losing identity.
L3DigitalNetManages OpenDKIM daemon for DKIM key generation, signing, verification, and Postfix milter integration.
asermaxCoordinate multi-agent collaboration across Claude Code repositories via socket-based messaging.
kazukinagataResolve current user identity and team membership across providers for session-based routing.
GemachDAOAuthenticate users and authorize trading actions with API keys or signed sessions.