Name: assetsonar
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

assetsonar

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/assetsonar/SKILL.md

Quality

Content

61%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 strongly actionable, built around concrete Membrane CLI commands and a well-instrumented connection state machine. Its weaknesses are mild verbosity, a thin/redundant "Popular actions" section, and the absence of verification steps for the potentially destructive action-run and proxy operations.

Suggestions

Add a verification/checkpoint step after running actions and proxy requests (e.g. inspect the `output` field, confirm status codes) so destructive or batch operations have a feedback loop.

Trim the introductory paragraph about who uses AssetSonar and de-duplicate the "Searching for actions" and "Popular actions" sections, ideally by listing a few concrete popular actions by name.

Fix the "skip to Step 2" reference by labeling the target section (e.g. "## Step 2 — Search for actions") and resolving the orphan "1b" heading.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening paragraph over-explains what AssetSonar is and who uses it, and "Searching for actions" / "Popular actions" redundantly repeat the same discovery command.	3 / 5
Actionability	It provides many concrete, copy-pasteable bash commands with clearly marked placeholders plus a flag table, but "Popular actions" only repeats the discovery command instead of listing actual actions and "Running actions" lacks a fully worked example.	4 / 5
Workflow Clarity	The connection workflow has real state-based checkpoints and a poll/re-poll feedback loop, but the core action-execution and proxy steps (which include destructive POST/PUT/DELETE) lack verification steps, and "skip to Step 2" points to an unlabeled section, triggering the destructive/batch cap at 3.	3 / 5
Progressive Disclosure	It is a single, well-sectioned file with no bundle files and no need for external references, appropriate for a CLI integration skill, but it exceeds 50 lines and has minor organization gaps (a thin "Popular actions" section and a broken "Step 2" cross-reference).	4 / 5
	Total	14 / 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 "Use when..." clause and a distinctive product-name trigger, placing it solidly above average. Its main weakness is generic, buzzword-tinged action language ("manage data, records, automate workflows") rather than concrete capabilities.

Suggestions

Replace generic verbs with concrete AssetSonar actions, e.g. "Create and update assets, manage stock and software licenses, raise purchase orders and service contracts, run asset audits."

Expand the "Use when" clause with concrete trigger phrases users would actually say, e.g. "Use when the user wants to track assets, manage stock or software licenses, create purchase orders, or audit AssetSonar records."

Drop the buzzword phrase "automate workflows" in favor of a specific capability it refers to.

Dimension	Reasoning	Score
Specificity	Names the domain and two action areas ("Manage data, records, and automate workflows"), but the verbs are generic and "automate workflows" is buzzword fluff, matching the anchor that lists 1-2 actions without being comprehensive.	3 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with AssetSonar data"), but the when clause is a single generic trigger rather than multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	The distinctive natural trigger is the product name "AssetSonar" plus "data" and "records", but the supporting terms are generic and missing common synonyms or variations.	3 / 5
Distinctiveness Conflict Risk	The named product "AssetSonar" gives a clear niche with minimal conflict risk, though the templated generic phrasing overlaps with sibling Membrane product skills that use identical wording.	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/assetsonar/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.