CtrlK
BlogDocsLog inGet started
Tessl Logo

ha-automation-trigger

Fire Aegis detection events in Home Assistant

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/automation/ha-trigger/SKILL.md
SKILL.md
Quality
Evals
Security

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 efficient and well-structured for a simple skill, with a copy-paste-ready automation example. Its main gap is incomplete actionability — a referenced requirements.txt is missing and no concrete script invocation is shown.

Suggestions

Include the missing requirements.txt in the bundle or replace the `pip install -r requirements.txt` line with the actual dependency (e.g. `pip install requests`).

Add a concrete invocation example for the script, such as `python3 scripts/ha_trigger.py --ha-url http://homeassistant.local:8123 --ha-token <token>`, so the action is fully executable from the skill alone.

Add a brief verification step (e.g. checking that HA responds at /api/ or that an `aegis_detection` event appears) to give the workflow an explicit success checkpoint.

DimensionReasoningScore

Conciseness

The body is lean with no over-explanation of concepts Claude already knows; the short intro, YAML example, and setup block each earn their place.

3 / 3

Actionability

The HA automation YAML and venv/pip setup are concrete, but setup references a requirements.txt that is not present in the bundle and the body gives no executable invocation of scripts/ha_trigger.py, leaving guidance incomplete.

2 / 3

Workflow Clarity

The single task is mostly unambiguous and setup steps are listed, but there are no verification checkpoints (e.g. confirming HA connectivity or that an event fired) for a networked operation, so it does not reach 3.

2 / 3

Progressive Disclosure

This is a simple, under-50-line skill with well-organized sections and the one bundle file (scripts/ha_trigger.py) referenced via the frontmatter capability, satisfying the simple-skill exception for a top score.

3 / 3

Total

10

/

12

Passed

Description

57%

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 is concise and specific to its niche, but it only states what the skill does without an explicit "when to use it" trigger clause. Adding a "Use when..." clause and richer natural keywords would raise completeness and trigger-term quality.

Suggestions

Append a "Use when..." clause naming the situations that should trigger this skill (e.g. turning on lights, sending notifications, or running HA automations from Aegis detections).

Add common natural trigger terms users would actually say, such as "HA automations", "smart home", "lights", or "notifications", alongside "Home Assistant" and "Aegis".

Optionally list a second concrete action (e.g. "trigger HA automations") to move specificity from one action toward multiple concrete actions.

DimensionReasoningScore

Specificity

"Fire Aegis detection events" names a domain and one concrete action, but does not list multiple specific actions, matching the score-2 anchor.

2 / 3

Completeness

The "what" is present (firing detection events) but there is no explicit "Use when..." clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

"Home Assistant" and "Aegis detection events" are relevant keywords, but common natural variations a user would say (e.g. "HA automations", "turn on lights", "notifications") are missing, so it sits at 2 rather than 3.

2 / 3

Distinctiveness Conflict Risk

The pairing of "Aegis detection events" with "Home Assistant" carves a clear niche with distinct triggers unlikely to conflict with other skills.

3 / 3

Total

9

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
SharpAI/DeepCamera
Reviewed

Table of Contents

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.