domain-iot

Use when building IoT apps. Keywords: IoT, Internet of Things, sensor, MQTT, device, edge computing, telemetry, actuator, smart home, gateway, protocol, 物联网, 传感器, 边缘计算, 智能家居

Quality

63%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/domain-iot/SKILL.md

Quality

Discovery

54%

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

This description relies heavily on a keyword list rather than explaining what the skill actually does. While the trigger terms are comprehensive and include good natural language variations, the lack of specific capabilities ('building IoT apps' is too vague) significantly weakens its utility for skill selection. Claude would know WHEN to consider this skill but not WHAT it can actually do.

Suggestions

Replace 'building IoT apps' with specific actions like 'Connect sensors via MQTT, process telemetry data, configure device gateways, and implement edge computing logic'

Add concrete use cases after 'Use when' such as 'Use when setting up sensor networks, configuring MQTT brokers, processing device telemetry, or building smart home automations'

Dimension	Reasoning	Score
Specificity	The description only says 'building IoT apps' without listing any concrete actions. It lacks specific capabilities like 'connect sensors', 'process telemetry data', or 'configure MQTT brokers'.	1 / 3
Completeness	Has a 'Use when' clause ('Use when building IoT apps') and keywords, but the 'what does this do' portion is extremely weak - it only implies building apps without describing specific capabilities or actions.	2 / 3
Trigger Term Quality	Excellent coverage of natural keywords including 'IoT', 'Internet of Things', 'sensor', 'MQTT', 'smart home', 'edge computing', and even Chinese translations (物联网, 传感器). These are terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	The IoT-specific keywords like 'MQTT', 'telemetry', 'actuator', and 'smart home' help distinguish it, but 'building apps' is generic and could overlap with other development skills. The keyword list helps but doesn't fully compensate.	2 / 3
	Total	8 / 12 Passed

Implementation

72%

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

This is a well-structured domain reference skill that excels at conciseness through effective use of tables and avoids explaining concepts Claude already knows. However, it functions more as a reference card than an actionable guide—while the MQTT example is executable, other critical patterns (OTA, power management, store-and-forward) lack concrete implementation examples.

Suggestions

Add executable code examples for store-and-forward pattern showing local queue persistence and flush logic

Include a concrete OTA update workflow with explicit validation and rollback steps

Add a power management code snippet demonstrating sleep/wake patterns with embassy or similar

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Uses tables extensively to compress information, avoids explaining basic concepts Claude knows, and every section adds domain-specific value without padding.	3 / 3
Actionability	Provides one concrete MQTT code example that is executable, but many sections are reference tables rather than actionable guidance. Missing complete examples for other patterns like store-and-forward, OTA updates, or power management.	2 / 3
Workflow Clarity	The 'Trace Down' section shows conceptual flow but lacks explicit step-by-step workflows with validation checkpoints. For IoT operations involving OTA updates or network recovery, explicit validation steps would be expected.	2 / 3
Progressive Disclosure	Well-organized with clear sections, tables for quick reference, and explicit 'Related Skills' section pointing to one-level-deep references. Content is appropriately structured for a domain overview skill.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: actionbook/rust-skills
Commit: 1f4becd

Reviewed: 19 days 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.