CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/mobile-app-testing/skills/mobile-app-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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, well-organized body with executable per-platform code examples and useful best-practice/anti-pattern lists. Main weaknesses are the absence of an explicit multi-step testing workflow with validation checkpoints, and missing run/setup details that would make the examples fully actionable end to end.

Suggestions

Add a short ordered workflow (e.g., 1. write unit tests for business logic, 2. add integration/E2E for critical flows, 3. run suite, 4. triage flaky tests and rerun) to give workflow_clarity explicit checkpoints and a feedback loop.

Include the commands to actually run each framework's tests (e.g., `npx jest`, `npx detox test`, `xcodebuild test`, `./gradlew connectedAndroidTest`) so the examples are executable end to end.

Mention how test IDs are wired up (Detox `testID`, iOS accessibility identifiers, Android `viewTag`) since all three examples rely on element IDs but none show how to set them.

DimensionReasoningScore

Conciseness

The body is lean with zero padding: a one-line purpose, a compact pyramid table, code examples, and terse best-practices/avoid lists. Every section adds information Claude does not already have, matching the 'every token earns its place' anchor.

5 / 5

Actionability

The Jest, Detox, XCTest, and Espresso examples are concrete, syntactically complete, and copy-paste ready. Not a 5 because key execution details are missing — no test-runner commands, Detox configuration, or guidance on wiring test IDs (`by.id`, accessibility identifiers).

4 / 5

Workflow Clarity

The pyramid table and 'Test business logic first' imply an ordering, but there is no explicit multi-step process for testing a feature, and no validation or feedback checkpoints (e.g., run suite -> triage flaky tests -> rerun) — matching the 'sequence present but checkpoints missing' anchor.

3 / 5

Progressive Disclosure

Well-organized sections with clear headers and appropriately inline examples for a single-file skill. Not a 5 because the ~83-line body includes full per-platform example suites that could be split into one-level-deep reference files (e.g., ios-testing.md, android-testing.md) to keep SKILL.md a leaner overview.

4 / 5

Total

16

/

20

Passed

Description

75%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 solid description that clearly states the mobile testing domain, lists several concrete testing capabilities, and provides an explicit 'Use for...' trigger clause with natural keywords. It falls just short of the top anchors due to minor coverage gaps, topic-noun phrasing instead of action verbs, and a few broad terms that overlap with general testing skills.

DimensionReasoningScore

Specificity

Names the mobile testing domain plus several concrete testing activities ("unit tests, UI automation, performance testing"), matching the 'several specific actions; minor gaps' anchor. Not a 5 because coverage has minor gaps and actions are topic nouns rather than concrete verbs like the 5-anchor example.

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... or encountering test framework setup..."). Not a 5 because the 'what' is a terse noun-phrase list rather than the comprehensive concrete action coverage of the 5 anchor.

4 / 5

Trigger Term Quality

Includes natural phrases users would actually say ("E2E tests", "flaky tests", "device farms", "platform-specific test errors"), giving good keyword coverage. Not a 5 because common variations and synonyms (e.g., "test suite", "coverage", specific framework names like Detox or Appium) are absent from the trigger list.

4 / 5

Distinctiveness Conflict Risk

Mobile-specific triggers ("device farms", "platform-specific test errors", iOS/Android testing terms) form a clear niche with minimal conflict risk. Not a 5 because generic terms like "test infrastructure" and "testing standards" could overlap with general or web testing skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.