SKILLEMALL.ai
RU Sign in

BC home-assistant

Control Home Assistant — lights, switches, climate, scenes, and automations — from your agent. Create and risk-check automations from natural language, validate YAML before deploying, and act on proactive suggestions. Connects over MCP with OAuth 2.0 (Selora Connect) — no long-lived tokens.

ClawHub Agent Skills author: Philippe Lafoucrière v1.0.6 MIT-0 2 files body ≈ 2 023 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process C 64/100 · Has gaps — weak spots: result and completion, when it triggers, consistency

IntegrationInfrastructureAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
73
Run on models
none yet
Process rating
C
64/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 64/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 10 mutating operations with no state check
  • 40Consistency. Frontmatter name (home-assistant) differs from the folder (homeassistant-selora)
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 42 steps
  • 100Failures and branches. 4 branches, has a failure section
  • 100Execution cost. Instruction body is 2023 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 291: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 42 items
  • +4Has examples (3 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.

External checks

ClawHub: suspicious
The skill mostly matches its Home Assistant purpose, but it asks users to paste an OAuth callback URL containing authorization data into chat, so it should be reviewed before installation.
LLM: suspicious (high) · VirusTotal: · 9 Jun 2026