Skip to content
skillsafebeta
← Report library
Purpose / Other

Recipe Post Mortem Setup Skill Security Audit

What the author says it does (original text)

Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.

Independent security check

Security risks found

Files checked
1
Risks found
2
Could it run dangerous commands?Looks for programs run straight after downloading, remote control of your computer, and hidden commands.No risks found
Could it expose your files or keys?Looks for uploads of files containing passwords or keys, and keys written directly in the code.Risks found: 1
Medium risk

The incident name is sent to fixed group and Chat destinations

Source references: 3
What we found

Both the calendar title and Chat message contain `[Incident]`, while the destinations are preset to `team@company.com` and `spaces/ENG_SPACE`. The recipe does not require confirmation that those recipients are authorized to know about the incident.

Why this matters

If the placeholder destinations are not replaced correctly or the space has broad membership, the existence and name of the incident could be disclosed to unintended recipients. Those recipients would also receive a real invitation or notification.

These are execution steps, not warnings or tests. The calendar invitation and Chat message send the incident name to preset destinations. Although `team@company.com`, `spaces/ENG_SPACE`, and `[Incident]` appear to be template placeholders, the recipe does not require verifying that the recipients are authorized. If an agent executes it directly or replaces only the incident name, incident information could reach the wrong people or space. A user can require recipient and authorization confirmation before sending.

SKILL.md:27In the instructionsOpen original file
1. Create post-mortem doc: `gws docs +write --title 'Post-Mortem: [Incident]' --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Action Items'`2. Schedule review meeting: `gws calendar +insert --summary 'Post-Mortem Review: [Incident]' --attendee team@company.com --start '2026-03-16T14:00:00' --end '2026-03-16T15:00:00'`3. Notify in Chat: `gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'`
Show 2 other places
SKILL.md:22In the instructionsOpen original file
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
SKILL.md:28In the instructionsOpen original file
2. Schedule review meeting: `gws calendar +insert --summary 'Post-Mortem Review: [Incident]' --attendee team@company.com --start '2026-03-16T14:00:00' --end '2026-03-16T15:00:00'`3. Notify in Chat: `gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'`
Could it delete files or keep running?Looks for broad file deletion, disk overwrites, and programs set to start automatically.No risks found
Could it bypass safety checks?Looks for skipped website security checks, excessive file access, or actions that skip your approval.No risks found
Could it mislead the AI or hide text?Checks the skill instructions for requests to ignore you, influence the report, or hide text in invisible characters.No risks found
Could it change links or payment recipients without asking?Looks for forced referral or payment changes combined with instructions to hide the change.Risks found: 1
Medium risk

The calendar step uses a fixed date and may send an incorrectly timed invitation

Source references: 1
What we found

The meeting start and end are hard-coded as 2026-03-16 14:00–15:00, with no instruction to replace or confirm them against the user's intended date and time zone.

Why this matters

Direct execution could create an incorrect or expired meeting, disrupt team calendars, and make the subsequent Chat message falsely state that the review was scheduled.

The calendar insertion is an active step with a fixed meeting time of 2026-03-16 14:00–15:00. It specifies no timezone and does not require replacement or confirmation against the user's intended date, time, and timezone. Running it as written could create a past or timezone-shifted event and send misleading invitations. A user can require preview and confirmation of the time, timezone, and attendees before creation.

SKILL.md:27In the instructionsOpen original file
1. Create post-mortem doc: `gws docs +write --title 'Post-Mortem: [Incident]' --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Action Items'`2. Schedule review meeting: `gws calendar +insert --summary 'Post-Mortem Review: [Incident]' --attendee team@company.com --start '2026-03-16T14:00:00' --end '2026-03-16T15:00:00'`3. Notify in Chat: `gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'`

Inside this skill

1 instruction sections

This Skill is a three-step operational recipe that creates a cloud post-mortem document, sends a calendar invitation, and posts a notice to a Google Chat space.

View source
SKILL.md:26In the instructionsOpen original file
1. Create post-mortem doc: `gws docs +write --title 'Post-Mortem: [Incident]' --body '## Summary\n\n## Timeline\n\n## Root Cause\n\n## Action Items'`2. Schedule review meeting: `gws calendar +insert --summary 'Post-Mortem Review: [Incident]' --attendee team@company.com --start '2026-03-16T14:00:00' --end '2026-03-16T15:00:00'`3. Notify in Chat: `gws chat +send --space spaces/ENG_SPACE --text '🔍 Post-mortem scheduled for [Incident].'`

Execution depends on the `gws` program and three Google Workspace Skills whose sources are not included, so the supplied material does not show how those dependencies handle credentials, permissions, or network requests.

View source
SKILL.md:9In the instructionsOpen original file
    domain: "engineering"    requires:      bins:        - gws      skills:        - gws-docs        - gws-calendar        - gws-chat---
SKILL.md:20In the instructionsOpen original file
> **PREREQUISITE:** Load the following skills to execute this recipe: `gws-docs`, `gws-calendar`, `gws-chat`
Start here · InstructionsSKILL.md
recipe-post-mortem-setup
Lines connect the instruction file to its sections, not an observed execution order. Select a section to read the source.
Files and check records1 files

Coverage and gaps

Content covered in each file

These are the source ranges included in this check, not a guarantee that every issue has been resolved.

  • SKILL.mdFull text included

This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.

  • SKILL.mdInstructions
Lines read
30
File checksum (to compare versions)
8ed45cba3f8deac3952c1f2037e05a615c259212cb8d3bf671588764178c3885