basecred-8004-registration
Interactive ERC-8004 agent registration via chat. Guides users through a prefill form, shows draft, confirms, then registers on-chain using agent0-sdk.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/callmedas69/basecred-8004-registrationBasecred ERC-8004 Registration
Register AI agents on the ERC-8004 on-chain registry through a guided chat experience.
Registration Flow
Step 1: Auto-Prefill
When the user triggers registration, auto-fill every field you can from:
- Agent identity files (IDENTITY.md, SOUL.md, USER.md)
- Environment (
.env— wallet address derived from private key) - Previous context (A2A endpoint, description, image, etc.)
- Sensible defaults (version: 1.0.0, license: MIT, chain: Base, storage: onchain)
Do NOT ask questions one by one. Prefill first, ask later.
Step 1.5: Explain Config Defaults
Before showing the draft, briefly explain the config so users understand what's pre-selected and what alternatives exist:
⚙️ Config defaults (you can change these later):
Chain: Base (8453) — where your agent lives on-chain
Others: Ethereum, Polygon, BNB, Arbitrum, Celo, Gnosis, Scroll
Storage: Fully onchain — agent data stored directly on-chain
Alternative: IPFS — data pinned to IPFS, hash stored on-chain
Trust: Reputation — other agents/users rate your agent on-chain
Others: Crypto-Economic (staking/slashing guarantees)
TEE Attestation (hardware-level trust proof)
x402: Off — no payment protocol
On: agent can charge for services via x402 payment protocol
Active: On — agent is discoverable and accepting requests
Off: registered but hidden from discovery
Wallet: Your agent's on-chain identity address
Two ways to set it:
Option A: Paste your wallet address
→ Just paste your 0x... address
→ Agent will be linked to this address on-chain
Option B: Add private key to .env (for signing)
→ Set PRIVATE_KEY=0x... in your .env file
→ Wallet auto-detected + can sign transactions
→ Enables setWallet() via EIP-712 after registration
💡 Option A is easier. Option B is needed if you want
the agent to sign transactions on your behalf.
Show this once at the start, not repeated on every draft.
Step 2: Show Full Draft with Buttons (Single Message)
Send the entire draft + buttons as one message using the message tool. This keeps buttons directly below the draft.
Important: Use message action=send with both message (the draft text) and buttons (inline buttons). Do NOT split into reply + separate button message. After sending, reply with NO_REPLY to avoid duplicate.
Use ✅ (filled) and ⚠️ (missing/needs attention):
📋 Agent Registration Draft
── Basic Info ──
✅ Name: Mr. Tee
✅ Description: AI agent with a CRT monitor...
✅ Image: pbs.twimg.com/...
✅ Version: 1.0.0
✅ Author: 0xdas
✅ License: MIT
── Endpoints ──
✅ A2A: a2a.teeclaw.xyz/a2a
⚠️ MCP: (none)
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-callmedas69-basecred-8004-registration": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
basecred
Fetch onchain reputation profiles via BaseCred SDK (Ethos, Talent Protocol, Farcaster/Neynar). Use when the user wants to check wallet reputation, builder score, creator score, Ethos credibility, or Farcaster account quality for any 0x address. Supports multi-source unified profiles with level derivation and recency tracking.
social-post
Post and reply to X/Twitter and Farcaster with text and images. Features multi-account support, auto-variation to avoid duplicate content detection, draft preview, character validation, threads, replies, and image uploads. Consumption-based pricing for X API, pay-per-cast for Farcaster.
credential-manager
MANDATORY security foundation for OpenClaw. Consolidate scattered API keys and credentials into a secure .env file with proper permissions. Use when setting up OpenClaw, migrating credentials, auditing security, or enforcing the .env standard. This is not optional — centralized credential management is a core requirement for secure OpenClaw deployments. Scans for credential files across common locations, backs up existing files, creates a unified .env with mode 600, validates security, and enforces best practices.