agentleFS
szmidtpiotrszmidtpiotr/ClaudeCode-Tools/Skills/mobile-game-test/SKILL.md

mobile-game-test

Skill0 starsChanged 5 months agoNo licenceView on GitHub

Drive the Moto G32 test phone via Appium (running on the AI-GM lab VM at 192.168.1.19) to play AI-GM as a real player through Chrome on Android. Use this skill whenever the user asks to test, verify, reproduce, or smoke-check AI-GM behavior "on the phone", "on mobile", "in the real player UI", "on a real device", "through scrcpy", or "end-to-end as a player" — even if they don't explicitly say "Appium". Also trigger when the user wants to play a session interactively while they watch via scrcpy, walk through a player flow on Android, or verify a mobile-specific regression. Do NOT use for backend-only checks, API smoke tests, admin-panel work, or anything where the deliverable is a code change rather than a played-out session. Bundles a Python helper that handles the hard parts: chromedriver auto-download, JS-based input that bypasses overlay intercepts, dice-prompt detection, dice rolling, and screenshot capture.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are 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.

  • 4

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

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.