mobile-app-testing

Mobile app testing with unit tests, UI automation, performance testing. Use for test infrastructure, E2E tests, testing standards, or encountering test framework setup, device farms, flaky tests, platform-specific test errors.

Quality

85%

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

Quality

Content

87%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 concise, highly actionable reference with copy-paste code across all three mobile platforms and clean single-file organization. The main weakness is the absence of an explicit, sequenced test-authoring workflow with validation/feedback checkpoints (e.g., for flaky tests or CI runs).

Suggestions

Add a short sequenced workflow for authoring and stabilizing tests with explicit checkpoints, e.g. write test -> run locally -> if flaky, isolate with retry/quarantine -> re-run on device farm -> confirm green before merge.

Include a feedback loop for flaky tests specifically (detect -> quarantine -> root-cause -> re-enable) since 'flaky tests' is a core trigger and batch/device-farm runs benefit from validation.

Add a brief verification step showing how to run the suites (e.g., `jest`, `detox test`, `xcodebuild test`, `./gradlew connectedAndroidTest`) so the executable guidance extends from writing to running and confirming pass/fail.

Dimension	Reasoning	Score
Conciseness	The body is lean: a pyramid table, three copy-paste code blocks, and short Best Practices/Avoid bullets, with no padding or explanation of concepts Claude already knows; matches the 'lean and efficient, every token earns its place' anchor and not 4 because there is no over-explanation to trim.	5 / 5
Actionability	Provides fully executable, copy-paste-ready examples across Jest, Detox, XCTest, and Espresso covering the common login-flow case; matches the top anchor and not 4 because the examples are complete rather than having minor gaps.	5 / 5
Workflow Clarity	Content is a reference catalog of example snippets plus a flat Best Practices list rather than a sequenced workflow, and there are no validation/feedback checkpoints (e.g., run suite -> if flaky -> retry/fix); matches the 'sequence present but checkpoints missing' anchor, not 4 because no explicit checkpoints exist and not 2 because priorities and structure are present.	3 / 5
Progressive Disclosure	Single self-contained file (~83 lines) with well-organized, clearly signaled sections (Testing Pyramid, per-platform sections, Best Practices, Avoid) and no bundle files to navigate; per the simple-skill guideline this reaches the top anchor, not 4 because organization is clean and appropriately placed.	5 / 5
	Total	18 / 20 Passed

Description

83%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 that explicitly states both capabilities and concrete use-when triggers with natural phrasing. It is mobile-specific with low conflict risk, with only minor gaps in action specificity and keyword synonym coverage.

Dimension	Reasoning	Score
Specificity	Names the mobile-testing domain plus several concrete actions ("unit tests, UI automation, performance testing"), with only minor gaps in coverage, matching the 'lists several specific actions' anchor; not 5 because coverage isn't comprehensive (e.g., no mocking or coverage tooling) and not 3 because more than 1-2 actions are named.	4 / 5
Completeness	Explicitly answers both what ("Mobile app testing with unit tests, UI automation, performance testing") and when ("Use for test infrastructure, E2E tests... device farms, flaky tests..."), with concrete trigger phrases matching the top anchor; not 4 because both clauses are explicit and concrete.	5 / 5
Trigger Term Quality	Strong natural triggers a user would say ("E2E tests", "test framework setup", "device farms", "flaky tests", "platform-specific test errors") with good synonym coverage; not 5 because some natural variations/framework names are absent and not 3 because keyword coverage is clearly good.	4 / 5
Distinctiveness Conflict Risk	Mobile-specific niche with distinct triggers (device farms, platform-specific test errors) is mostly distinct; not 5 because the when-clause doesn't strongly foreground mobileness and could overlap a generic code-testing skill, and not 3 because the triggers are clearly scoped.	4 / 5
	Total	17 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/mobile-app-testing/skills/mobile-app-testing/SKILL.md
Commit: 84802a4

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