Our review
Checks if the bead daemon (bd) is running and responsive via its socket.
Strengths
- Quick and simple health check for the bead daemon
- No installation required, uses existing bd command
- Provides status output for troubleshooting
Limitations
- Only checks socket availability, not full functionality
- Requires bd daemon to be installed and running
Use to verify the bead daemon is operational before running bead-related commands.
Do not use as a comprehensive health check for the entire beads system.
Security analysis
SafeThe skill only checks a local socket file (`bd.sock`) to confirm a daemon is running. It involves no destructive, exfiltrating, or elevated operations. The commands are simple status checks with no risk of harm or data leakage.
No concerns found
Examples
ping-beadsname: ping-beads description: "Verify the bead daemon is alive and responsive" metadata: { "openclaw": { "emoji": "🫘", "requires": { "bins": ["bd"] }, "install": [], }, }
Ping Beads
Verify the bead daemon is alive and responsive. Checks the bd.sock socket to confirm the bead daemon (bd) is running and accepting connections.
Commands
# Check if the bead daemon is alive (checks bd.sock)
ping-beads
# Show detailed bead daemon status
ping-beads status
Install
No installation needed. bd is expected to be in PATH as part of the beads system.
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.