domain-iot
Use when building IoT apps. Keywords: IoT, Internet of Things, sensor, MQTT, device, edge computing, telemetry, actuator, smart home, gateway, protocol, 物联网, 传感器, 边缘计算, 智能家居
70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 has strong trigger term coverage with relevant IoT keywords in multiple languages, but critically lacks specificity about what the skill actually does. The 'what' portion is essentially empty - 'building IoT apps' tells Claude nothing about the skill's actual capabilities, making it difficult to know if this skill can help with a specific IoT task.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configure MQTT brokers, process sensor telemetry, design device communication protocols, implement edge computing pipelines'
Expand the 'Use when' clause to include specific scenarios, e.g., 'Use when connecting sensors to cloud platforms, setting up device-to-device communication, or processing real-time telemetry data'
| 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 but the 'what' is extremely weak - only 'building IoT apps'. The description tells when to use it but fails to explain what specific capabilities the skill provides. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural keywords users would say: 'IoT', 'sensor', 'MQTT', 'smart home', 'edge computing', 'telemetry', plus Chinese equivalents. These are terms users would naturally use when seeking IoT help. | 3 / 3 |
Distinctiveness Conflict Risk | The IoT domain keywords provide some distinctiveness, but 'building IoT apps' is broad enough to potentially overlap with embedded systems, networking, or hardware skills. More specific capabilities would reduce conflict risk. | 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 constraints document that efficiently communicates IoT-specific considerations through tables and concise rules. Its strength is in providing a mental model and quick reference for IoT development patterns. However, it leans more toward reference material than actionable skill guidance, with only one executable code example and missing step-by-step workflows for complex operations like OTA updates.
Suggestions
Add executable code examples for store-and-forward pattern and power management (sleep/wake cycles) to match the actionability of the MQTT example
Include a step-by-step workflow with validation checkpoints for OTA update implementation, given its critical nature and rollback requirements
Add a concrete example showing local buffering with persistence for offline-first design, including retry with backoff logic
| 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 executable examples for power management, OTA updates, and store-and-forward patterns mentioned. | 2 / 3 |
Workflow Clarity | The MQTT example shows error handling with retry, but lacks explicit validation checkpoints. The 'Trace Down' section shows conceptual flow but not step-by-step workflows for critical operations like OTA updates or offline-first implementation. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, tables for quick reference, and explicit cross-references to related skills (domain-embedded, m07-concurrency, etc.). Content is appropriately structured as an overview pointing to detailed materials. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
- 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.