Skip to content
TrustedSkillsbeta
Back to all skills

Recipe Post Mortem Setup

Checked
googleworkspace·vlatest·other·Apache-2.0

Analyzes past recipe creation attempts to identify common errors and proactively suggests setup improvements.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add googleworkspace/cli --skill recipe-post-mortem-setup -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

googleworkspace

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned googleworkspace/cli at a3768d0e82.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a3768d0e82
Manifest
skills/recipe-post-mortem-setup/SKILL.md
Scanned
1 file, 30 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to automatically configure and run post-mortem analysis workflows within Google Workspace environments. It streamlines the process of gathering incident data, generating reports, and facilitating team discussions after a service disruption or project failure.

When to use it

  • Automating the collection of logs and metrics immediately following a production outage.
  • Generating structured summary documents for engineering teams to review root causes.
  • Triggering scheduled retrospective meetings by preparing all necessary context materials in advance.
  • Standardizing incident reporting formats across different departments or projects.

Key capabilities

  • Integrates directly with Google Workspace tools to access relevant data sources.
  • Executes predefined post-mortem templates tailored to specific incident types.
  • Compiles findings into shareable documents suitable for stakeholder review.
  • Facilitates the transition from technical analysis to actionable improvement plans.

Example prompts

  • "Run a post-mortem setup for yesterday's API latency spike and draft the initial findings."
  • "Configure the post-mortem workflow for our Q3 project launch and gather all relevant metrics."
  • "Prepare a retrospective document based on the recent security incident report."

Tips & gotchas

Ensure you have appropriate permissions to access Google Workspace logs and documents before running this skill. The effectiveness of the analysis depends on the quality and completeness of the data available in your workspace at the time of execution.