Name: firmalyzer-iotvas-api
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

firmalyzer-iotvas-api

Firmalyzer IoTVAS API integration. Manage Organizations. Use when the user wants to interact with Firmalyzer IoTVAS API data.

Quality

66%

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/firmalyzer-iotvas-api/SKILL.md

Quality

Content

76%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 concrete, copy-paste-ready commands and a well-organized single-file structure. The main gap is the absence of explicit validation checkpoints in the connection/discovery workflow.

Suggestions

Add validation checkpoints to the workflow, e.g. after `membrane connect` confirm a connectionId was returned, and after `membrane action list` confirm the desired action id before running.

Consider extracting the proxy flag reference table into a separate references file to keep SKILL.md a leaner overview once the skill grows.

Dimension	Reasoning	Score
Conciseness	The body is lean and dominated by executable commands and reference tables; the brief opening paragraph and best-practices rationale are justified context for a niche external API rather than concepts Claude already knows.	4 / 5
Actionability	Provides copy-paste-ready commands for every step (install, login, search, connect, action list/run, request) plus a flag reference table and a popular-actions table covering common cases.	5 / 5
Workflow Clarity	A sequence exists across sections (install → login → connect → discover → run) but there are no explicit validation checkpoints (e.g., confirming a connection id was obtained or that an action exists before running it).	3 / 5
Progressive Disclosure	A single well-organized file with clear section headers and no nested/buried references; at ~120 lines with no external bundle files it stays appropriately inline, though the proxy flag table could live in a reference file.	4 / 5
	Total	16 / 20 Passed

Description

57%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 has an explicit trigger clause and a distinct product niche, but it undersells the API's core capabilities and lacks the natural vocabulary a user would actually invoke. Strengthening the action list and trigger synonyms would materially improve it.

Suggestions

Replace 'Manage Organizations' with the API's concrete capabilities (e.g., 'Analyze IoT device firmware for vulnerabilities, detect devices, extract weak keys/certs, run risk analysis') to raise specificity.

Add natural trigger synonyms users would say, e.g. 'Use when the user wants to scan IoT firmware, find device vulnerabilities, or analyze firmware security.'

Make the 'when' clause more concrete by naming the user intents (vulnerability discovery, firmware risk assessment) rather than 'interact with ... data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Firmalyzer IoTVAS API integration') but the only stated action is the minimal/generic 'Manage Organizations', which undersells the firmware-analysis capabilities documented in the body.	2 / 5
Completeness	Both a 'what' and an explicit 'Use when...' clause are present, but the 'when' trigger is generic ('interact with Firmalyzer IoTVAS API data') rather than concrete.	4 / 5
Trigger Term Quality	Includes the product name as a keyword ('interact with Firmalyzer IoTVAS API data') but omits natural synonyms a user would say, such as 'IoT firmware', 'vulnerability scanning', or 'device firmware analysis'.	3 / 5
Distinctiveness Conflict Risk	The specific product name gives a clear niche with minimal conflict risk, though 'Manage Organizations' could overlap with generic org-management skills.	4 / 5
	Total	13 / 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/firmalyzer-iotvas-api/SKILL.md
Commit: f484c82

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