Menu

Individual skill

to-android-probe

Investigate an Android App through mobile-easy-use from a natural-language request by composing probe generation and execution. Use when the user wants to navigate to a page, observe a critical runtime chain, inspect state, verify UI changes, or answer another scoped Android runtime question without managing script or execution details.

skills/to-android-probe/SKILL.md

Read pinned source

Source commit 79d8da76964b67c5857cd700ea30bf12538b52d0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
9
Repository last updated
Sep 17, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# To Android Probe

Turn one natural-language Android runtime question into a generated probe, one controlled execution, and an evidence-backed answer. Keep code generation and execution details hidden unless the user asks for them.

## Workflow

1. Read the complete sibling `../to-android-probe-script/SKILL.md` and follow its generation contract.
2. Read the complete sibling `../to-android-run/SKILL.md` and follow its connection and execution contract.
3. Resolve the requested target, starting scene, allowed interactions, and required chain, state, or UI evidence. Inspect the target App source and existing presets when symbols or navigation steps are unknown; never guess them. Ask only when missing information makes execution unsafe or materially ambiguous.
4. Use `to-android-probe-script` to generate the smallest probe that answers the original question. Use a task-specific directory under the workspace `artifacts/` for Module output unless the user supplies another directory.
5. Use `to-android-run` to execute exactly one generated Inline operation or one Module export. Preserve its single-operation and no-unsafe-retry rules.
6. After execution returns, inspect its result and only the evidence files it returned. Read only the references matching the returned evidence types: [chain](references/chain-evidence.md), [state](references/state-evidence.md), or [UI](references/ui-evidence.md).
7. Relate observed runtime events to original App source, distinguish observed facts from source-based inference, and decide whether the question is answered.
8. If it is not answered, revise and execute another probe only when doing so is safe. Do not automatically retry a failed or timed-out operation that may have mutated App state; first restore or confirm a known starting scene.