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

smartbear

SmartBear integration. Manage data, records, and automate workflows. Use when the user wants to interact with SmartBear 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

67%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 a well-structured, actionable CLI guide with a strong connection-state workflow and feedback loops, though it opens with unnecessary concept explanation and lacks verification steps in the action-running sections. No bundle files are present or needed.

Suggestions

Trim the opening overview paragraph and the "so you can focus on the integration logic rather than auth plumbing" aside — Claude already knows what testing tools and auth plumbing are.

Add a verification/error-handling checkpoint after "Running actions" and "Proxy requests" (e.g., check the `output`/error field and retry or surface `clientAction` on failure).

Provide one fully-resolved worked example with concrete values (a real connection id and action id) to bridge the placeholder gap.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational commands, but the opening paragraph ("SmartBear provides software testing and monitoring tools. Developers, testers, and operations teams use it...") explains what SmartBear is, and phrases like "so you can focus on the integration logic rather than auth plumbing" pad concepts Claude already knows. Fits anchor 3 (mostly efficient with some unnecessary explanation); not 4 because the intro and asides are clearly trimmable.	3 / 5
Actionability	Concrete, executable commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run", proxy flags table). Mostly executable per anchor 4; not 5 because examples rely on placeholders (CONNECTION_ID, <actionId>, QUERY) and lack a single fully-resolved worked example.	4 / 5
Workflow Clarity	The connection setup is a clear sequence with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-action feedback loop. Anchor 4; not 5 because the later "Running actions" and "Proxy requests" sections lack verification/error-handling checkpoints for responses.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, and no external files are needed for this self-contained CLI guide. Anchor 4; not 5 because the "SmartBear Overview" hierarchy is thin and a couple of sections ("Popular actions") are lightly fleshed out.	4 / 5
	Total	15 / 20 Passed

Description

70%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 and is anchored to a distinctive brand trigger, but its action language is generic and omits SmartBear's actual testing/monitoring capabilities. Trigger coverage is good though missing QA-specific synonyms.

Suggestions

Replace generic actions ("Manage data, records, and automate workflows") with SmartBear-specific capabilities such as API testing, UI testing, and performance monitoring that appear in the body.

Expand the "Use when..." trigger to name concrete phrases users would say, e.g. "Use when the user wants to run SmartBear test cases, view test results, or monitor API/UI tests."

Dimension	Reasoning	Score
Specificity	Names the domain (SmartBear) and a couple of actions ("Manage data, records, and automate workflows"), but the actions are generic rather than SmartBear-specific capabilities like API/UI testing or performance monitoring. Fits anchor 3 (domain + 1-2 concrete actions, not comprehensive); not 4 because the actions lack concrete specificity, and not 2 because it does list more than minimal action verbs.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with SmartBear data") are present. Matches anchor 4; not 5 because the "when" clause is generic rather than listing concrete trigger phrases, and not 3 because an explicit trigger clause exists.	4 / 5
Trigger Term Quality	The brand name "SmartBear" is the natural term a user would say and it appears twice ("SmartBear integration", "interact with SmartBear data"). Good keyword coverage but missing common QA-specific variations (testing, test cases, API testing) that users might also say, so not 5.	4 / 5
Distinctiveness Conflict Risk	The "SmartBear" brand trigger gives it a clear niche with minimal conflict risk, but the generic action language ("Manage data, records, and automate workflows") creates minor overlap risk with other data-management skills. Mostly distinct per anchor 4; not 5 because of that generic action breadth.	4 / 5
	Total	15 / 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/smartbear/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.