> 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-xsiam-developer-guide/cortex-xsiam-development-guide/playbooks/generic-playbooks.md). # Generic playbooks The Common Playbooks content pack, installed by default, provides support for common tasks that are part of many analyst workflows. These playbooks can support multiple integrations, and can be used independently or as a sub-playbook for your larger use case. You can view a [full list of the playbooks in the Common Playbooks content pack and their descriptions](https://cortex.marketplace.pan.dev/marketplace/details/CommonPlaybooks/) in the **Content** tab of the pack. A few examples of generic playbooks include: * Detonate URL - Generic Detonates URLs through active integrations that support URL detonation. * File Enrichment - File reputation Get file reputation using one or more integrations. * Get File Sample - Generic Retrieves files from endpoints by the file hash or the file path. --- # 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-xsiam-developer-guide/cortex-xsiam-development-guide/playbooks/generic-playbooks.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.