CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/maestro-flows

Use for any question or task about Maestro, even writing one short flow, or a mobile UI test format that product managers and other non-engineers can read and edit: .maestro/*.yaml with tapOn, inputText, assertVisible and swipe, for iOS, Android, Flutter, React Native and web, with nested flows and JavaScript hooks.

Quality

95%

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

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.

The body is a strong, actionable guide: every step has executable code or commands, the workflow is clearly sequenced with an explicit failure-recovery loop, and the anti-patterns and limitations tables add real value. The only weaknesses are minor: a few trimmable motivational sentences and reference-grade material (command table, CI recipe) inlined in an otherwise well-organized single file.

Suggestions

Trim sales-adjacent asides (e.g., "YAML is more accessible than Swift / Kotlin / JS", "this dramatically shortens the authoring loop") to pure operational guidance to lift conciseness.

Move the full command table (Step 3) into a references/ file (e.g., commands.md) and keep a handful of the most common commands inline with a clearly signaled link, improving progressive disclosure and shrinking the main file.

Consider moving the complete CI workflow YAML to a separate reference file, leaving a minimal inline example plus a one-line pointer.

DimensionReasoningScore

Conciseness

The body is efficient — tables, tight code blocks, and terse prose with no explanation of concepts Claude already knows — but a few motivational asides could be trimmed ("YAML is more accessible than Swift / Kotlin / JS", "this dramatically shortens the authoring loop", "Commands map directly to user actions"). This fits 'efficient; minor instances of over-explanation' rather than the 'every token earns its place' top anchor.

4 / 5

Actionability

Fully executable throughout: the curl install one-liner, a complete copy-paste-ready cart-flow YAML, a concrete command table, env-var interpolation examples, run commands, and a full GitHub Actions workflow for both Android and iOS. Specific examples cover the common cases, matching the top anchor rather than the 'minor gaps' anchor at 4.

5 / 5

Workflow Clarity

Steps 1–8 are clearly sequenced (install → author → commands → modularity → hooks → run → studio → CI) with an explicit validation feedback loop: "maestro test exits non-zero if any command fails... Maestro writes a screenshot of the failing screen - use it to fix the failing tapOn / assertVisible target, then re-run before moving on", plus verification guidance in the CI step. This matches the 'explicit validation steps; feedback loops for error recovery' anchor rather than the 'minor validation gaps' anchor at 4.

5 / 5

Progressive Disclosure

The file is well-sectioned with clear headers and no nested references, but it is a ~225-line monolith: the 16-row command table (Step 3) and the full CI workflow recipe are inline reference material that could live in one-level-deep reference files. This fits 'good structure; most content appropriately placed; minor organization gaps' rather than the top anchor, which expects well-signaled separate reference files, and is clearly above the 'structure present but content that should be separate is inline' anchor at 3.

4 / 5

Total

18

/

20

Passed

Description

100%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 a strong, dense trigger-rich statement: it names the tool, the file format, concrete commands, platforms, and audience, with an explicit 'Use for...' clause. Both 'what' and 'when' are clearly answered with concrete phrases, and it occupies a distinct niche with low conflict risk.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions and artifacts — ".maestro/*.yaml with tapOn, inputText, assertVisible and swipe", "nested flows and JavaScript hooks" — plus five target platforms, giving comprehensive coverage with no meaningful gaps, which matches the top anchor rather than the 'minor gaps' anchor at 4.

5 / 5

Completeness

It explicitly answers 'when' ("Use for any question or task about Maestro, even writing one short flow, or a mobile UI test format that product managers and other non-engineers can read and edit") and 'what' (YAML flow files with named commands for named platforms) with concrete trigger phrases, matching the top anchor; a 4 would require the when-clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

It covers the natural terms a user would say — "any question or task about Maestro", "mobile UI test", "flow", the exact command names (tapOn, inputText, assertVisible, swipe), platform names, and the ".maestro/*.yaml" file pattern — satisfying the 'synonyms and file extensions' comprehensiveness of the top anchor rather than the 'a few natural terms missing' anchor at 4.

5 / 5

Distinctiveness Conflict Risk

"Maestro", the command vocabulary, and ".maestro/*.yaml" form a clear niche with distinct triggers and minimal conflict risk against adjacent skills like Detox or Appium, matching the top anchor.

5 / 5

Total

20

/

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