Agent skill

Android Testing

by Moustachauve in Moustachauve/WLED-Android

Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests.

Apache-2.0Auto-check passedTesting & QA

Install Android Testing

skills CLI

$ npx skills add Moustachauve/WLED-Android --skill android-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Moustachauve/WLED-Android android-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Moustachauve/WLED-Android.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/android-testing .claude/skills/android-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "android-testing" agent skill from https://github.com/Moustachauve/WLED-Android/tree/main/.github/skills/android-testing into .claude/skills/android-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-testing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Moustachauve/WLED-Android/tree/main/.github/skills/android-testing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Moustachauve/WLED-Android --skill android-testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Moustachauve/WLED-Android android-testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Moustachauve/WLED-Android.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/android-testing .agents/skills/android-testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "android-testing" agent skill from https://github.com/Moustachauve/WLED-Android/tree/main/.github/skills/android-testing into .agents/skills/android-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-testing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Moustachauve/WLED-Android --skill android-testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Moustachauve/WLED-Android android-testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Moustachauve/WLED-Android.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/android-testing .cursor/skills/android-testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "android-testing" agent skill from https://github.com/Moustachauve/WLED-Android/tree/main/.github/skills/android-testing into .cursor/skills/android-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-testing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Moustachauve/WLED-Android.git --path .github/skills/android-testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Moustachauve/WLED-Android --skill android-testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Moustachauve/WLED-Android android-testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Moustachauve/WLED-Android.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/android-testing .gemini/skills/android-testing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "android-testing" agent skill from https://github.com/Moustachauve/WLED-Android/tree/main/.github/skills/android-testing into .gemini/skills/android-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-testing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Moustachauve/WLED-Android android-testing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Moustachauve/WLED-Android --skill android-testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Moustachauve/WLED-Android.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/android-testing .github/skills/android-testing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "android-testing" agent skill from https://github.com/Moustachauve/WLED-Android/tree/main/.github/skills/android-testing into .github/skills/android-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-testing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Moustachauve/WLED-Android --skill android-testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Moustachauve/WLED-Android android-testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Moustachauve/WLED-Android.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/android-testing .opencode/skills/android-testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "android-testing" agent skill from https://github.com/Moustachauve/WLED-Android/tree/main/.github/skills/android-testing into .opencode/skills/android-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "android-testing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: android-testing
GitHub stars: 169
Used in: 3 other repos
Token cost: ~731 tokens
SKILL.md length: 141 words
Files: 1
Skills in repo: 17
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests.

Works in 3 steps: Unit Tests: Fast, isolate logic… → Integration Tests: Test interactions… → UI/Screenshot Tests: Verify UI…
Tasks that involve Test strategy
SKILL.md covers Testing Pyramid, Dependencies…, Screenshot Testing with… and Hilt Testing, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Android Testing is an agent skill from Moustachauve/WLED-Android. Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests.

Its SKILL.md is about 730 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test strategy. It works with Android. The repository describes itself as: Native Android application for WLED. The licence is Apache-2.0.

When your agent uses it

Tasks that involve Test strategy

Example prompts

“/android-testing”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Unit Tests: Fast, isolate logic (ViewModels, Repositories).
Integration Tests: Test interactions (Room DAOs, Retrofit vs MockWebServer).
UI/Screenshot Tests: Verify UI correctness (Compose).

What it can do on your machine

Read from SKILL.md and the folder at commit 7e164a8. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are kotlin and toml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Android Testing loads about 731 tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 141 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~26
When it runs · the whole SKILL.md, loaded when a task matches: ~731

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Moustachauve/WLED-Android at commit 7e164a8, republished under its Apache-2.0 licence (© Moustachauve). 141 words, ~731 tokens.

