> 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/cortex-xsoar-8-on-prem/8.5/configure-cortex-xsoar/marketplace/content-pack-contributions/create-a-content-pack.md). # Create a content pack Any user can add content that has been created to a content pack. The content pack is submitted and reviewed by Cortex XSOAR to ensure it complies with Cortex XSOAR standards. After approval, the content pack can be used in Marketplace. 1. Select Marketplace → Contributions → **Contribute Content**. 2. In the **Pack Name** field type a meaningful name for the content pack. 3. From the list select the type of content you want, locate the content you want to add and click **Add**. ![market-contribution.png](/files/673a5eZjcozG1yaQ10T4) For more information about how to build a content pack, see the [Dev Hub documentation](http://xsoar.pan.dev/start-contributing). 4. If you want to continue adding content at a later time or to use the **Validate Pack** option, click the save button. 5. (Optional) Click [Validate Pack](/cortex-xsoar-8-on-prem/8.5/configure-cortex-xsoar/marketplace/content-pack-contributions.md) to check for errors. The pack must be saved before you validate. 6. If you have finished and want to send the content pack to a Cortex XSOAR developer for review, click **Save and Contribute** to either contribute or download your contribution. 7. (Optional) In the **Contribute** dialog box, add a description. 8. Select **Save and submit your contribution**, enter your email address and click **Contribute**.

Note

Instead of submitting the contribution, you can also download the content pack and upload it, for example, to GitHub.

9. After you contribute the content pack, you will receive an email with a link to a form you must complete. 1. Fill in additional details, such as pack name, author, and description. 2. Log in to your GitHub account to participate in the review process of the pull request that is automatically opened for your content pack. 3. Sign the [Palo Alto Networks Contributor License Agreement](https://github.com/demisto/content/blob/master/docs/cla.pdf). If you are updating an existing content pack: 10. If you are updating an existing content pack: 1. Select **Update Existing Pack** from the **Select Contribution Mode** menu. 2. Select the pack you want to update from the **Select Existing Pack** menu. 3. Log in to your GitHub account to participate in the review process of the pull request that is automatically opened for the content pack. 4. Sign the [Palo Alto Networks Contributor License Agreement](https://github.com/demisto/content/blob/master/docs/cla.pdf). 5. Given a version number MAJOR.MINOR.REVISION, select **Update Type**. | Type | Description | | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Revision | When you make backwards compatible bug fixes. | | Minor | When you add functionality in a backwards compatible manner. | | Major |

A major revision contains one or more of the following:

| | Documentation | When only documentation files are updated. | 11. After you submit the form, a GitHub branch is created in the [xsoar-contrib content repository fork](https://github.com/xsoar-contrib/content) with the changes from your contribution. 12. You will receive an invitation to join the `xsoar-contrib` organization. Being a member of the organization enables the xsoar-bot to invite you to a GitHub team and grant you write permissions to the created branch. (Each contributor can only modify files in content packs that they contributed). 13. The pull request is created and a reviewer is assigned.

Note

The documentation for new integrations/scripts/playbooks is automatically generated and contains basic information. You need to review the documentation file, README.md, and modify it according to Cortex XSOAR standards. The files to be reviewed are listed at the pull request comment.

14. You can now modify the files changed in the pull request as part of the review process. --- # 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/cortex-xsoar-8-on-prem/8.5/configure-cortex-xsoar/marketplace/content-pack-contributions/create-a-content-pack.md?ask=&goal= ``` `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.