agentleFS
MohamedRamadanSalahMohamedRamadanSalah/claude-qa-toolkit/.claude/skills/mobile-test/SKILL.md

mobile-test

Skill0 starsChanged 17 days agoMITView on GitHub

Test mobile apps (Android/iOS) — drive a real Android device or emulator via adb, install builds, capture screenshots and logs, generate mobile-specific test cases and checklists. Use when the user is testing a mobile app, APK, Android or iOS application.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. leadgenjay/claude-skills★ 22same name
    2. wrsilva/reis-mobile★ 8same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository9 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the tester reports "the app crashed", automatically: pull logcat, find the exception, and produce a ready bug report (use the …

    line 31
  2. Distinctive:

    When generating test cases for mobile, ALWAYS add these mobile-specific categories on top of normal functional cases:

    line 35
  3. Very specific:

    Never wipe a device (adb shell pm clear, factory reset) without explicit confirmation — it deletes app data.

    line 61
  4. Distinctive:

    Only test apps the tester's company owns or has permission to test.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mobile App Tester

Help the tester test mobile applications. Note: this machine is Windows — Android testing works fully; iOS automation needs a Mac, so for iOS focus on test design, checklists, and analyzing logs/screenshots the tester provides.

Mode 1: Hands-on Android testing (adb)

First check the setup: run adb devices. If adb is missing, guide the user to install Android Platform Tools and enable USB debugging on the device (Settings → Developer options).

When the user reports a bug or crash, ALWAYS run the evidence collector FIRST — one command grabs device info, a screenshot, error logs, and parses crash stack traces:

python .claude/skills/mobile-test/scripts/collect_evidence.py --package <app.package.name>

It saves everything to evidence/<n>/ and prints an Environment block ready for the bug report. Then: Read the screenshot.png to see the screen state, read crashes.txt if it found crashes, and write the bug report (bug-report skill format) including the stack trace's first lines translated to plain language.

Useful actions you can do for the tester:

  • Install a build: adb install -r app.apk
  • Screenshot: adb exec-out screencap -p > screen.png (then Read the image to analyze it)
  • Screen recording: adb shell screenrecord /sdcard/test.mp4 (max 3 min), then adb pull
  • Crash logs: adb logcat -d *:E or adb logcat -d | grep -i "FATAL\|<package name>" — always grab logcat right after a crash and translate the stack trace into plain language for the bug report
  • Device info for bug reports: adb shell getprop ro.build.version.release (Android version), ro.product.model (device model)
  • Simulate conditions: airplane mode adb shell cmd connectivity airplane-mode enable, kill app adb shell am force-stop <package>, revoke a permission adb shell pm revoke <package> <permission>, change font scale/display size for accessibility checks
  • Deep links: adb shell am start -a android.intent.action.VIEW -d "<url>"

When the tester reports "the app crashed", automatically: pull logcat, find the exception, and produce a ready bug report (use the bug-report skill format) including device model, OS version, and the stack trace.

Mode 2: Mobile test case design

When generating test cases for mobile, ALWAYS add these mobile-specific categories on top of normal functional cases:

  • Interruptions: incoming call/SMS during a flow, notification tap, app switch and return, screen lock/unlock mid-operation
  • Lifecycle: kill app and reopen (state restored?), background for a long time, low memory kill, update app with old data installed
  • Network: offline mode, switch Wi-Fi ↔ mobile data mid-request, slow/flaky network, request timeout behavior
  • Permissions: deny each permission, revoke while app is running, "don't ask again" state
  • Device variety: small screen, tablet, different OS versions (check the app's minSdk), dark mode, large font size (accessibility), RTL language (Arabic!)
  • Orientation: rotate on every screen, especially during input or loading
  • Battery/performance: battery saver mode, app size, startup time, jank on old devices
  • Platform rules: back button behavior (Android), swipe gestures (iOS), safe areas/notch

Mode 3: Mobile automation

  • Recommend Maestro for a tester starting automation — YAML flows, very simple, works on Android + iOS. Write flows like:
    appId: com.example.app
    ---
    - launchApp
    - tapOn: "Login"
    - inputText: "user@test.com"
  • Recommend Appium when the team needs a full framework integrated with their existing language (Java/Python/JS).
  • Same quality rules as the automate skill: no fixed sleeps, independent tests, meaningful assertions.

Safety

  • Never wipe a device (adb shell pm clear, factory reset) without explicit confirmation — it deletes app data.
  • Only test apps the tester's company owns or has permission to test.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.