CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/espresso-suite

Use whenever an Android app needs UI tests in Google's Espresso: onView with perform and check, automatic synchronization instead of sleeps, IdlingResource for app async work, ./gradlew connectedAndroidTest and JUnit XML results.

Quality

90%

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

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.

A highly actionable, well-structured skill with copy-paste-ready code for every step and a valuable anti-patterns table. It is only slightly held back by quotable doc padding, pinned versions, the absence of an explicit run-results validation loop, and a couple of sections that could be split into reference files.

Suggestions

Trim the opening blockquote and the quoted doc sentences in the Intents section to their operative facts to tighten conciseness.

Add a short validation step after Step 6 (e.g., check the JUnit XML for failures and re-run only failing tests with --tests filters) to close the workflow feedback loop.

Consider moving the Espresso-Intents deep-dive and the GitHub Actions CI config into separate reference files to keep SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

The body is efficient and code-dense, but contains minor trimmable padding: the opening marketing quote ("concise, beautiful, and reliable"), several quoted doc sentences in the Intents section, and pinned dependency version numbers, which the guidelines flag as time-sensitive content outside a deprecated section.

4 / 5

Actionability

Fully executable throughout: complete gradle dependencies, full Kotlin test classes, a working IdlingResource implementation, a matcher/action cheat sheet, run commands, and a CI yaml — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced (dependencies → author tests → IdlingResource → matchers → RecyclerView → intents → run/CI) with an anti-patterns table for recovery, but there is no explicit validation checkpoint such as interpreting JUnit XML failures before iterating, keeping it below the top anchor.

4 / 5

Progressive Disclosure

Good single-file structure with well-labeled numbered steps and a clearly signaled References section; however, the ~60-line Espresso-Intents deep-dive and the CI configuration could arguably live in separate reference files, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

92%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 trigger clause and concrete, comprehensive capability statements. The only gap is missing a few natural synonym phrases (e.g., "instrumented tests", "UI automation") that users might say.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "onView with perform and check", "automatic synchronization instead of sleeps", "IdlingResource for app async work", "./gradlew connectedAndroidTest and JUnit XML results" — covering authoring, synchronization, execution, and result reporting comprehensively for the Espresso domain.

5 / 5

Completeness

It explicitly answers both questions: "Use whenever an Android app needs UI tests in Google's Espresso" gives a concrete when-clause, and the remainder concretely enumerates what the skill does.

5 / 5

Trigger Term Quality

Natural terms users would say are present ("Android app", "UI tests", "Espresso", "IdlingResource", "connectedAndroidTest"), but common variations like "instrumented tests", "UI automation", or "flaky tests" are missing, so coverage falls short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — first-party Espresso UI testing for pure-Android apps — with distinct triggers that would not fire for cross-platform (Appium) or iOS (XCUITest) skills.

5 / 5

Total

19

/

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