gamma-incident-runbook

Manage incident response for Gamma integration issues. Use when experiencing production incidents, outages, or need systematic troubleshooting procedures. Trigger with phrases like "gamma incident", "gamma outage", "gamma down", "gamma emergency", "gamma runbook".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The content is highly actionable with concrete commands for each incident scenario and clear sequencing, but it is weighed down by unnecessary inline explanatory comments and a monolithic structure with no progressive disclosure or validation checkpoints on risky operations.

Suggestions

Remove explanatory comments for well-known concepts (e.g. Prometheus port 9090, HTTP 429) to tighten token efficiency.

Add explicit validate-then-proceed feedback loops to scenarios involving risky actions (deployment rollback, circuit breaker, key rotation) so workflow clarity can reach 3.

Move communication templates and detailed scenario procedures into referenced bundle files (e.g. TEMPLATES.md, SCENARIOS.md) with one-level-deep links to enable proper progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and structured tables, but it is padded with comments explaining concepts Claude already knows (repeated "# Prometheus port", "# HTTP 429 Too Many Requests", "# Check Gamma status page"), so it could be tightened rather than earning the lean score.	2 / 3
Actionability	It provides concrete, copy-paste-ready curl/grep/awk commands with specific endpoints and parameters across diagnostics and each incident scenario, giving fully executable guidance.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1-3 diagnostics, numbered scenario actions), but workflows involving risky operations like deployment rollback, circuit breaker, throttling, and key rotation lack explicit validation/verification checkpoints, capping this dimension at 2 per the destructive/batch guidance.	2 / 3
Progressive Disclosure	The skill is a single ~265-line monolithic file with no bundle references (references/scripts/assets absent) and inline content such as templates and detailed scenarios that could be split out; it is well-sectioned but does not progressively disclose to separate files.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 is strong: it covers both what the skill does and when to trigger it using natural, distinctive phrases tied to a specific integration. Its only weakness is specificity, where actions remain high-level rather than a concrete enumerated list.

Dimension	Reasoning	Score
Specificity	Names the domain and high-level actions ("Manage incident response for Gamma integration issues", "systematic troubleshooting procedures") but does not list multiple concrete actions like extract/fill/merge, so it stops at the domain-and-some-actions level.	2 / 3
Completeness	Clearly states what it does ("Manage incident response for Gamma integration issues") and when to use it ("Use when experiencing production incidents, outages, or need systematic troubleshooting procedures") with explicit trigger guidance, satisfying both what and when.	3 / 3
Trigger Term Quality	Explicitly enumerates natural trigger phrases a user would say ("gamma incident", "gamma outage", "gamma down", "gamma emergency", "gamma runbook") alongside "production incidents, outages", giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The Gamma-specific niche and dedicated trigger phrases ("gamma incident", "gamma outage", etc.) make it clearly distinguishable and unlikely to fire for unrelated skills.	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
Commit: 1628598

Reviewed: 1 day 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.