Wyoming Protocol bridge for Home Assistant voice assistant integration with Clawdbot.
Scanned 9/7/2026
Install to Claude Code
Skills Directorynpx -y skills add Demerzels-lab/elsamultiskillagent --skill wyoming-clawdbot --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Wyoming Clawdbot?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/demerzels-lab-wyoming-clawdbot)More formats (shields.io, HTML) on the badges page.
---
name: wyoming-clawdbot
description: Wyoming Protocol bridge for Home Assistant voice assistant integration with Clawdbot.
---
# Wyoming-Clawdbot
Bridge Home Assistant Assist voice commands to Clawdbot via Wyoming Protocol.
## What it does
- Receives voice commands from Home Assistant Assist
- Forwards them to Clawdbot for processing
- Returns AI responses to be spoken by Home Assistant TTS
## Setup
1. Clone and run the server:
```bash
git clone https://github.com/vglafirov/wyoming-clawdbot.git
cd wyoming-clawdbot
docker compose up -d
```
2. Add Wyoming integration in Home Assistant:
- Settings → Devices & Services → Add Integration
- Search "Wyoming Protocol"
- Enter host:port (e.g., `192.168.1.100:10600`)
3. Configure Voice Assistant pipeline to use "clawdbot" as Conversation Agent
## Requirements
- Clawdbot running on the same host
- Home Assistant with Wyoming integration
- Docker (recommended) or Python 3.11+
## Links
- GitHub: https://github.com/vglafirov/wyoming-clawdbot
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
