Name: mabl
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mabl

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

Quality

72%

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

Quality

Content

82%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 strong: highly actionable with concrete CLI commands, well-structured sections, and a clear connection-state workflow. Main gaps are inconsistent step numbering and the absence of explicit validation/retry checkpoints for action runs.

Suggestions

Add explicit validation checkpoints and retry loops for action runs and proxy requests, e.g. check the response status/error field and retry or surface clientAction before proceeding.

Fix the step numbering inconsistency ('#### 1b.' appears with no '1a', and 'Step 2' is referenced but never defined) so the workflow is unambiguous.

Move the proxy flag reference table and the full clientAction schema into a separate reference file to keep the overview lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and minimal padding, though a few sentences (e.g. the overview of what Mabl is and the 'fastest way to get a connection' aside) explain context Claude could infer.	4 / 5
Actionability	Commands are concrete, copy-paste ready, and cover the common cases (login, connection ensure/get, action list/run, request proxy) with flags and JSON output shown explicitly.	5 / 5
Workflow Clarity	The connection flow is sequenced with state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling loop, but there are no explicit validation/retry checkpoints for batch or destructive action runs, and step numbering is inconsistent (jumps from '1b' without a '1a'/'Step 2' is referenced but missing).	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files and no nested references, though some reference-style detail (the proxy flag table, full clientAction schema) could live in a separate file.	4 / 5
	Total	17 / 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 is adequate: it names Mabl, lists a few actions, and includes a 'Use when' trigger clause. It is hurt by generic action verbs and missing the natural QA/test vocabulary that users would actually invoke.

Suggestions

Replace generic verbs with concrete Mabl actions, e.g. 'Run and inspect end-to-end tests, view test runs, suites, and plans'.

Add natural trigger keywords users would say, such as 'test runs', 'suites', 'plans', 'QA testing', or 'end-to-end tests'.

Tighten the 'when' clause to reference Mabl-specific scenarios rather than the broad 'interact with Mabl data'.

Dimension	Reasoning	Score
Specificity	Names the Mabl domain and lists concrete actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than specific Mabl operations like running tests or viewing test results.	3 / 5
Completeness	It answers both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Mabl data'), so the 'Use when' clause is present, though the 'when' is broad.	4 / 5
Trigger Term Quality	It mentions 'Mabl data' and 'workflows', but lacks the natural phrases a user would say such as 'test runs', 'suites', 'plans', or 'QA testing' that appear nowhere in the description.	3 / 5
Distinctiveness Conflict Risk	Tied to the specific product 'Mabl', it is mostly distinct from other skills, with only minor overlap risk against generic data-management skills.	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/mabl/SKILL.md
Commit: f484c82

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