Write scripts with Claude, Grok or ChatGPT

By the end of this page you will know how to teach AppsMobs to Claude, Grok, ChatGPT or Gemini, ask it for a script, and check that script before running it. ⏱ 5 minutes.

The AppsMobs pack

The pack is one text file that explains AppsMobs to an AI: how to use the app, the rules of a script (no import, wait() in seconds, always a timeout…) and every function with its exact signature. It is generated from the app's code, so it matches the functions that really exist.

• Download the pack (English)
• Télécharger le pack (français)
• Claude Skill (.zip)

The pack is also inside the app: in the Playground, on an empty script, the Write it with Claude or Grok card copies it to the clipboard, no Internet needed.

1. 1

   Give the pack to your AI

   • Grok, ChatGPT, Gemini: paste the pack as your first message, or attach the .md file.
   • Claude, once and for all: download the Skill (.zip), then in Claude open Settings, the Skills section, and upload it. Claude then uses it on its own as soon as you talk about AppsMobs.
   • Claude Project: add the .md file to the project knowledge.

   The AI now knows the app, the script rules and every function.

2. 2

   Describe your script

   Write what you want in plain sentences, with the details that matter:

   Tap play.png, then wait up to 20 seconds for the text "Welcome". Write a message in the output in both cases. Repeat 10 times.

   Which image, which text, how many times, what to do on failure: the more precise you are, the better the script.

3. 3

   Paste it into the Playground

   Copy the code block of the answer, paste it into an empty script in the Playground, and save. Put the images it mentions (play.png…) in the script folder.

4. 4

   Read, then test on a device

   Choose the device in Run on, click Run and read the Output. If something fails, paste the error to the AI: "Here is the error, what is wrong?".

What the AI does badly

An AI writes plausible code, not verified code. Even with the pack, expect:

• Invented functions (click_image, sleep_random…): they cause a NameError. Remind it: "use only the functions in the pack". The reference is the same list.
• Imaginary images: it writes button.png but does not know what your button looks like. You must provide the capture.
• Badly dosed waits: too short, or without testing the result. Re-read with the good habits.
• Random coordinates: a tap(540, 960) only makes sense for your screen.