Name: successware21
Rating: 59.2 (1 reviews)
Author: membranedev

successware21

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

Quality

68%

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

Quality

Content

75%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 body is highly actionable with complete, copy-paste CLI commands and a well-sequenced connection workflow, held back only by minor redundancy, a light marketing preamble, and a broken in-page step reference.

Suggestions

Define the missing "Step 2" anchor (or rewrite "skip to Step 2") so the cross-reference in the connection flow resolves.

De-duplicate the `membrane action list --intent=QUERY` command, which appears in Searching for actions, Popular actions, and Best practices.

Trim the opening paragraph to the trade context Claude actually needs, or move the entity hierarchy into a short reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and lean, but the marketing-style opener ("comprehensive business management software designed for HVAC, plumbing, and electrical service contractors") and the `membrane action list --intent=QUERY` command repeated three times are padding that could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases end to end (`npm install -g @membranehq/cli`, `membrane connection ensure`, `membrane action run`, `membrane request`) with a clear flag table and a consistent placeholder convention (CONNECTION_ID, QUERY).	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop; the "skip to Step 2" reference points at a label that does not exist, a minor navigation gap that keeps it below 5.	4 / 5
Progressive Disclosure	The single SKILL.md is well-sectioned (Overview, Working with, Install, Auth, Connecting, Searching, Proxy, Best practices) with no nested references, but all detail lives inline and no external reference files are used to split the larger reference material.	4 / 5
	Total	16 / 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 successfully pairs a clear what/when structure around a branded product, but its action language is generic and its trigger terms lack the synonyms and concrete entities users would naturally mention.

Suggestions

Replace generic verbs with concrete actions, e.g. "create and update customers, work orders, and equipment records; search and run SuccessWare21 actions".

Broaden trigger terms to natural user phrasings such as "SuccessWare21, SW21, service tickets, work orders, dispatch".

Tighten the "when" clause to specific trigger scenarios (e.g. "Use when the user wants to query, create, or update SuccessWare21 records or run a SuccessWare21 workflow").

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the SuccessWare21 domain and a couple of actions, but the verbs ("manage") are generic rather than concrete; not the comprehensive action list of a 4-5, yet more than the single generic verb of a 2.	3 / 5
Completeness	It states both the "what" ("SuccessWare21 integration. Manage data, records, and automate workflows.") and an explicit "when" clause, but the trigger ("interact with SuccessWare21 data") is somewhat generic rather than packing the concrete trigger phrases that define a 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with SuccessWare21 data" surfaces the brand keyword plus "data"/"records", but it lacks common variations or synonyms a user might actually say (e.g. SW21, service tickets, work orders).	3 / 5
Distinctiveness Conflict Risk	The branded "SuccessWare21" noun and "Use when the user wants to interact with SuccessWare21 data" trigger carve a clear niche with low conflict risk; the generic action verbs ("manage data, records") keep it just short of the fully-distinct 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/successware21/SKILL.md
Commit: f484c82

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