Download SKILL.mdSave it as .claude/skills/android-testing/SKILL.md (or your agent's skills folder).

name: android-testing
description: Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests.

Android Testing Strategies

This skill provides expert guidance on testing modern Android applications, inspired by "Now in Android". It covers Unit Tests, Hilt Integration Tests, and Screenshot Testing.

Testing Pyramid

Unit Tests: Fast, isolate logic (ViewModels, Repositories).
Integration Tests: Test interactions (Room DAOs, Retrofit vs MockWebServer).
UI/Screenshot Tests: Verify UI correctness (Compose).

Dependencies (`libs.versions.toml`)

Ensure you have the right testing dependencies.

toml

[libraries]
junit4 = { module = "junit:junit", version = "4.13.2" }
kotlinx-coroutines-test = { group = "org.jetbrains.kotlinx", name = "kotlinx-coroutines-test", version.ref = "kotlinxCoroutines" }
androidx-test-ext-junit = { group = "androidx.test.ext", name = "junit", version = "1.1.5" }
espresso-core = { group = "androidx.test.espresso", name = "espresso-core", version = "3.5.1" }
compose-ui-test = { group = "androidx.compose.ui", name = "ui-test-junit4" }
hilt-android-testing = { group = "com.google.dagger", name = "hilt-android-testing", version.ref = "hilt" }
roborazzi = { group = "io.github.takahirom.roborazzi", name = "roborazzi", version.ref = "roborazzi" }

Screenshot Testing with Roborazzi

Screenshot tests ensure your UI doesn't regress visually. NiA uses Roborazzi because it runs on the JVM (fast) without needing an emulator.

Setup

Add the plugin to libs.versions.toml:

toml

[plugins]
roborazzi = { id = "io.github.takahirom.roborazzi", version.ref = "roborazzi" }

Apply it in your module's build.gradle.kts:
kotlin
```
plugins {
    alias(libs.plugins.roborazzi)
}
```

Writing a Screenshot Test

kotlin

@RunWith(AndroidJUnit4::class)
@GraphicsMode(GraphicsMode.Mode.NATIVE)
@Config(sdk = [33], qualifiers = RobolectricDeviceQualifiers.Pixel5)
class MyScreenScreenshotTest {

    @get:Rule
    val composeTestRule = createAndroidComposeRule<ComponentActivity>()

    @Test
    fun captureMyScreen() {
        composeTestRule.setContent {
            MyTheme {
                MyScreen()
            }
        }

        composeTestRule.onRoot()
            .captureRoboImage()
    }
}

Hilt Testing

Use HiltAndroidRule to inject dependencies in tests.

kotlin

@HiltAndroidTest
class MyDaoTest {

    @get:Rule
    var hiltRule = HiltAndroidRule(this)

    @Inject
    lateinit var database: MyDatabase
    private lateinit var dao: MyDao

    @Before
    fun init() {
        hiltRule.inject()
        dao = database.myDao()
    }
    
    // ... tests
}

Running Tests

Unit: ./gradlew test
Screenshots: ./gradlew recordRoborazziDebug (to record) / ./gradlew verifyRoborazziDebug (to verify)

Files

Just SKILL.md in .github/skills/android-testing of Moustachauve/WLED-Android.

Open the folder on GitHubat commit 7e164a8

Used in 3 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in Moustachauve/WLED-Android, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Android Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Android Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Android Testing this skillMoustachauve/WLED-Android	169	3 repos	~731	Automated safety check: Pass	Apache-2.0	today
QAdutradotdev/quokka	108	—	~1k	Automated safety check: Pass	MIT	2 mo ago
Testing Setuparindamxd/camerax-android	132	4 repos	~2.3k	Automated safety check: Pass	Apache-2.0	5 days ago
Understanding The Testing Pyramidskydoves/android-testing-skills	333	—	~4.4k	Automated safety check: Pass	Apache-2.0	4 mo ago
Applying Testing Strategiesskydoves/android-testing-skills	333	—	~5.4k	Automated safety check: Pass	Apache-2.0	4 mo ago
Diagnoseywwynm/EverythingDone	144	18 repos	~1.8k	Automated safety check: Pass	GPL-3.0	23 days ago

Similar skills

QA
dutradotdev/quokka
Run quokka's real-device E2E layer (QA strategy layer 5): drive the real qk binary against connected iPhone/Android devices through tmux, apply deterministic verifiers, and write a report.
108 GitHub stars~1k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
Testing Setup
arindamxd/camerax-android
Analyze and create a testing strategy for native Android apps - install testing libraries, set up test infrastructure, create harnesses for unit tests, UI tests, screenshot tests, and end-to-end…
132 GitHub starsUsed in 4 repos~2.3k tokens
Testing & QAAuto-check passed
Understanding The Testing Pyramid
skydoves/android-testing-skills
A skill your agent uses to size an Android test suite using Google's small / medium / big scope vocabulary and the qualitative pyramid.
333 GitHub stars~4.4k tokensUpdated 4 mo ago
Testing & QAAuto-check passed
Applying Testing Strategies
skydoves/android-testing-skills
A skill your agent uses to apply Android-team testing strategies — determinism, hermetic execution, Given-When-Then / Arrange-Act-Assert structure, naming conventions, and Hilt-based dependency…
333 GitHub stars~5.4k tokensUpdated 4 mo ago
Testing & QAAuto-check passed
Diagnose
ywwynm/EverythingDone
Disciplined diagnosis loop for hard bugs and performance regressions.
144 GitHub starsUsed in 18 repos~1.8k tokens
Testing & QAAuto-check passed
SoloPi AI Control
alipay/SoloPi
Drives Android devices through SoloPi's typed command line to record, replay and verify app behavior, with device pools and signed on-device decision models.
6.3k GitHub stars~3.6k tokensUpdated 1 mo ago
Testing & QAAuto-check passed

Questions about Android Testing

What does Android Testing do?

Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests. Android Testing is an agent skill from Moustachauve/WLED-Android. Comprehensive testing strategy involving Unit, Integration, Hilt, and Screenshot tests.

When should I use Android Testing?

Android Testing fits situations like: tasks that involve Test strategy.

How do I install Android Testing in Claude Code?

Run `npx skills add Moustachauve/WLED-Android --skill android-testing -a claude-code`. Or copy the skill folder (.github/skills/android-testing in Moustachauve/WLED-Android) into .claude/skills/android-testing in your project. Claude Code loads it when a task matches its description.

How do I install Android Testing in Codex?

Run `npx skills add Moustachauve/WLED-Android --skill android-testing -a codex`. Or copy the skill folder (.github/skills/android-testing in Moustachauve/WLED-Android) into .agents/skills/android-testing in your project. Codex loads it when a task matches its description.

Can I use Android Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Moustachauve/WLED-Android --skill android-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/android-testing, .gemini/skills/android-testing, .github/skills/android-testing and .opencode/skills/android-testing in your project.

What does Android Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Android Testing is instructions for the agent only.

Does Android Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Android Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Android Testing use?

Android Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Android Testing use?

About 731 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Android Testing?

Skills that share tags, products or a category with Android Testing: QA (dutradotdev/quokka, 108 stars), Testing Setup (arindamxd/camerax-android, 132 stars), Understanding The Testing Pyramid (skydoves/android-testing-skills, 333 stars) and Applying Testing Strategies (skydoves/android-testing-skills, 333 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Android Testing?

Moustachauve (a GitHub user) maintains it in Moustachauve/WLED-Android, which has 169 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: Moustachauve/WLED-Android on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Android Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Android Testing Strategies

Testing Pyramid

Dependencies (libs.versions.toml)

Screenshot Testing with Roborazzi

Setup

Writing a Screenshot Test

Hilt Testing

Running Tests

Files

Used in 3 other repositories

Compare with similar skills

Similar skills

More from Moustachauve/WLED-Android

Related

Questions about Android Testing

Dependencies (`libs.versions.toml`)