New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Android Interactive Verification

by DodoraApp in DodoraApp/DodoStream

Session-scoped Android and Android TV fixture, APK, interaction, evidence, and Maestro procedure through the agent-device MCP server.

GPL-3.0Auto-check passedMobile

Install Android Interactive Verification

skills CLI
$ npx skills add DodoraApp/DodoStream --skill android-interactive-verification -a claude-code

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

GitHub CLI
$ gh skill install DodoraApp/DodoStream android-interactive-verification --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/DodoraApp/DodoStream.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/android-interactive-verification .claude/skills/android-interactive-verification && 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/

Facts

Skill name
android-interactive-verification
GitHub stars
243
Token cost
~1.1k tokens
SKILL.md length
618 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
GPL-3.0

At a glance

Session-scoped Android and Android TV fixture, APK, interaction, evidence, and Maestro procedure through the agent-device MCP server.

  • Works in 7 steps: Start the fixture add-on for this… → Build the release APK artifact: pnpm… → Through the MCP tools: list or boot the… → …
  • Tasks that involve Mobile testing and debugging
  • SKILL.md covers Permission and ownership gate, Required inputs, Session sequence and Evidence and Maestro promotion, plus 1 more section
  • Calls pnpm

What it does

Android Interactive Verification is an agent skill from DodoraApp/DodoStream. Session-scoped Android and Android TV fixture, APK, interaction, evidence, and Maestro procedure through the agent-device MCP server.

Its SKILL.md is about 1.1k 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 Mobile, covering Mobile testing and debugging. It works with Android, Model Context Protocol, pnpm and Expo. The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Mobile testing and debugging

Example prompts

  • “/android-interactive-verification”

Workflow steps

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

  1. Start the fixture add-on for this worktree (pnpm e2e:addon) and probe its /manifest.json.
  2. Build the release APK artifact: pnpm e2e:android:build -- --profile . The build applies APP_VARIANT=dev, EXPO_PUBLIC_E2E=1, the profile…
  3. Through the MCP tools: list or boot the profile-matching device and bind the worktree's MCP session to it.
  4. Through the MCP tools: disable animations, set the profile orientation, install the artifact, and launch app.dodora.dodostream.dev. Clear…
  5. Execute the recorded sequence through MCP interactions (tv_remote for DPAD_* and BACK, press, type, swipe). Capture the resulting…
  6. On failure, return to the same slice's DEBUG loop: repeat the exact sequence, state one causal hypothesis, change one causal area, and…
  7. Release the MCP session with close when no nearby slice needs it, and stop the fixture add-on process.

What it can do on your machine

Read from SKILL.md and the folder at commit 1ef9461. 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

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    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 Interactive Verification loads about 1.1k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 618 words of instructions outside code blocks.

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

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 DodoraApp/DodoStream at commit 1ef9461, republished under its GPL-3.0 licence (© DodoraApp). 618 words, ~1,143 tokens.

