automating-mobile-app-testing
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill automating-mobile-app-testingThis 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".
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 16 Passed | |
Implementation
7%This skill content reads like marketing copy rather than actionable instructions. It describes what the skill does conceptually but provides zero executable code, no actual test examples, no configuration snippets, and no specific commands. Claude cannot use this to actually generate mobile tests because it lacks concrete implementation details for any of the mentioned frameworks.
Suggestions
Add executable code examples for at least one framework (e.g., complete Appium test file with imports, setup, and assertions)
Include actual configuration snippets (e.g., appium.config.js, detox config, capabilities JSON) that Claude can adapt
Replace the abstract 'Examples' section with concrete input/output pairs showing actual test code generation
Add framework-specific reference files (APPIUM.md, DETOX.md, etc.) with detailed setup and API patterns for each
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what page object models are, what device farms are). It describes what the skill does rather than providing actionable instructions, wasting tokens on meta-explanation. | 1 / 3 |
Actionability | No executable code, commands, or concrete examples are provided. The 'Examples' section describes what 'the skill will do' abstractly rather than showing actual test code, configuration files, or specific commands Claude should execute. | 1 / 3 |
Workflow Clarity | The 'How It Works' section lists abstract concepts rather than actionable steps. There are no validation checkpoints, no specific commands to run, and no feedback loops for error handling in test setup or execution. | 1 / 3 |
Progressive Disclosure | The content is organized into logical sections with clear headers, but it's a monolithic document with no references to detailed materials. For a skill covering 4+ frameworks across 2 platforms, framework-specific guides should be referenced. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
100%This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, comprehensive trigger terms, explicit usage guidance, and clear differentiation from other testing-related skills. The description uses proper third-person voice and balances detail with conciseness.
| 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). | 3 / 3 |
Completeness | Clearly answers both what (automated testing, generates tests, sets up page objects) AND when with explicit 'Use this skill when...' clause and specific trigger terms listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'mobile testing', 'appium', 'detox', 'xcuitest', 'espresso', 'android test', 'ios test', plus mentions 'device farms' and 'simulators'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on mobile app testing with distinct platform identifiers (iOS, Android) and framework-specific triggers that wouldn't overlap with general testing or web testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
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.