# Recipes ## What this is Recipes are small starting points for common Protege workflows. Use them as prompts to adapt, not as final production instructions. ## 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 ## Linear urgent issue routing ### Use when You want urgent Linear issues routed to the right place. ### Starting prompt > When a new Linear issue is created with urgent priority, summarize the issue and post it to the engineering triage Slack channel. ### Setup to verify * Linear is connected * Slack is connected if the Protege posts to Slack * The Linear team or issue scope is narrow * Tool Access allows only the actions the Protege should take ## 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 ## 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 webhook event * Tool Access matches the allowed response path ## 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 cron 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 ## Next step * [Create a Protege](/create-a-protege.md) * [Integrations overview](/integrations.md) * [Event Feed](/event-feed.md) --- # Agent Instructions: 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: ``` GET https://gitbook.tryprotege.com/create-a-protege/recipes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.