> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/mcp/mozark-mcp-docs/reference/example-prompts.md).

# Example prompts

Ready-to-adapt prompts for common Mozark tasks.

Copy, paste and adapt. The assistant fills in the tool calls.

## Getting oriented

* *"Who am I in Mozark and what's my default project?"*
* *"List the organisations and projects I can access."*
* *"Switch to the Acme org, Checkout project, Android app."*

## Test generation

* *"Generate positive functional test cases for the onboarding flow using the existing knowledge base."*
* *"Upload these four screenshots of the cart screen, then generate negative edge cases for coupon codes."*
* *"Generate automation-type test cases for login — both polarities."*
* *"Save the last five generated cases to the Auth folder."*

## Test case management

* *"Show me TC-27 with all its steps."*
* *"Find test cases about refunds."*
* *"Move every test case tagged 'smoke' into a folder called Smoke."*
* *"Create a requirement 'Users can pay by UPI' and link TC-12 and TC-13 to it."*

## Planning & runs

* *"Suggest a regression plan for release 3.2."*
* *"Create a test run from the Smoke plan and assign it to Priya."*
* *"Mark step 2 of TC-9 in TR-4 as Failed and attach this screenshot."*
* *"Finish TR-4 and lock it."*

## Real-device execution

* *"Run TC-12 on a free Pixel 7 with screenshots and device logs enabled."*
* *"Run TR-4 on a device and record results as you go."*
* *"Export the last run as an Optics YAML script."*

## Appium

* *"Start a session on any iOS 17 device and install `~/builds/app.ipa`."*
* *"Tap the element with text 'Get started', then screenshot."*
* *"Download the HAR file from that session."*

## Housekeeping

* *"Find duplicate test cases in this project."*
* *"Re-index all test cases for search."*
* *"How much of our plan have we used this month?"*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mozark.ai/mcp/mozark-mcp-docs/reference/example-prompts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.