recipe-post-mortem-setup
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-post-mortem-setup69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
42%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 effectively lists specific concrete actions across three Google services, demonstrating good specificity. However, it critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill over others. The trigger terms are decent but could include more natural variations users might say.
Suggestions
Add a 'Use when...' clause with trigger terms like 'incident review', 'post-mortem', 'outage report', 'retrospective', or 'incident follow-up'
Include natural language variations users might say, such as 'retro', 'incident report', 'RCA (root cause analysis)', or 'schedule a review meeting'
Clarify the workflow context to distinguish from general Google Workspace skills, e.g., 'Use when handling incident response workflows or post-incident documentation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists three specific concrete actions: 'Create a Google Docs post-mortem', 'schedule a Google Calendar review', and 'notify 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. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Contains relevant keywords like 'Google Docs', 'post-mortem', 'Google Calendar', 'review', and 'Chat', but missing common variations users might say like 'incident report', 'retro', 'meeting invite', or 'Slack/Teams notification'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Google Docs, Calendar, and Chat for post-mortems is somewhat specific, but could overlap with general Google Workspace skills or individual document/calendar skills without clearer trigger boundaries. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted recipe skill that excels in conciseness and actionability with executable CLI commands. The workflow is clear but could benefit from validation steps (e.g., confirming doc creation before scheduling, or handling failures). The prerequisite pattern for skill dependencies is clean.
Suggestions
Add brief validation guidance after each step (e.g., 'Confirm doc URL returned before proceeding')
Consider adding error handling hints for common failures (e.g., invalid space ID, calendar conflicts)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, assumes Claude knows what post-mortems are and how to use CLI tools. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable CLI commands with specific flags and example values. Copy-paste ready with clear placeholders for customization. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (create doc → schedule meeting → notify), but lacks validation checkpoints. No guidance on what to do if a step fails or how to verify success. | 2 / 3 |
Progressive Disclosure | Appropriately simple for a recipe-style skill. Clear prerequisite reference to other skills, well-organized with a single-level structure that's easy to follow. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- 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.