Athena starters for it and engineering

Run a vendor security watch. Ask me which software and vendors we run. Cover the last 7 days: breaches, critical vulnerabilities with CVE numbers, outages, and end-of-life notices, with severity and what we should do. Cite every item. Deliver three files in my company's brand. If I have Word, PowerPoint, or Excel templates in Athena, ask once which to use and build every file from them, keeping their layouts, styles, and formulas. For the brand, use my company's design system if one exists. Otherwise find my company's website (search the web if you are not sure of the domain), run design_system_retriever on it to get the real logo, colors, and fonts, and save the result with create_design_system so every run matches. Use the real logo image; never redraw it or type the company name in its place. The files: (1) a spreadsheet with one row per item (date, vendor, product, issue, CVE, severity, action, source link); (2) a PowerPoint deck with the logo on the title slide, a one-slide summary, a slide per section with a chart wherever there are numbers, and a so-what slide; (3) a Word document with the logo in the header, the full brief, and every source cited. Brand colors and fonts throughout, one idea per slide, no walls of text. Finish with a short summary in chat that links all three. When each run finishes, this one included, email me the three files from Athena: send them to my own email address with the chat summary in the body. If Athena cannot send email in this workspace, say so instead. When you are done, ask me if I want this every Monday at 7am (or every weekday, or monthly instead). Also ask which sections to keep and confirm my IANA time zone (for example America/New_York), and pass it explicitly when creating the schedule. If I choose a schedule, set up a scheduled agent that runs this same brief on it, keeps the spreadsheet asset ID and any template IDs in its instructions, reads the latest dated tab before each run, and reports only what changed since the last run. It says plainly when nothing material changed, and says comparison is unavailable if the prior tab cannot be read. Each run adds a dated tab to the same spreadsheet and makes a new dated deck and document. Whenever I give feedback on a run, in this chat or a later one, update the scheduled agent's instructions (and the template or design system when the feedback is about how the files look) so every later run follows it, then tell me exactly what you changed.

Write an AI news brief for business and IT leaders. Cover the last 7 days: model and product releases from the major providers, enterprise adoption news, regulation, and security issues, and what each means for us. Cite every item. Deliver three files in my company's brand. If I have Word, PowerPoint, or Excel templates in Athena, ask once which to use and build every file from them, keeping their layouts, styles, and formulas. For the brand, use my company's design system if one exists. Otherwise find my company's website (search the web if you are not sure of the domain), run design_system_retriever on it to get the real logo, colors, and fonts, and save the result with create_design_system so every run matches. Use the real logo image; never redraw it or type the company name in its place. The files: (1) a spreadsheet with one row per item (date, company, category, what happened, why it matters, source link); (2) a PowerPoint deck with the logo on the title slide, a one-slide summary, a slide per section with a chart wherever there are numbers, and a so-what slide; (3) a Word document with the logo in the header, the full brief, and every source cited. Brand colors and fonts throughout, one idea per slide, no walls of text. Finish with a short summary in chat that links all three. When each run finishes, this one included, email me the three files from Athena: send them to my own email address with the chat summary in the body. If Athena cannot send email in this workspace, say so instead. When you are done, ask me if I want this every Monday at 7am (or every weekday, or monthly instead). Also ask which sections to keep and confirm my IANA time zone (for example America/New_York), and pass it explicitly when creating the schedule. If I choose a schedule, set up a scheduled agent that runs this same brief on it, keeps the spreadsheet asset ID and any template IDs in its instructions, reads the latest dated tab before each run, and reports only what changed since the last run. It says plainly when nothing material changed, and says comparison is unavailable if the prior tab cannot be read. Each run adds a dated tab to the same spreadsheet and makes a new dated deck and document. Whenever I give feedback on a run, in this chat or a later one, update the scheduled agent's instructions (and the template or design system when the feedback is about how the files look) so every later run follows it, then tell me exactly what you changed.

Track software renewals and waste. Ask me for our license or spend export (a spreadsheet in Athena or an upload). Find renewals in the next 90 days, unused seats, and tools that overlap, and estimate what we could save. Deliver three files in my company's brand. If I have Word, PowerPoint, or Excel templates in Athena, ask once which to use and build every file from them, keeping their layouts, styles, and formulas. For the brand, use my company's design system if one exists. Otherwise find my company's website (search the web if you are not sure of the domain), run design_system_retriever on it to get the real logo, colors, and fonts, and save the result with create_design_system so every run matches. Use the real logo image; never redraw it or type the company name in its place. The files: (1) a spreadsheet with one row per tool (tool, vendor, cost, seats, seats used, renewal date, overlap, saving); (2) a PowerPoint deck with the logo on the title slide, a one-slide summary, a slide per section with a chart wherever there are numbers, and a so-what slide; (3) a Word document with the logo in the header, the full brief, and every source cited. Brand colors and fonts throughout, one idea per slide, no walls of text. Finish with a short summary in chat that links all three. When each run finishes, this one included, email me the three files from Athena: send them to my own email address with the chat summary in the body. If Athena cannot send email in this workspace, say so instead. When you are done, ask me how often I want this: every weekday at 7am, weekly on Mondays at 7am, monthly on the 1st, or not now. Also ask which sections to keep and confirm my IANA time zone (for example America/New_York), and pass it explicitly when creating the schedule. If I choose a schedule, set up a scheduled agent that runs this same brief on it, keeps the spreadsheet asset ID and any template IDs in its instructions, reads the latest dated tab before each run, and reports only what changed since the last run. It says plainly when nothing material changed, and says comparison is unavailable if the prior tab cannot be read. Each run adds a dated tab to the same spreadsheet and makes a new dated deck and document. Whenever I give feedback on a run, in this chat or a later one, update the scheduled agent's instructions (and the template or design system when the feedback is about how the files look) so every later run follows it, then tell me exactly what you changed.

