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

# Execute Prompts

All of the prompts within Riku.ai can be executed directly within Riku! You can go to either the Community Showcase or Private Prompts and choose what you'd like to run. Click it and it will load up the execution page. You will see the input titles and examples of text to input. Fill in these fields and the final option is to choose how many you would like to create from 1 to 4. 

![](/files/vzEBkpSFaUUIXry7GjeH)

Once you have the outputs, you can choose to use them for your projects, you can choose to edit the prompt in the playground to fit it more to your needs or you can go back to the input fields and tweak them slightly. We want you to have the best experience with AI. 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.riku.ai/rikus-playground/execute-prompts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.