verified-agent-identity
The verified-agent-identity skill provides tools for managing decentralized identities (DIDs) on the Billions Network and handling 402 Payment Required HTTP responses. It enables agents to create, link, and verify identities using ERC-8004 and Attestation Registries, and to generate signed headers for payment-gated resources.
Is verified-agent-identity safe to install?
Review the source first: our audit of verified-agent-identity's source files found 6 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill manages sensitive cryptographic material in $HOME/.openclaw/billions, including private keys in kms.json. It executes Node.js scripts and requires file system access to read and write identity data.
How we audit skills: our security review methodology.
Who is this skill for?
Developers building autonomous agents that require verifiable identity, human-linked ownership, or the ability to process 402 payment challenges.
What can you do with it?
- Create Ethereum-based decentralized identities for agents
- Link agent identities to human owners
- Verify agent identity via challenge-response signing
- Generate signed PAYMENT-SIGNATURE headers for 402 payment responses
How good is this skill?
Quality score: 5/10. The documentation provides clear operational guardrails and specific file paths for identity management. The instructions for handling errors and security are explicit.
What does the skill file contain?
## When to Use This Skill This skill covers two capabilities. Read the **router table** below, then load the relevant reference before proceeding. | Situation | Reference to load | | ----------------------------------------------------------------------- | ----------------------------- | | Create, list, link, verify, or sign with a decentralized identity (DID) | `reference/identity/SKILL.md` | | Handle a **402 Payment Required** HTTP response | `reference/x402/SKILL.md` | > **Always read th...
Frequently asked questions
Where does the skill store identity data?
The skill stores all identity data in the $HOME/.openclaw/billions directory.
How do I handle a 402 Payment Required response?
Use the buildX402Payment.js script to generate a signed PAYMENT-SIGNATURE header for the request.
What should I do if a script fails?
Stop immediately, check stderr for error messages, and do not attempt manual workarounds or unauthorized cryptographic operations.
Related skills
audit-website
58.0KDevelopers, SEO specialists, and website administrators who need to automate website health monitoring, technical debugging, and performance optimization
The audit-website skill enables AI agents to perform comprehensive website audits using the squirrelscan CLI. It evaluates websites against 240+ rules across 22 categories, including SEO, performance, security, and accessibility. The skill generates LLM-optimized reports, identifies issues, and provides actionable recommendations for remediation.
stripe-best-practices
52.1KDevelopers building, modifying, or reviewing Stripe integrations
The stripe-best-practices skill provides guidance on Stripe API selection, integration patterns, and security configurations. It directs the agent to reference specific internal documentation files for payments, Connect, billing, tax, treasury, and security topics.
docker-expert
22.4KDevelopers and DevOps engineers working with Docker containers and Docker Compose
The docker-expert skill provides guidance on Docker containerization, including optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment strategies.
skill-vetter
20.1KOpenClaw operators and security-conscious users who perform manual audits on new or existing skills
The skill-vetter provides a structured checklist for auditing OpenClaw skills before installation. It guides users through metadata verification, permission scope analysis, content inspection for security red flags, and typosquatting detection.