recipe-post-mortem-setup
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
65
57%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-post-mortem-setup/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description clearly lists three specific concrete actions forming a distinct post-mortem workflow across Google services, which is a strength. However, it critically lacks any 'Use when...' clause or trigger guidance, making it incomplete for Claude's skill selection process. Adding explicit trigger terms and common user phrasings would significantly improve its effectiveness.
Suggestions
Add a 'Use when...' clause such as 'Use when the user requests a post-mortem, incident review, retrospective, or RCA workflow across Google Workspace.'
Include common user-facing trigger variations like 'incident report', 'outage review', 'retrospective', 'root cause analysis', or 'post-incident review'.
Specify the integration context more broadly, e.g., mention 'Google Workspace' and 'Google Chat' explicitly to help distinguish from generic document or calendar skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists three specific concrete actions: creating a Google Docs post-mortem, scheduling a Google Calendar review, and notifying via Chat. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'post-mortem', 'Google Docs', 'Google Calendar', and 'Chat', but misses common variations users might say such as 'incident review', 'retrospective', 'RCA', 'outage report', or 'Slack/Teams notification'. The terms are somewhat product-specific but not comprehensive. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Google Docs post-mortem creation, Google Calendar scheduling, and Chat notification is a very specific workflow niche that is unlikely to conflict with other skills. The post-mortem context makes it clearly distinguishable. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured recipe that provides concrete commands for a three-step post-mortem workflow. Its main weaknesses are the lack of validation between steps (e.g., confirming doc creation before scheduling) and hardcoded values like dates that should be parameterized. The prerequisite callout is a nice touch but could benefit from direct links to the referenced skills.
Suggestions
Add validation checkpoints between steps, e.g., 'Verify the doc was created and capture its URL before proceeding to step 2' and 'Confirm the calendar event was created before notifying in Chat'.
Replace the hardcoded date with guidance on how to determine the appropriate date, or note that the date should be adjusted to the desired review time.
Include the doc URL in the chat notification and calendar event description to link the artifacts together, making the workflow more cohesive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what post-mortems are or how Google Workspace APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Commands are concrete and copy-paste ready, but they contain hardcoded placeholder values (dates, space IDs, email addresses) without guidance on how to substitute them. The bracket placeholders like [Incident] are helpful but the hardcoded date '2026-03-16T14:00:00' is problematic as it should be parameterized or explained. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced, but there are no validation checkpoints—no verification that the doc was created successfully before scheduling the meeting, or that the meeting was created before sending the chat notification. For a multi-step workflow involving document creation and notifications, error handling/verification is missing. | 2 / 3 |
Progressive Disclosure | The prerequisite note referencing dependent skills is good progressive disclosure, but the skill doesn't link to those skill files or provide any navigation for learning more about the individual commands. For a short skill this is acceptable but could be improved with explicit links. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- googleworkspace/cli
- Commit
a3768d0
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.