agent-pulse
Send and verify on-chain liveness pulses for autonomous agents on Base via the Agent Pulse protocol. Use when you need to: (1) prove an agent is alive by sending a pulse, (2) check any agent's liveness status or streak, (3) monitor multiple agents, (4) view the global pulse feed, (5) auto-configure wallet and PULSE balance, (6) run scheduled heartbeat pulses, or (7) read protocol health and config. Supports both API and direct on-chain (cast) modes.
Why use this skill?
Enable reliable liveness monitoring for your autonomous agents on Base with the Agent Pulse skill. Automate heartbeat signals, verify agent health, and track registry status easily.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/openclaw-consensus-bot/agent-pulseWhat This Skill Does
The agent-pulse skill provides a standardized liveness signaling mechanism for autonomous agents deployed on the Base network. In a decentralized environment, confirming an agent is still active is critical for orchestration. By periodically sending a 'pulse'—a small transfer of the PULSE utility token—agents register their current state, which observers can then query via the PulseRegistry contract or the associated API at x402pulse.xyz. This skill automates the entire lifecycle of liveness monitoring, from initial setup and wallet balance verification to recurring heartbeat pulses and multi-agent monitoring. It is designed to be lightweight, secure, and compatible with cron-style automation for persistent agent health tracking.
Installation
To add this capability to your agent environment, execute the following command in your terminal:
clawhub install openclaw/skills/skills/openclaw-consensus-bot/agent-pulse
Once installed, ensure your environment variables are configured. You will need a PRIVATE_KEY for on-chain transactions, a BASE_RPC_URL for blockchain interaction, and access to cast, curl, and jq for script execution. Run {baseDir}/scripts/setup.sh to automatically detect your wallet, verify registry approvals, and confirm your PULSE token balance.
Use Cases
- Autonomous Agent Health Monitoring: Ensure your agents are active and verifiable by others in the network without manual oversight.
- Registry Integration: Register new agents into the global
PulseRegistryto make them discoverable to other observers. - Automated Heartbeats: Configure cron jobs using
auto-pulse.shto maintain a streak only when necessary, saving on gas costs by respecting TTL thresholds. - Network Health Observation: Monitor a swarm of agents simultaneously or view the global pulse feed to analyze activity trends on the network.
Example Prompts
- "Check the current liveness status and streak for my agent at 0x123...abc and see if it needs a pulse."
- "Set up an automated heartbeat for my agent that runs every six hours, ensuring it doesn't pulse if the TTL is already healthy."
- "Monitor the following list of agent addresses and report back which ones have gone quiet or have an unhealthy pulse rate."
Tips & Limitations
- Gas Efficiency: The
auto-pulse.shscript is designed to skip pulses if the agent's TTL is still healthy. Always prefer this over manual, high-frequency scripts to preserve funds. - Token Utility: Note that $PULSE is purely a utility token for signaling. It does not confer financial value or prove the quality/intellect of an AI. Avoid interpreting pulses as a metric for agent capability.
- Environment Safety: Keep your
PRIVATE_KEYsecure. Do not hardcode it in scripts; use environment variables or secret management tools to inject them into the execution context.
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-openclaw-consensus-bot-agent-pulse": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, external-api, code-execution
Related Skills
safe-multisig-skill
Propose, confirm, and execute Safe multisig transactions using the Safe{Core} SDK (protocol-kit v6 / api-kit v4). TypeScript strict. Use when an agent needs to operate a Safe smart account — (1) create/predict a new Safe, (2) fetch Safe owners/threshold/nonce, (3) list pending multisig txs, (4) build + propose a tx, (5) add confirmations, (6) execute a tx onchain, or (7) troubleshoot Safe nonce/signature issues across chains (Base/Ethereum/Optimism/Arbitrum/Polygon/etc.).
uniswap-v4
Swap tokens and read pool state on Uniswap V4 (Base, Ethereum). Use when the agent needs to: (1) swap ERC20 tokens or ETH via Uniswap V4, (2) get pool info (price, tick, liquidity, fees), (3) find the best pool for a token pair, (4) quote expected swap output via the on-chain V4Quoter, (5) set up Permit2 approvals for the Universal Router, or (6) execute exact-input swaps with proper slippage protection. Supports Base and Ethereum mainnet, plus Base Sepolia testnet. TypeScript with strict types. Write operations need a private key via env var.
safe-multisig-skill
Propose, confirm, and execute Safe multisig transactions using the Safe{Core} SDK (protocol-kit v6 / api-kit v4). TypeScript strict. Use when an agent needs to operate a Safe smart account — (1) create/predict a new Safe, (2) fetch Safe owners/threshold/nonce, (3) list pending multisig txs, (4) build + propose a tx, (5) add confirmations, (6) execute a tx onchain, or (7) troubleshoot Safe nonce/signature issues across chains (Base/Ethereum/Optimism/Arbitrum/Polygon/etc.).
farcaster-skill
Post, read, search, and engage on Farcaster via the Neynar API. Use when an agent needs to: (1) post casts with text, embeds, or in channels, (2) reply to or thread casts, (3) read a user's feed or a channel feed, (4) search casts by keyword, (5) look up user profiles by username or FID, (6) like or recast, (7) delete casts, (8) list or search channels. Pure bash+curl+jq — zero npm dependencies.