automating-mobile-app-testing
This skill enables automated testing of mobile applications on iOS and Android platforms using frameworks like Appium, Detox, XCUITest, and Espresso. It generates end-to-end tests, sets up page object models, and handles platform-specific elements. Use this skill when the user requests mobile app testing, test automation for iOS or Android, or needs assistance with setting up device farms and simulators. The skill is triggered by terms like "mobile testing", "appium", "detox", "xcuitest", "espresso", "android test", "ios test".
80
50%
Does it follow best practices?
Impact
100%
1.02xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/testing/mobile-app-tester/skills/mobile-app-tester/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly defines its scope, lists concrete actions, provides explicit trigger guidance, and occupies a distinct niche. It uses proper third-person voice throughout and includes both broad and specific trigger terms. The description is well-structured and comprehensive without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'generates end-to-end tests', 'sets up page object models', 'handles platform-specific elements', and mentions specific frameworks (Appium, Detox, XCUITest, Espresso). Also mentions device farms and simulators. | 3 / 3 |
Completeness | Clearly answers both 'what' (automated testing of mobile apps, generates e2e tests, sets up page object models, handles platform-specific elements) and 'when' (explicit 'Use this skill when...' clause with specific trigger terms listed). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'mobile testing', 'appium', 'detox', 'xcuitest', 'espresso', 'android test', 'ios test', plus broader terms like 'mobile app testing', 'test automation for iOS or Android'. These are terms users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on mobile app testing with named frameworks (Appium, Detox, XCUITest, Espresso) and platform-specific concerns (iOS, Android, device farms, simulators). Unlikely to conflict with general testing or web testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a marketing description rather than actionable technical guidance. It contains no executable code, no concrete commands, no configuration examples, and no real workflows despite covering a complex multi-framework, multi-platform domain. Claude would gain almost nothing from this skill that it doesn't already know.
Suggestions
Add concrete, executable code examples for at least 2 frameworks (e.g., a complete Appium test in Python and a Detox test in JavaScript) with actual selectors, assertions, and configuration files.
Provide specific setup commands and configuration snippets (e.g., `appium --platform-name iOS --device-name 'iPhone 15'`, `detox.config.js` contents) instead of abstract descriptions.
Remove the 'How It Works', 'When to Use', 'Best Practices', and 'Integration' sections — they explain things Claude already knows — and replace them with framework-specific reference files linked from the main skill.
Add a concrete workflow with validation steps, e.g., 'Run `detox build` → verify build succeeds → run `detox test` → check for failures → retry flaky tests with `--retries 2`'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains things Claude already knows (what page object models are, what simulators are, when to use the skill). The 'How It Works', 'When to Use', and 'Integration' sections add no actionable value and waste tokens restating the skill description. | 1 / 3 |
Actionability | There is zero executable code, no concrete commands, no configuration snippets, no actual test examples. The 'Examples' section describes what the skill 'will do' in abstract terms rather than showing any actual Appium/Detox/XCUITest/Espresso code or configuration. | 1 / 3 |
Workflow Clarity | No concrete workflow steps are provided. The numbered lists describe abstract intentions ('Generate Appium tests', 'Configure an iOS simulator') without any actual commands, validation checkpoints, or error recovery guidance. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block with no references to supporting files, no linked resources for framework-specific details, and no bundle files to support the breadth of topics covered (four different frameworks, device farm setup, page object models). | 1 / 3 |
Total | 4 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
13d35b8
- 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.