granola-incident-runbook

Incident response procedures for Granola meeting capture failures and outages. Use when meetings aren't recording, transcription fails mid-meeting, integrations stop syncing, or the Granola service is down. Trigger: "granola incident", "granola outage", "granola down", "granola not recording", "granola emergency".

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an actionable, well-sequenced incident runbook with concrete commands, templates, and checklists that respect token budget. Its main weakness is progressive disclosure: the provided implementation.md reference is neither linked from the body nor differentiated from it, creating duplication rather than clean one-level-deep navigation.

Suggestions

Link references/implementation.md from the body (e.g. 'See [implementation.md](references/implementation.md) for expanded quick-fix steps and templates') so the bundle is discoverable.

De-duplicate: keep the severity triage and escalation framework in SKILL.md and move the per-incident quick-fix detail into implementation.md, or vice-versa, so the two files are clearly one level deep rather than overlapping.

Consider moving the post-incident report template and communication templates (which are reference material) into implementation.md to slim the overview.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout — tables, shell commands, checkbox checklists, and message templates with no padding or explanations of concepts Claude already knows (e.g. 'Granola stops transcription after ~15 minutes of no detected audio' is domain-specific knowledge worth keeping), matching the level-3 anchor.	3 / 3
Actionability	It provides fully executable commands (curl status check, pgrep/pkill), specific UI steps ('Click Granola menu bar icon > Start Recording'), per-integration fix tables, and copy-paste Slack/report templates, matching the level-3 'copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps are explicitly sequenced (Step 1 Triage → Step 2 Remediation → Step 3 Escalation → Step 4 Post-Incident) with a severity-assessment checkpoint, root-cause checklists, and an Error Handling table for recovery feedback, matching the level-3 anchor.	3 / 3
Progressive Disclosure	A references/implementation.md bundle exists but is never linked or signaled from the body, and it duplicates incident content already inline; the body is a long monolithic runbook that could be split, fitting the level-2 'references present but not clearly signaled; content that should be separate is inline' anchor rather than level 3.	2 / 3
	Total	11 / 12 Passed

Description

90%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description with explicit 'Use when' guidance and natural trigger terms targeting a clear Granola-specific niche. The only weakness is that the capability statement ('incident response procedures') is somewhat abstract rather than enumerating concrete actions.

Suggestions

Replace the abstract 'Incident response procedures' with concrete verbs, e.g. 'Triages, remediates, and escalates Granola meeting capture failures and outages'.

Dimension	Reasoning	Score
Specificity	The phrase 'Incident response procedures for Granola meeting capture failures and outages' names the domain and lists failure scenarios, but the action verb is the abstract 'procedures' rather than multiple concrete actions (e.g. triage, remediate, escalate), so it stops short of the level-3 anchor.	2 / 3
Completeness	It answers both 'what' (incident response procedures for Granola failures/outages) and 'when' via an explicit 'Use when meetings aren't recording, transcription fails mid-meeting, integrations stop syncing, or the Granola service is down' clause, matching the level-3 anchor.	3 / 3
Trigger Term Quality	The explicit 'Trigger: "granola incident", "granola outage", "granola down", "granola not recording", "granola emergency"' gives good coverage of natural phrases a user would say, matching the level-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The Granola-specific niche plus distinctive 'granola incident/outage/down' triggers make it clearly distinguishable and unlikely to fire for the wrong skill, matching the level-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/granola-pack/skills/granola-incident-runbook/SKILL.md
Commit: 4c47e33

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.