> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mobileboost.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting started

> Use MobileBoost with Claude Code, Cursor, Codex, and other AI coding agents

The MobileBoost agent skill lets you create, run, and debug mobile tests directly from your AI coding agent. It works with any agent that supports custom skills or tool definitions.

## How it works

The skill generates native **XCUITest** and **Espresso** code by default for fast, deterministic test execution. It also has built-in knowledge of the MobileBoost SDK (GptDriver) and uses it as a fallback where native automation alone isn't enough, for example when dealing with non-accessible elements like web views, third-party components, or graphical elements. This gives you the performance of native frameworks with the reliability of AI-powered automation where it matters.

## Installation

Add the MobileBoost skill to your agent by providing the following URL:

```
https://www.mobileboost.io/mobileboost-skill.md
```

<Tabs>
  <Tab title="Claude Code">
    Add the skill URL to your Claude Code configuration:

    ```bash theme={null}
    claude skill add https://www.mobileboost.io/mobileboost-skill.md
    ```
  </Tab>

  <Tab title="Cursor">
    In Cursor, go to **Settings > AI > Custom Skills** and paste the skill URL:

    ```
    https://www.mobileboost.io/mobileboost-skill.md
    ```
  </Tab>

  <Tab title="Codex">
    Add the skill URL to your Codex agent configuration:

    ```bash theme={null}
    codex skill add https://www.mobileboost.io/mobileboost-skill.md
    ```
  </Tab>
</Tabs>

## Recommended models

For best results, use a model with medium reasoning capacity:

| Provider  | Recommended model |
| --------- | ----------------- |
| Anthropic | Claude Sonnet 4.6 |
| OpenAI    | GPT 5.4           |

## Usage

Invoke the skill using the `/gptdriver-ui-tests` slash command in your agent:

```
/gptdriver-ui-tests <your test instruction>
```

### Prompting tips

The skill works best when you provide structured input:

* **Step-by-step test definitions**: break your test into individual steps describing each action and expected outcome
* **Screenshots**: attach screenshots of the flow you want to test so the agent can understand the UI context

<Note>
  The more specific your test definition, the better the generated test. Instead of "test the login flow", provide individual steps like "tap the email field, enter [test@example.com](mailto:test@example.com), tap the password field, enter a password, tap the login button, verify the home screen appears".
</Note>