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 involving Google Workspace services, making it distinctive and specific. However, it critically lacks any 'Use when...' guidance, which means Claude would have to infer when to select this skill. Adding explicit trigger conditions and more natural user-facing keywords would significantly improve its effectiveness.
Suggestions
Add a 'Use when...' clause such as 'Use when the user requests a post-mortem, incident review, or retrospective that involves documenting in Google Docs and scheduling follow-up meetings.'
Include natural trigger term variations users might say, such as 'incident review', 'retrospective', 'RCA', 'root cause analysis', 'outage report', or 'blameless post-mortem'.
| 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 multi-service integration pattern is distinctive. | 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.
This is a concise, well-structured recipe skill that provides concrete CLI 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 reduce practical reusability. The prerequisite skills are mentioned but not linked.
Suggestions
Add validation checkpoints between steps, e.g., 'Verify the doc was created and capture its URL before proceeding to step 2' and 'Include the doc URL in the calendar invite and chat message'.
Replace the hardcoded date with guidance on parameterization, e.g., 'Set --start to the desired review date' or use a relative time reference.
Link the prerequisite skills directly, e.g., 'See [gws-docs](./gws-docs/SKILL.md)' so Claude can navigate to them if needed.
| 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 parameterize them. The bracket placeholders like '[Incident]' are helpful but the hardcoded date '2026-03-16T14:00:00' is problematic. | 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/validation is missing. | 2 / 3 |
Progressive Disclosure | The prerequisite skills are referenced but not linked. For a short recipe-style skill this is acceptable, but linking to the dependent skill files (gws-docs, gws-calendar, gws-chat) would improve navigation. The structure is otherwise clean and appropriate for the content length. | 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
c7c6646
- 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.