CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/maestro-flows

Authors Maestro YAML flow files (`.maestro/*.yaml`) for mobile + web UI automation: declarative `tapOn`, `inputText`, `assertVisible`, `swipe`, supported targets (iOS, Android, Flutter, React Native, web), nested flow imports, JavaScript hooks for complex conditions. Use when the team has already chosen Maestro, is coming from an existing `.maestro/` directory, or explicitly wants YAML-declarative tests readable by non-engineers without a compile step. For framework selection or authoring tests in XCUITest / Espresso / Detox / Appium / Flutter, use a mobile driver-selection or per-flow mobile test-authoring step instead.

77

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a strong, executable tutorial with clear sequencing and real validation/feedback loops, penalized only on progressive disclosure: everything lives inline in one file with no reference split for the longer sections. Conciseness, actionability, and workflow clarity are all strong.

Suggestions

Move the Step 8 CI integration block (and optionally Step 5 JS hooks / Step 7 Studio) into a `references/ci-integration.md` file referenced one level deep, leaving SKILL.md a leaner overview that points to it.

If the command table in Step 3 grows, extract it to `references/commands.md` so the main flow stays scannable while the full command catalog remains one click away.

Add a short 'Quick start' block at the top (install + run a single flow) so the core loop is visible before the detailed steps, improving top-level navigability.

DimensionReasoningScore

Conciseness

The body is lean: a one-line overview, executable YAML/bash blocks, a command table, and anti-patterns — it assumes Claude's competence and does not pad with what-Maestro-is exposition, so most tokens earn their place.

3 / 3

Actionability

Provides copy-paste-ready install commands, complete flow YAML, a command reference table, modular `runFlow` examples, JS hook snippets, and a full CI workflow — fully executable rather than descriptive.

3 / 3

Workflow Clarity

Steps 1–8 are clearly sequenced with explicit validation/feedback loops — 'maestro test exits non-zero if any command fails... use the screenshot to fix the failing target, then re-run' — matching the checkpoint-with-recovery anchor for both local runs and CI.

3 / 3

Progressive Disclosure

The skill is well-organized into clear sections with no nested-reference problem, but it is a monolithic ~230-line single file with no bundle files: substantial content (CI integration, JS hooks, Studio) is inline rather than split into one-level-deep references, so the 'overview pointing to detailed materials' structure is only partially realized.

2 / 3

Total

11

/

12

Passed

Description

100%

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 concrete, third-person, and tightly scoped: it lists specific commands and platforms, gives explicit positive and negative use triggers, and clearly distinguishes Maestro from neighboring frameworks. It is among the strongest reference examples in the rubric.

DimensionReasoningScore

Specificity

Names multiple concrete actions and artifacts — `tapOn`, `inputText`, `assertVisible`, `swipe`, nested flow imports, JavaScript hooks — plus concrete targets (iOS, Android, Flutter, React Native, web), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (authors Maestro YAML flow files with the listed commands/targets) and when ('Use when the team has already chosen Maestro, is coming from an existing `.maestro/` directory...'), plus an explicit when-not-to-use redirect.

3 / 3

Trigger Term Quality

Covers natural terms a Maestro user would actually say — 'Maestro', '`.maestro/*.yaml`', 'YAML-declarative tests', 'mobile UI automation', platform names — giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

Clear Maestro-YAML niche with distinct triggers, and it actively redirects XCUITest / Espresso / Detox / Appium / Flutter to other skills, making wrong-skill conflicts unlikely.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents