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

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/gamma-pack/skills/gamma-incident-runbook/SKILL.md

Quality

Content

65%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.

A thorough, actionable incident runbook with concrete executable commands and clear sequencing. Its main weaknesses are repetitive diagnostic blocks, missing validation/feedback checkpoints around destructive operations, and a monolithic single-file structure that could benefit from reference files.

Suggestions

Add explicit validation/verification steps after destructive or batch actions (e.g. after a deployment rollback, verify error rate returns to baseline before declaring mitigated).

Consolidate the repetitive Prometheus curl and grep blocks into a single parameterized snippet or a reference script to reduce token overhead.

Split the four detailed scenario runbooks into bundled reference files (e.g. references/scenarios.md) and keep SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	It is mostly efficient (tables, code blocks, checklists rather than concept exposition), but the three near-identical Prometheus curl queries and the repeated grep variants could be consolidated, so it could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready bash commands with concrete endpoints and flags (e.g. the status page curl, grep/tail log filters, throttle and circuit-breaker POST calls), meeting the score-3 anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (numbered diagnostics and per-scenario Actions, severity table, checklist), but destructive/batch operations like deployment rollback, circuit-breaker enabling, and backup-key deployment lack explicit validation checkpoints or verify-after feedback loops, which caps this at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but everything (diagnostics, four detailed scenario runbooks, templates, checklist) lives inline in a single ~240-line SKILL.md with no bundle reference files, so content that should be separate remains inline.	2 / 3
	Total	9 / 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 that clearly states purpose and provides explicit natural trigger phrases tied to a specific product. The only weakness is that the capability list is somewhat high-level rather than enumerating concrete distinct actions.

Dimension	Reasoning	Score
Specificity	It names the domain ('Gamma integration issues') and several actions ('Manage incident response', 'systematic troubleshooting procedures') but does not comprehensively enumerate distinct concrete actions like the score-3 anchor, so it sits at 'names domain and some actions'.	2 / 3
Completeness	It explicitly answers both 'what' (manage incident response for Gamma integration issues) and 'when' via an explicit 'Use when...' clause plus trigger phrases, so it is not capped at 2.	3 / 3
Trigger Term Quality	It lists multiple natural phrases a user would actually say ('gamma incident', 'gamma outage', 'gamma down', 'gamma emergency', 'gamma runbook'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	It is tied to a specific named product (Gamma) with brand-specific trigger phrases, making it clearly distinguishable and unlikely to fire for the wrong skill.	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/gamma-pack/skills/gamma-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.