Name: saucelabs
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

saucelabs

SauceLabs integration. Manage Users, Organizations, Files, Notes, Activities. Use when the user wants to interact with SauceLabs 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/saucelabs/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, largely executable guide to driving SauceLabs through the Membrane CLI, with a sensible connection-state workflow and feedback loop. Its main weaknesses are an unnecessary introductory explanation of what Sauce Labs is and slightly inconsistent step numbering.

Suggestions

Trim or remove the intro paragraph explaining what Sauce Labs is and the bare "SauceLabs Overview" bullet list, since Claude already knows the product.

Fix the step numbering (there is a "1b" and a "skip to Step 2" but no labeled Step 1 or Step 2) so the connect → ready → act flow is unambiguous.

Consolidate the overlapping "Searching for actions" and "Popular actions" sections to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Sauce Labs is ("Sauce Labs is a cloud-based platform for automated testing...") and the thin "SauceLabs Overview" list restate concepts Claude already knows, while the command sections themselves are reasonably lean.	3 / 5
Actionability	Concrete executable commands are provided throughout (login, connection ensure, action list/run, request with a full flag table), but placeholders like CONNECTION_ID and <actionId> keep it just short of copy-paste-ready.	4 / 5
Workflow Clarity	A clear sequence (install → authenticate → connect → poll for READY → search → run/proxy) with state-based checkpoints and a feedback loop for CLIENT_ACTION_REQUIRED is present, though the "skip to Step 2" / "1b" numbering is inconsistent and no Step 1/Step 2 is actually labeled.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into headed sections with no external bundle files to navigate, though at ~140 lines the inline flag table and overlapping "Searching for actions" / "Popular actions" sections show minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

66%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 clearly identifies the SauceLabs niche and includes an explicit "Use when" trigger, but its action vocabulary is a single generic verb applied to a list of entities and the trigger phrasing lacks natural synonyms. It is solid but could be sharper.

Suggestions

Replace the single generic verb "Manage" with a few distinct concrete actions (e.g. "list, create, update, and delete Users, Organizations, Files, Notes, and Activities").

Expand the trigger clause with natural user phrasings and synonyms, e.g. "Use when the user wants to query or manage SauceLabs users, jobs, assets, or test data."

Dimension	Reasoning	Score
Specificity	The phrase "Manage Users, Organizations, Files, Notes, Activities" names several concrete domain objects but relies on a single generic verb ("Manage") rather than listing distinct concrete actions, matching the anchor that names the domain with limited action variety.	3 / 5
Completeness	Both "what" ("Manage Users, Organizations, Files, Notes, Activities") and an explicit "when" ("Use when the user wants to interact with SauceLabs data") are present, but the trigger clause is somewhat generic and could be more specific.	4 / 5
Trigger Term Quality	"SauceLabs" and "interact with SauceLabs data" provide relevant keywords, but common natural variations or synonyms a user might say are missing, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Naming a specific external product ("SauceLabs integration") with a product-scoped trigger gives it a clear niche and minimal overlap with other skills.	5 / 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/saucelabs/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.