> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/demisto-sdk-development-guide/demisto-sdk-guide/demisto-sdk-commands/prepare-content.md).

# prepare-content

The `prepare-content` command prepares content to upload to Cortex XSOAR or Cortex XSIAM. If the content item is a pack, `prepare-content` creates the pack .zip file. If the content item is an integration/script/rule, `prepare-content` creates the unified YAML file.

{% hint style="info" %}

### Note

The `prepare-content` command replaces the `unify` command.
{% endhint %}

<details>

<summary>Arguments</summary>

| Argument                        | Description                                                                                                                                             |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `-i`, `--input`                 | The path to the directory of a content pack or a content item where the files reside.                                                                   |
| `-o`, `--output`                | The path to the directory into which to write the result.                                                                                               |
| `-f`, `--force`                 | Forcefully overwrites the preexisting file if one exists.                                                                                               |
| `-c`, `--custom`                | Adds a custom label to the `name`/`display`/`id` of the unified YAML. Only applies to integrations/scripts.                                             |
| `-a`, `--all`                   | Runs `prepare-content` on all content packs. If no output path is given, it dumps the result in the current working path.                               |
| `-g`, `--graph`                 | Whether to use the content graph.                                                                                                                       |
| `--skip-update`                 | Whether to skip updating the content graph (used only when graph is `true`).                                                                            |
| `-ini`, `--ignore-native-image` | Whether to ignore the addition of the `nativeimage` key to the YAML of a script/integration.                                                            |
| `-mp`, `--marketplace`          | The Marketplace the content items are created for, which determines the text used specific to that Marketplace. Default is the **`XSOAR`** Marketplace. |

</details>

<details>

<summary>Examples</summary>

* `demisto-sdk prepare-content -i Integrations/MyInt -o Integrations`

  Takes the integration components in the `Integrations/MyInt` directory and unifies them to a single YAML file that is created in the `Integrations` directory.
* `demisto-sdk prepare-content -i Scripts/MyScr -o Scripts`

  Takes the script components in the `Scripts/MyScr` directory and unifies them to a single YAML file that is created in the `Scripts` directory.
* `demisto-sdk prepare-content -u Integrations/MyInt -c Test`

  Appends to the unified YAML `name`/`script`/`id` a label `- Test` that prevents conflicts with the uploaded unified YAML and the original integration/script on the server.

  origin yml: `{name: integration}` --> unified yml: `{name: integration - Test}`
* `demisto-sdk prepare-content -i Packs/RBVM/GenericModules/genericmodule-RBVM.json`

  Takes the `GenericModule` input file `genericmodule-RBVM.json`, unifies it with its dashboards, and saves the unified file in the same directory as the input file in the `Packs/RBVM/GenericModules` directory.
* `demisto-sdk prepare-content -i Packs/RBVM/GenericModules/genericmodule-RBVM.json -o Packs/RBVM/`

  Takes the GenericModule input file `genericmodule-RBVM.json`, unifies it with its dashboards, and saves the unified file in the given output directory `Packs/RBVM`.
* `demisto-sdk prepare-content -i Packs/SIEMPack/ParsingRule/MyParsingRule -o Packs/SIEMPack/ParsingRule`

  Takes the parsing rules components (YAML, XIF and JSON) from the `ParsingRule/MyParsingRule` directory and unifies them into a single YAML file that is created in the `ParsingRule` directory.

</details>


---

# 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://cortex-docs.paloaltonetworks.com/demisto-sdk-development-guide/demisto-sdk-guide/demisto-sdk-commands/prepare-content.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.