Name: bolt-iot
Rating: 56.8 (1 reviews)
Author: membranedev

bolt-iot

Bolt IoT integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bolt IoT data.

Quality

65%

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/bolt-iot/SKILL.md

Quality

Content

68%Weight 40%Scale 1-5

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

The content is highly actionable with copy-paste-ready commands and a well-validated connection workflow, but it carries some unnecessary background prose and lacks validation guidance around destructive device operations. Trimming the intro and adding pre/post checks for risky actions would address the lowest dimensions.

Suggestions

Cut the background intro about hobbyists/students/professionals; lead directly with what the skill does and the CLI commands.

Add a pre-confirmation and post-verification step for destructive actions (e.g., confirm before `restart-device`, verify device status after) so the run workflow has explicit validation checkpoints.

Consider moving the popular-actions reference table into a separate reference file if the action catalog grows, to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-driven, but the intro ("used by hobbyists, students, and professionals to create connected devices") is background Claude already knows, and a few explanatory passages could be trimmed, fitting the 'mostly efficient but some unnecessary explanation' anchor.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request proxy) with concrete parameterization and a popular-actions table, matching the 'fully executable, covers common cases' anchor.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state-based validation and feedback loops (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), but destructive device actions (Restart Device, Serial/Digital Write) are run via `membrane action run` with no pre-confirmation or post-verification step, which per the rubric caps this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files are present; the single ~150-line file is organized into clear H2 sections with a logical setup-to-advanced flow and content appropriately placed at this length, fitting the 'good structure, minor organization gaps' anchor.	4 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 answers both what and when with an explicit trigger and a distinctive brand niche, but its action verbs are generic and it offers only one narrow trigger phrase without common variations. Tightening the capabilities and broadening the trigger terms would lift the weaker dimensions.

Suggestions

Replace generic verbs with concrete Bolt IoT operations (e.g., "read sensor data, control GPIO pins, check device status, restart devices") to raise specificity.

Broaden the trigger clause with natural variations users actually say, e.g. "Use when the user wants to interact with Bolt IoT devices, sensors, or IoT data".

Keep the distinctive "Bolt IoT" brand trigger but pair it with platform-specific capability terms to further reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Names the domain and three actions ("Manage data, records, and automate workflows"), but the verbs are generic ("manage", "automate") rather than concrete operations, matching the 'names domain and concrete actions but not comprehensive' anchor better than the specific-action anchor above.	3 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Bolt IoT data"), but the trigger is a single narrow phrase rather than the multiple concrete triggers required for a 5.	4 / 5
Trigger Term Quality	Includes the distinctive brand keyword "Bolt IoT" plus "data" and "records", but misses common natural variations a user would say (device, sensors, IoT), fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The "Bolt IoT" brand establishes a clear distinct niche with minimal conflict risk, but the generic action framing ("manage data, records") and single narrow trigger leave minor overlap risk versus the comprehensive distinct triggers of a 5.	4 / 5
	Total	14 / 20 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: membranedev/application-skills
Path: skills/bolt-iot/SKILL.md
Commit: f484c82

Reviewed: 3 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.