> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/create-a-protege/recipes.md). # Recipes ## What this is Recipes are small starting points for common Hookshot™ Protege workflows. Use them as prompts to adapt, not as final production instructions. ## When to use it * When you want to create a Protege but are not sure where to start * When you need a working example to adapt for your own workflow * When you want to see what a good Builder prompt looks like ## What you need first * A Hookshot workspace * At least one connected integration relevant to the recipe * Permission to create Proteges in your workspace ## Steps ### 1. Slack triage summary #### Use when You want Hookshot to notice important Slack activity and summarize it for a team. #### Starting prompt > When a message in the support triage Slack channel looks urgent, summarize the issue, identify the customer impact, and post a short update to the support leads channel. #### Setup to verify * Slack is connected * The monitored channel is the intended channel * The destination channel is correct * Event Feed shows the message event * Audit shows the posted summary ### 2. GitHub pull request follow-up #### Use when You want a Protege to react to GitHub pull request activity. #### Starting prompt > When a pull request is opened in the repository, check whether it needs release-note attention and post a short reminder if it does. #### Setup to verify * GitHub is connected * The repo scope is correct * Trigger Access points to the intended pull request event * Audit shows any resulting message or update ### 3. Asana task comment response #### Use when You want Hookshot to watch Asana work and respond when a task comment needs attention. #### Starting prompt > When a new comment appears on an Asana task in the customer onboarding project, decide whether it needs follow-up and post a concise response or task update. #### Setup to verify * Asana is connected * The project or portfolio scope is correct * Trigger Access is ready or waiting for the first trigger event * Tool Access matches the allowed response path ### 4. Scheduled weekly summary #### Use when You want a recurring update without waiting for an external event. #### Starting prompt > Every Monday morning, summarize open high-priority work for the team and post a short status update to the weekly planning channel. #### Setup to verify * The schedule has the right time and timezone * The Protege has access to the tools it needs for the summary * The destination is narrow and correct * Audit shows the scheduled run after it fires ## How to verify You adapted a recipe correctly when: * The Protege has a clear trigger that matches your real workflow * The tools are scoped to the smallest practical boundary * Event Feed shows the expected event * Audit shows the expected run and outcome ## Common failures * Copying a recipe prompt without adapting the channel, project, or team names to your workspace * Using a recipe as a production Protege without testing with a safe event first * Choosing a recipe that spans too many integrations for a first Protege ## Next step * [Create a Protege](/create-a-protege.md) * [Integrations overview](/integrations.md) * [Event Feed](/event-feed.md) --- # 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.tryprotege.com/create-a-protege/recipes.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.