Orchestrate post-mortem workflows across Google Docs, Calendar, and Chat in one recipe.
Works with
Combines three Google Workspace skills to create a structured post-mortem document, schedule a review meeting, and send a team notification
Requires gws-docs , gws-calendar , and gws-chat skills to be loaded before execution
Provides templated steps with customizable incident names, attendees, and meeting times for consistent incident response processes
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrecipe-post-mortem-setupExecute the skills CLI command in your project's root directory to begin installation:
Fetches recipe-post-mortem-setup from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate recipe-post-mortem-setup. Access via /recipe-post-mortem-setup in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
1d:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"<h1>Set Up Post-Mortem</h1>\n<blockquote>\n<p><strong>PREREQUISITE:</strong> Load the following skills to execute this recipe: <code>gws-docs</code>, <code>gws-calendar</code>, <code>gws-chat</code></p>\n</blockquote>\n<p>Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.</p>\n<h2>Steps</h2>\n<ol>\n<li>Create post-mortem doc: <code>gws docs +write --title 'Post-Mortem: [Incident]' --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Action Items'</code></li>\n<li>Schedule review meeting: <code>gws calendar +insert --summary 'Post-Mortem Review: [Incident]' --attendee [email protected] --start '2026-03-16T14:00:00' --end '2026-03-16T15:00:00'</code></li>\n<li>Notify in Chat: <code>gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'</code></li>\n</ol>"}}]
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
recipe-post-mortem-setup is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in recipe-post-mortem-setup — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
recipe-post-mortem-setup has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for recipe-post-mortem-setup matched our evaluation — installs cleanly and behaves as described in the markdown.
recipe-post-mortem-setup reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend recipe-post-mortem-setup for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: recipe-post-mortem-setup is focused, and the summary matches what you get after install.
We added recipe-post-mortem-setup from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend recipe-post-mortem-setup for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
recipe-post-mortem-setup reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 26