Download SKILL.mdSave it as .claude/skills/android-interactive-verification/SKILL.md (or your agent's skills folder).
name
android-interactive-verification
description
Session-scoped Android and Android TV fixture, APK, interaction, evidence, and Maestro procedure through the agent-device MCP server.

Android interactive verification

Use this skill only when the slice's expectation crosses a native Android/Android TV boundary: focus routing, D-pad semantics, native players, lifecycle or system UI, real list recycling, Android-only behavior, rendered geometry, or a stable Maestro regression. Pure parsing, state, hook, transformation, and mockable API work stays on the lower verification ladder.

Permission and ownership gate

Before acquiring or driving a device, confirm that the task explicitly requires device evidence or that the user authorized it. Stop before device acquisition when neither is true. If no agent-device session is active or the selected target is occupied by another agent, ask the user what to do before acquiring, booting, or reusing a target. Never start Metro, use Expo web, call the agent-device CLI directly, or use raw adb.

All device interaction goes through the repository's agent-device MCP server (.omp/mcp.json): keep exactly one MCP session per worktree and bind every operation to it. Keep the session for nearby repairs; release it with close after the last related L4/L5 slice, including failure paths.

Required inputs

Record these before starting:

  • The slice's exact expectation and RED interaction, including the expected initial and final state.
  • phone, tablet, or tv profile; dev app id app.dodora.dodostream.dev; and the required orientation.
  • The release APK path recorded by pnpm e2e:android:build in artifacts/e2e/<profile>/artifact.json.
  • The seeded fixture manifest URL. The fixture's GET /manifest.json must identify com.dodostream.e2e-fixture before install or launch; do not invent a second health endpoint.
  • The affected existing Maestro flow, if a stable regression path already exists.

Session sequence

  1. Start the fixture add-on for this worktree (pnpm e2e:addon) and probe its /manifest.json.
  2. Build the release APK artifact: pnpm e2e:android:build -- --profile <phone|tablet|tv>. The build applies APP_VARIANT=dev, EXPO_PUBLIC_E2E=1, the profile orientation, and EXPO_TV=1 for TV. Never substitute a Metro bundle.
  3. Through the MCP tools: list or boot the profile-matching device and bind the worktree's MCP session to it.
  4. Through the MCP tools: disable animations, set the profile orientation, install the artifact, and launch app.dodora.dodostream.dev. Clear only the app state when the slice needs a clean start, then capture the initial screenshot, hierarchy snapshot, and app logs before interacting.
  5. Execute the recorded sequence through MCP interactions (tv_remote for DPAD_* and BACK, press, type, swipe). Capture the resulting screenshot, hierarchy, and focused-component or app logs at each meaningful state.
  6. On failure, return to the same slice's DEBUG loop: repeat the exact sequence, state one causal hypothesis, change one causal area, and retest on the same session.
  7. Release the MCP session with close when no nearby slice needs it, and stop the fixture add-on process.
Show full SKILL.md (188 more words)Show less

Captures belong beneath the current worktree's ignored artifacts/ directory. A local emulator reaches the fixture through http://10.0.2.2:<port>/manifest.json; record the exact URL the session used. Never assume a host address works from a physical device.

Evidence and Maestro promotion

The final slice record must state initial state → key/action → observed state and identify which screenshot, hierarchy, and log artifacts support it. A screenshot alone does not prove focus; name the visual focus indicator plus hierarchy or focused-component evidence. Do not overwrite committed snapshots during exploration.

Promote the sequence to a targeted Maestro flow only when L4 establishes a stable, user-important regression with reliable selectors and reviewed screenshots. Run the flow through the MCP server (test with the flow file and session env such as ADDON_MANIFEST_URL, PROFILE, E2E_ORIENTATION); inspect every screenshot and baseline change before staging. Do not use Maestro as the first debugger for an unclear focus graph, a positional workaround, or a one-off exploratory trace.

Exit criteria

The skill exits only when the slice has concrete interaction evidence, a targeted Maestro result when promotion is warranted, and no live agent-device MCP session or fixture add-on process is left running.

© DodoraApp, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/android-interactive-verification of DodoraApp/DodoStream.

Open the folder on GitHubat commit 1ef9461

Compare with similar skills

Android Interactive Verification 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 Interactive Verification compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Android Interactive Verification this skillDodoraApp/DodoStream243—~1.1kAutomated safety check: PassGPL-3.0
Screenmapaleqsio/screenmap239—~7.2kAutomated safety check: PassMIT
Magicnet Device DebuggingLIghtJUNction/MagicNet185—~2.9kAutomated safety check: NotesMIT
Phone Harnessmilind-soni/OpenMausBot4.1k—~364Automated safety check: PassApache-2.0
Scrcpy GotchasJuanCF/scrcpy-mcp112—~5.8kAutomated safety check: PassMIT
Generate Appclaw Flowappclawhq/AppClaw116—~3.4kAutomated safety check: NotesApache-2.0

Similar skills

  • Screenmap

    aleqsio/screenmap

    Generate a visual navigation map of an Expo / React Native or NativeScript app.

    239 GitHub stars~7.2k tokensUpdated 2 days ago
    MobileAuto-check passed

  • Magicnet Device Debugging

    LIghtJUNction/MagicNet

    Debug and verify MagicNet on a real Android root device. An agent skill from LIghtJUNction/MagicNet.

    185 GitHub stars~2.9k tokensUpdated today
    MobileAuto-check: notes

  • Phone Harness

    milind-soni/OpenMausBot

    Control, inspect, test, or automate a physical Android phone connected to OpenMausBot over authorized USB debugging.

    4.1k GitHub stars~364 tokensUpdated today
    MobileAuto-check passed

  • Scrcpy Gotchas

    JuanCF/scrcpy-mcp

    A skill your agent uses when interacting with Android devices via scrcpy-mcp tools (tap, swipe, inputtext, keyevent, uidump, uifindelement, appstart, etc.).

    112 GitHub stars~5.8k tokensUpdated 14 days ago
    MobileAuto-check passed

  • Generate Appclaw Flow

    appclawhq/AppClaw

    Generate YAML flow files for AppClaw mobile automation. An agent skill from appclawhq/AppClaw.

    116 GitHub stars~3.4k tokensUpdated 1 mo ago
    MobileAuto-check: notes

  • Spock Adb

    WahdanZ/SpockAdb

    Debug Android apps on a connected device or emulator through the Spock ADB MCP server (tools named android).

    114 GitHub stars~3.3k tokensUpdated yesterday
    MobileAuto-check passed

More from DodoraApp/DodoStream

  • Agent Verification

    DodoraApp/DodoStream

    Select and run concise deterministic DodoStream verification checks.

    243 GitHub stars~802 tokensUpdated 16 days ago
    Auto-check passed

  • Bug Reproduction

    DodoraApp/DodoStream

    Reproduce a reported bug on Android/Android TV and capture evidence.

    243 GitHub stars~495 tokensUpdated 16 days ago
    Auto-check passed

  • Issue Triage

    DodoraApp/DodoStream

    Rank open GitHub issues and propose the next work. An agent skill from DodoraApp/DodoStream.

    243 GitHub stars~473 tokensUpdated 16 days ago
    Auto-check passed

  • Slice Development

    DodoraApp/DodoStream

    Behavior-first planning, verification, debugging, review, and checkpointing for non-trivial DodoStream changes.

    243 GitHub stars~1.9k tokensUpdated 16 days ago
    Auto-check passed

  • Feature Delivery

    DodoraApp/DodoStream

    Deliver a feature end to end from user-visible goal to PR-ready branch.

    243 GitHub stars~354 tokensUpdated 16 days ago
    Auto-check passed

  • PR Handoff

    DodoraApp/DodoStream

    Prepare the branch, title, and draft PR body for substantive finished work.

    243 GitHub stars~250 tokensUpdated 16 days ago
    Auto-check passed

Works with

Categories

Questions about Android Interactive Verification

What does Android Interactive Verification do?

Session-scoped Android and Android TV fixture, APK, interaction, evidence, and Maestro procedure through the agent-device MCP server. Android Interactive Verification is an agent skill from DodoraApp/DodoStream. Session-scoped Android and Android TV fixture, APK, interaction, evidence, and Maestro procedure through the agent-device MCP server.

When should I use Android Interactive Verification?

Android Interactive Verification fits situations like: tasks that involve Mobile testing and debugging.

How do I install Android Interactive Verification in Claude Code?

Run `npx skills add DodoraApp/DodoStream --skill android-interactive-verification -a claude-code`. Or copy the skill folder (.agents/skills/android-interactive-verification in DodoraApp/DodoStream) into .claude/skills/android-interactive-verification in your project. Claude Code loads it when a task matches its description.

How do I install Android Interactive Verification in Codex?

Run `npx skills add DodoraApp/DodoStream --skill android-interactive-verification -a codex`. Or copy the skill folder (.agents/skills/android-interactive-verification in DodoraApp/DodoStream) into .agents/skills/android-interactive-verification in your project. Codex loads it when a task matches its description.

Can I use Android Interactive Verification 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 DodoraApp/DodoStream --skill android-interactive-verification -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-interactive-verification, .gemini/skills/android-interactive-verification, .github/skills/android-interactive-verification and .opencode/skills/android-interactive-verification in your project.

What does Android Interactive Verification need to run?

Going by SKILL.md and its folder, Android Interactive Verification needs the command-line tools its instructions call (pnpm).

Does Android Interactive Verification 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 Interactive Verification 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 Interactive Verification use?

Android Interactive Verification is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Android Interactive Verification use?

About 1.1k tokens (SKILL.md is roughly 4.6k 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 Interactive Verification?

Skills that share tags, products or a category with Android Interactive Verification: Screenmap (aleqsio/screenmap, 239 stars), Magicnet Device Debugging (LIghtJUNction/MagicNet, 185 stars), Phone Harness (milind-soni/OpenMausBot, 4.1k stars) and Scrcpy Gotchas (JuanCF/scrcpy-mcp, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Android Interactive Verification?

DodoraApp (a GitHub organization) maintains it in DodoraApp/DodoStream, which has 243 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 20, 2026.

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