Guide · Agent skill
How to use the Set Up Post-Mortem agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Set Up Post-Mortem skill (recipe-post-mortem-setup) is a short, ready-made recipe that lets an AI agent set up the paperwork after an incident in Google Workspace: a post-mortem document, a review meeting and a Chat notice. It is written for engineering or SRE teams that already use Google Workspace and the gws command-line tool. After this guide you will know what the skill does, how to install it, how to ask for it in plain language, and what to change before running it.
Set Up Post-Mortemgoogleworkspace/cli · Apache-2.0 Download the skill Quick start
- 1Download and unzip the skill. Download the ZIP from this page and unzip it so you have a folder containing SKILL.md.
- 2Place the folder. Put the folder in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder. Alternatively, upload it in the Claude apps under Settings → Capabilities → Skills.
- 3Install gws and the related skills. Install the gws command-line tool, authenticate it with your Google account, and add the gws-docs, gws-calendar and gws-chat skills.
- 4Edit the hardcoded values. Change the meeting date and times, the attendee address and the Chat space ID so they match your team, not the example values.
- 5Ask for the post-mortem setup. Describe the incident in plain language and ask the agent to set up the post-mortem, review meeting and Chat notice.
- 6Review the result. Check the created document, the calendar invite and the Chat message to confirm they went to the correct places.
What the skill makes the agent do
Agent skills are instruction packages that an AI agent loads so it knows how to perform a specific task. This one describes a three-step recipe for incident reviews in Google Workspace. The agent creates a Google Doc titled as a post-mortem, with a template outline of Summary, Timeline, Root Cause and Action Items.
It then schedules a one-hour Google Calendar review meeting with an attendee, and sends a short notification to a Google Chat space. The skill runs these steps through the gws command-line tool and relies on three other skills, gws-docs, gws-calendar and gws-chat, for the underlying actions.
Install the skill from the ZIP download
Download the ZIP for the skill from this page and unzip it. The skill is a folder containing a SKILL.md file. For a personal setup, place the folder in ~/.claude/skills/. For a single project, place it in that project's .claude/skills/ folder.
If you use the Claude apps instead, open Settings, go to Capabilities, and upload the skill under Skills.
- Personal: ~/.claude/skills/
- Project: .claude/skills/ inside the project folder
- Claude apps: Settings → Capabilities → Skills
Install the prerequisites
The recipe will not work on its own. You need the gws command-line tool (Google Workspace CLI) installed and authenticated with a Google account. You also need the gws-docs, gws-calendar and gws-chat skills, which the recipe loads first.
- gws command-line tool, installed and authenticated with a Google account
- gws-docs skill
- gws-calendar skill
- gws-chat skill
Trigger the skill with a natural request
You do not need special syntax. Describe the situation in plain language and name the incident, and the agent should pick up the recipe. Because each step writes to real systems, give the agent the details it needs: the incident name, and ideally the meeting time, attendee and Chat space you want.
Before running it on a live incident, check the hardcoded values described in the next section.
- "Set up a post-mortem for the payments outage on Tuesday."
- "Create the post-mortem doc and schedule the review for the checkout incident."
- "Notify the engineering Chat space that the database post-mortem is scheduled."
Edit the hardcoded values first
The skill file contains fixed example values. A 2026-03-16 meeting time, the attendee team@company.com and the Chat space spaces/ENG_SPACE are all hardcoded. If you do not change them, the invite and message can go to the wrong people or place.
The recipe's underlying commands look like this, with [Incident] as a placeholder for the incident name. Edit the attendee, times and space to match your team before the agent runs them.
gws docs +write --title 'Post-Mortem: [Incident]' --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Action Items'
gws calendar +insert --summary 'Post-Mortem Review: [Incident]' --attendee team@company.com --start '2026-03-16T14:00:00' --end '2026-03-16T15:00:00'
gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'Safety: scripts and network access
This skill runs scripts and uses the network. Each step writes to real systems: it creates a document, sends a calendar invite and posts to a Chat space. Nothing in the recipe asks for a review step between actions.
For sensitive incidents, do not let the agent act without reviewing what it is about to do. Confirm the attendee list and Chat space first, since a message posted to a shared space or an invite sent to the wrong people is hard to undo.
- Each step writes to real Google Workspace systems.
- Check the attendee, date, time and Chat space before running.
- Avoid unattended use for sensitive incidents.
Tips for reliable results
Keep the three prerequisite skills installed alongside this one, and confirm gws is authenticated before you ask for the recipe. Run the steps one at a time on your first try so you can see what each one produces. Once you trust the output, you can use the full sequence for routine incidents.
The recipe is most useful for teams that follow a standard post-mortem process. The template headings are fixed, so if your team uses different sections, edit the document body before use.
- Test on a non-sensitive or dummy space first.
- Verify gws authentication before running.
- Adjust the template headings if your process differs.
What people use it for
- Creating a standard post-mortem document with Summary, Timeline, Root Cause and Action Items sections after an outage.
- Scheduling a one-hour review meeting with the responsible team lead as the attendee.
- Posting a short notice to an engineering Chat space so the team knows a review is booked.
- Running the same three-step setup consistently across multiple incidents in one team.
Frequently asked questions
How do I install the Set Up Post-Mortem skill?
Download the ZIP from this page and unzip it. Place the folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder. In the Claude apps, you can instead upload it under Settings → Capabilities → Skills.
What do I need to run this agent skill?
You need the gws command-line tool (Google Workspace CLI) installed and authenticated with a Google account. You also need the gws-docs, gws-calendar and gws-chat skills, because the recipe depends on them.
Is the Set Up Post-Mortem skill free?
The skill is licensed under Apache-2.0. The source does not state pricing for the gws tool or Google Workspace, so check those separately.
Why does the agent send meetings to the wrong person or space?
The skill file hardcodes the attendee team@company.com, the Chat space spaces/ENG_SPACE and a 2026-03-16 meeting time. Edit these values in the skill to match your team before running it.
Does this skill work without Google Workspace?
No. The steps only work with Google Docs, Calendar and Chat, so teams that do not use Google Workspace cannot use it as written.
Can the agent run this without my review?
The skill runs scripts and uses the network, and each step writes to real systems. Review the attendees, times and Chat space before running it, especially for sensitive incidents.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits engineering or SRE teams that use Google Workspace and gws, and that follow a standard post-mortem template. Teams without Google Workspace, or handling sensitive incidents where automatic invites and posts are risky, should choose a different workflow or review every step manually.
Download the skill