android-verify
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
Capture Android device or emulator evidence with adb before claiming a mobile UI fix is done.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- arclabs-studio/ARCKnowledge-Androidtheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- arclabs-studio/ARCKnowledge-Android★ 1same 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 repository11 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- app-store-listing-creatorSkill
- expo-android-performanceSkill
- expo-interactive-designSkill
- flutter-android-performanceSkill
- flutter-interactive-designSkill
- release-checkSkill
- reproduce-firstSkill
- seo-geo-optimizerSkill
- ship-smallSkill
- toris-flutter-play-store-releaseSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
See what is connected: Use the android tool with action: "devices" (or toris android devices).
- Very specific: line 30
No device in device state → tell the operator to start an emulator or plug in a phone.
≈ “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.
Files
Android verify
A mobile UI fix is not done because the web inspector looks right. Capture device evidence, then point at it.
adb is optional. If it is missing, say so and stop — do not invent a
screenshot or a device list.
Procedure
- See what is connected. Use the
androidtool withaction: "devices"(ortoris android devices). Note the serial and state. - Reproduce on device. Launch or navigate to the screen you changed.
- Capture evidence.
action: "screenshot"writes a PNG under~/.toris/android/screenshots/. Cite that path. For crashes or surprising behaviour, also takeaction: "logcat". - Only then claim the fix. The receipt or chat answer must name the artifact path. "Looks good" without a screenshot is a vibe, not evidence.
Stop conditions
adbis not on PATH → report that Android verify is unavailable. The rest of toris still works. Do not pretend you looked at a device.- No device in
devicestate → tell the operator to start an emulator or plug in a phone. Do not keep retrying blindly. - The screenshot does not show the screen you changed → say so, do not crop the claim to match the photo.
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
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.