Triage new tickets in our issue tracker. Ask me which project or queue. Group them by type and severity, find duplicates, suggest an owner and a first response for each, and flag anything blocking people today. Deliver three files in my company's brand. If I have Word, PowerPoint, or Excel templates in Athena, ask once which to use and build every file from them, keeping their layouts, styles, and formulas. For the brand, use my company's design system if one exists. Otherwise find my company's website (search the web if you are not sure of the domain), run design_system_retriever on it to get the real logo, colors, and fonts, and save the result with create_design_system so every run matches. Use the real logo image; never redraw it or type the company name in its place. The files: (1) a spreadsheet with one row per ticket (key, title, type, severity, duplicate of, suggested owner, first response); (2) a PowerPoint deck with the logo on the title slide, a one-slide summary, a slide per section with a chart wherever there are numbers, and a so-what slide; (3) a Word document with the logo in the header, the full brief, and every source cited. Brand colors and fonts throughout, one idea per slide, no walls of text. Finish with a short summary in chat that links all three. When each run finishes, this one included, email me the three files from Athena: send them to my own email address with the chat summary in the body. If Athena cannot send email in this workspace, say so instead. When you are done, ask me how often I want this: every weekday at 7am, weekly on Mondays at 7am, monthly on the 1st, or not now. Also ask which sections to keep and confirm my IANA time zone (for example America/New_York), and pass it explicitly when creating the schedule. If I choose a schedule, set up a scheduled agent that runs this same brief on it, keeps the spreadsheet asset ID and any template IDs in its instructions, reads the latest dated tab before each run, and reports only what changed since the last run. It says plainly when nothing material changed, and says comparison is unavailable if the prior tab cannot be read. Each run adds a dated tab to the same spreadsheet and makes a new dated deck and document. Whenever I give feedback on a run, in this chat or a later one, update the scheduled agent's instructions (and the template or design system when the feedback is about how the files look) so every later run follows it, then tell me exactly what you changed.

Summarize the current sprint for stakeholders from our issue tracker. Ask me which board. Show what got done, what slipped and why, what is blocked, and what is next, in plain words. Deliver three files in my company's brand. If I have Word, PowerPoint, or Excel templates in Athena, ask once which to use and build every file from them, keeping their layouts, styles, and formulas. For the brand, use my company's design system if one exists. Otherwise find my company's website (search the web if you are not sure of the domain), run design_system_retriever on it to get the real logo, colors, and fonts, and save the result with create_design_system so every run matches. Use the real logo image; never redraw it or type the company name in its place. The files: (1) a spreadsheet with one row per ticket (key, title, owner, status, slipped, blocker); (2) a PowerPoint deck with the logo on the title slide, a one-slide summary, a slide per section with a chart wherever there are numbers, and a so-what slide; (3) a Word document with the logo in the header, the full brief, and every source cited. Brand colors and fonts throughout, one idea per slide, no walls of text. Finish with a short summary in chat that links all three. When each run finishes, this one included, email me the three files from Athena: send them to my own email address with the chat summary in the body. If Athena cannot send email in this workspace, say so instead. When you are done, ask me if I want this every Monday at 7am (or every weekday, or monthly instead). Also ask which sections to keep and confirm my IANA time zone (for example America/New_York), and pass it explicitly when creating the schedule. If I choose a schedule, set up a scheduled agent that runs this same brief on it, keeps the spreadsheet asset ID and any template IDs in its instructions, reads the latest dated tab before each run, and reports only what changed since the last run. It says plainly when nothing material changed, and says comparison is unavailable if the prior tab cannot be read. Each run adds a dated tab to the same spreadsheet and makes a new dated deck and document. Whenever I give feedback on a run, in this chat or a later one, update the scheduled agent's instructions (and the template or design system when the feedback is about how the files look) so every later run follows it, then tell me exactly what you changed.

Go through our open bugs in [project]. Rank them by severity and how many people they affect, mark likely duplicates, and recommend which to fix this sprint.

Review this pull request: [link]. Check correctness, security, and missing tests, and give comments by file and line, most important first.

Write a system design doc for [feature]: goals and non-goals, architecture, data model, APIs, risks, and a rollout plan, with a diagram.

Write a blameless postmortem from these notes and logs: [attach]. Include the timeline, impact, root cause, what went well, and action items with owners.