homeassistant-bridge

Bidirectional Home Assistant integration — HA cameras in, detection results out

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/integrations/homeassistant-bridge/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with a clear architecture diagram and a real bundle script, but it stops short of actionable usage guidance — there is no example of running bridge.py or handling its emitted events, and the operational workflow lacks validation checkpoints.

Suggestions

Add a usage example showing how to run the bridge, e.g. `python scripts/bridge.py --ha-url http://... --ha-token $TOKEN --cameras camera.front_door` plus the expected `ready`/`frame`/`error` JSON events.

Spell out the operational workflow as numbered steps with a validation checkpoint (e.g. confirm the `ready` event lists cameras before processing, and retry on retriable `error` events).

Verify the `pip install -r requirements.txt` reference — no requirements.txt exists in the bundle — by either adding the file or inlining the dependency (e.g. `pip install requests`).

Dimension	Reasoning	Score
Conciseness	The body is lean — a short overview, a compact ASCII data-flow diagram, and a two-line setup block — with no padding or explanation of concepts Claude already knows, matching the score-3 "every token earns its place" anchor.	3 / 3
Actionability	The only executable code is the venv/pip setup block; there is no example showing how to invoke scripts/bridge.py, what arguments to pass, or what output events to expect, so key usage details are missing per the score-2 anchor.	2 / 3
Workflow Clarity	A sequence exists only for setup, while the operational workflow (run the bridge, handle frame/error/ready events, push results back) is not stepped out and has no validation checkpoints, matching the score-2 "sequence present but checkpoints missing" anchor.	2 / 3
Progressive Disclosure	The skill is under 50 lines with well-organized sections (How It Works, Wraps, Setup) and a single one-level-deep bundle file (scripts/bridge.py) tied via frontmatter, so per the simple-skills note progressive disclosure scores 3.	3 / 3
	Total	10 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly conveys the bidirectional HA camera integration niche but omits any explicit "Use when" trigger guidance, capping completeness and trigger quality at 2. It is concise and free of fluff, yet lacks the keyword coverage and distinctiveness that explicit triggers would provide.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when integrating Home Assistant cameras with Aegis or when the user mentions HA camera feeds, image_processing entities, or detection results."

Broaden trigger terms to include common variations users say (e.g. "Home Assistant", "HA", "camera feeds", "image_processing entities", "smart camera automations").

List a couple more concrete actions to lift specificity toward 3 (e.g. "captures HA camera frames, runs detection/VLM/REID, and publishes image_processing entities").

Dimension	Reasoning	Score
Specificity	The phrase "Bidirectional Home Assistant integration — HA cameras in, detection results out" names the domain and two concrete data flows, but does not enumerate multiple specific actions, so it falls short of the multi-action score-3 anchor.	2 / 3
Completeness	It states what the skill does but includes no "Use when..." or equivalent trigger guidance, so per the guidelines completeness is capped at 2 even though the "what" is clear.	2 / 3
Trigger Term Quality	"Home Assistant", "HA cameras", and "detection results" are relevant keywords a user might say, but common variations and explicit trigger phrasing are missing, matching the score-2 anchor of partial keyword coverage.	2 / 3
Distinctiveness Conflict Risk	The HA-camera niche is fairly specific, but without explicit triggers it could still overlap with other Home Assistant skills, matching the score-2 "somewhat specific but could overlap" anchor.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: SharpAI/DeepCamera
Path: skills/integrations/homeassistant-bridge/SKILL.md
Commit: 2264fcb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.