Review support requests, rank urgency by impact and timing, and identify the responsible internal team. Record evidence, next actions, and response deadlines, then prepare customer reply drafts and an escalation summary organized by urgency.
Prioritize support requests, identify owners, route internally, and prepare safe customer drafts
This skill reviews support requests and organizes their urgency, owners, and next actions. It preserves each request’s identifier, checks whether the sender is internal or external, and identifies the responsible team using contact and service ownership information. It assigns one of four urgency levels based on impact and time sensitivity, then records the problem, evidence, affected scope, workaround, and response deadline. It also prepares customer reply drafts and an escalation summary grouped by urgency.
Use it when unanswered requests are accumulating or you need to identify incidents that deserve priority. It also helps assemble handoff information for the responsible department and review customer responses before sending them.
Do not use it for unrelated inbox summaries or when the sender cannot be safely identified. Emotional wording alone does not determine severity. Replies must not include another customer’s information. Actual internal messages require user authorization. External replies remain drafts by default; sending requires explicit permission.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Use when reviewing a support backlog, identifying urgent incidents, assigning internal ownership, or drafting customer responses.
Do not use when the request is merely to summarize an unrelated inbox or when sender identity cannot be established safely.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Turn scattered messages, meeting notes, and documents into sourced action lists and status briefs. The skill reconciles updates, separates facts from tentative inferences, and highlights decisions, dependencies, risks, and unanswered questions.
Create a complete first version of a requested file or other deliverable early, then refine it and check its format, required content, location, and usability before reporting the work as finished.
Find official documentation for a library, framework, or API and apply it to the task at hand. Check the relevant version, distinguish documented facts from assumptions, and verify code changes with a focused test or concrete command.
Extract and verify text, numbers, objects, and sequences from images, documents, and video. Record where each finding appears, check exact labels and values, and build answers whose supporting evidence can be traced back to the input.
Use Codex to manage Odysseus todos, calendars, memory, and documents, and read or draft email. Through its permission-scoped API, the skill also supports reminders and launching, inspecting, or stopping Cookbook model servers.
Use Claude Code to manage Odysseus tasks, email, calendar events, stored facts, and documents through a permission-scoped API. You can also start, inspect logs for, and stop Cookbook model servers using the access granted by your token.