mobile-app-testing
tessl i github:secondsky/claude-skills --skill mobile-app-testingMobile 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.
Validation
63%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 10 / 16 Passed | |
Implementation
80%This skill provides excellent, actionable code examples across multiple mobile platforms with efficient token usage. However, it lacks workflow guidance for test infrastructure setup, CI/CD integration, and handling common issues like flaky tests that were mentioned in the skill description. The content would benefit from explicit workflows and references to advanced topics.
Suggestions
Add a workflow section for test infrastructure setup with explicit steps (install dependencies -> configure -> run -> validate results)
Include guidance on handling flaky tests with concrete debugging steps and retry strategies
Add references to separate files for advanced topics: device farm setup, CI/CD integration, and platform-specific troubleshooting
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting information in tables and code examples without unnecessary explanation. It assumes Claude knows what testing pyramids, mocking, and code coverage mean. | 3 / 3 |
Actionability | Provides fully executable code examples for all three platforms (React Native, iOS, Android) that are copy-paste ready. The testing pyramid table gives concrete coverage targets. | 3 / 3 |
Workflow Clarity | While the testing pyramid provides a clear structure and best practices are listed, there's no explicit workflow for setting up test infrastructure, running tests, or handling flaky tests. Missing validation checkpoints for test execution. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections by platform, but for a comprehensive testing skill, advanced topics like device farms, CI/CD integration, and flaky test handling mentioned in the description are missing and could benefit from references to separate detailed files. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
92%This is a strong skill description that clearly articulates specific mobile testing capabilities and provides explicit trigger conditions. The description uses appropriate third-person voice and covers a good range of natural trigger terms. Minor improvement could be made by adding platform-specific terms (iOS, Android) to further distinguish from general testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'unit tests, UI automation, performance testing' and specific concerns like 'test infrastructure, E2E tests, testing standards, device farms, flaky tests, platform-specific test errors'. | 3 / 3 |
Completeness | Clearly answers both what ('Mobile app testing with unit tests, UI automation, performance testing') and when ('Use for test infrastructure, E2E tests, testing standards, or encountering test framework setup, device farms, flaky tests, platform-specific test errors'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'unit tests', 'UI automation', 'E2E tests', 'flaky tests', 'device farms', 'test framework setup' - these are all terms developers naturally use when discussing mobile testing. | 3 / 3 |
Distinctiveness Conflict Risk | While 'mobile app testing' and 'device farms' are distinctive, terms like 'unit tests', 'E2E tests', and 'flaky tests' could overlap with general testing skills not specific to mobile. Could benefit from more explicit mobile platform mentions (iOS, Android). | 2 / 3 |
Total | 11 / 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.