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

# Submission Guidelines

> Follow these guidelines to make sure your Plays meet our quality standards before publishing.

## Why guidelines matter

* To keep the Marketplace clean, useful, and professional, every published Play should follow these standards.
* High-quality submissions = more visibility, more adoption, and a better experience for the community.

***

## Required fields

When publishing a Play, make sure you include:

* **Clear title** → short, descriptive, and easy to search.
* **Description** → what the Play does, who it’s for, and key benefits.
* **Tags** → relevant keywords to improve discoverability.
* **Images** → professional, relevant screenshots or graphics that clearly reflect the workflow.
* **Publisher info** → your name, your company, and the publish timestamp (automatically attached).

***

## Image standards

Images should:

* Be **directly related** to the workflow or topic.
* Use a **consistent and professional style** across Plays.
* Be clean and easy to interpret (no clutter or irrelevant visuals).
* Give a quick **visual understanding** of what the Play does.

<Tip>
  Good examples of images include:

  * A screenshot of your workflow in the Canvas.
  * An example output to show what users can expect.
  * A simple visual overview that highlights what the Play does.
</Tip>

***

## Best practices

To maximize adoption of your Play:

* Use **clear, outcome-focused tags** (e.g., `ICP filtering`, `Persona filtering`).
* Write descriptions like you’re explaining to a first-time user.
* Keep titles concise — avoid internal or overly technical jargon.
* If possible, enable **retain run data** so others can see example inputs/outputs.

***

<Note>
  Want to know why publishing is worth it?\
  Check out the [Why should you publish?](./publishing-a-play#why-should-you-publish%3F-coming-soon-🚀) section in the publishing guide.
</Note>