CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/maestro-flows

Use when a team uses or wants Maestro YAML flows for mobile or web UI tests that non-engineers can read: .maestro/*.yaml with tapOn, inputText, assertVisible and swipe, for iOS, Android, Flutter, React Native and web, with nested flows and JavaScript hooks.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

88%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.

A well-crafted, highly actionable skill body: complete executable examples at every step, an explicit verify-and-retry feedback loop, and honest anti-patterns and limitations sections. The only notable improvements are trimming a few editorial sentences and moving the command catalog or CI config into a reference file.

DimensionReasoningScore

Conciseness

Efficient throughout: no explanations of what YAML or UI testing is, dense command table, and tight anti-patterns/limitations tables. A few sentences could be trimmed ("Commands map directly to user actions", "this dramatically shortens the authoring loop"), matching the 4 anchor of minor over-explanation rather than the fully lean 5 anchor.

4 / 5

Actionability

Fully executable end-to-end: install commands ("curl -Ls \"https://get.maestro.mobile.dev\" | bash"), complete copy-paste flow YAML with appId and separator, concrete command syntax for all common cases, run commands with env vars ("EMAIL=... PASSWORD=test maestro test .maestro/"), and a complete GitHub Actions workflow for both Android and iOS.

5 / 5

Workflow Clarity

Steps 1-8 are clearly sequenced (install → author → commands → modularity → hooks → run → studio → CI) with explicit validation and a feedback loop: "Verify: maestro test exits non-zero if any command fails. If it does, Maestro writes a screenshot of the failing screen... use it to fix the failing tapOn / assertVisible target, then re-run before moving on". Batch/directory runs do include verification, so no cap applies.

5 / 5

Progressive Disclosure

No bundle files exist; the skill is self-contained with well-organized sections and clearly signaled one-level external references (maestro docs link, sibling skill names). Falls short of 5 because at ~230 lines the full command catalog table and the CI workflow YAML are inlined in SKILL.md where a references/ file could keep the overview leaner.

4 / 5

Total

18

/

20

Passed

Description

87%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.

A strong description with an explicit 'Use when' clause, distinctive tool-specific triggers, and concrete command/file-path detail. The main gap is missing natural synonyms like 'end-to-end' or 'acceptance tests', and the skill's actions are implied through the artifact description rather than stated directly.

DimensionReasoningScore

Specificity

Names concrete specifics like "Maestro YAML flows for mobile or web UI tests", ".maestro/*.yaml with tapOn, inputText, assertVisible and swipe", and "for iOS, Android, Flutter, React Native and web, with nested flows and JavaScript hooks". Falls short of the 5 anchor because it lists artifacts and commands rather than the skill's own actions (author, run, wire up CI), and coverage of what the skill actually does is implied rather than stated.

4 / 5

Completeness

Explicitly answers both: the "Use when a team uses or wants Maestro YAML flows for mobile or web UI tests that non-engineers can read" clause gives concrete trigger conditions, and the colon-elaboration states the what (YAML flow testing with tapOn/inputText/assertVisible/swipe, nested flows, JavaScript hooks). Clearly above the 4 anchor, whose 'when' would be less explicit.

5 / 5

Trigger Term Quality

Good keyword coverage: "Maestro", "YAML flows", "mobile or web UI tests", ".maestro/*.yaml", platform names, and command names. Not the 5 anchor because common natural synonyms such as "end-to-end (e2e) tests", "acceptance tests", or "app testing" are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche: the named tool "Maestro", its ".maestro/*.yaml" file pattern, and Maestro-specific commands (tapOn, inputText, assertVisible) are unambiguous triggers with minimal overlap risk against sibling frameworks (Detox, Appium, XCUITest) referenced in the body.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page