fireflies-incident-runbook

Execute Fireflies.ai incident response with triage, remediation, and postmortem. Use when responding to Fireflies.ai API outages, auth failures, or webhook delivery problems. Trigger with phrases like "fireflies incident", "fireflies outage", "fireflies down", "fireflies on-call", "fireflies emergency", "fireflies broken".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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

An action-dense, well-sequenced incident runbook with executable commands and clear triage-to-remediation flow. Its main weakness is progressive disclosure: everything lives in one file rather than splitting templates and detailed remediation into referenced bundle files.

Suggestions

Move the communication and postmortem templates into a references/ file (e.g. references/templates.md) and link to it from the body to reduce inline bulk.

Extract the per-error-type remediation details (auth_failed, rate limiting, webhook signature debugging) into a references/remediation.md, keeping only the decision tree and quick triage in SKILL.md.

Add a short 'Prerequisites' note confirming FIREFLIES_API_KEY and network access expectations so the triage checkpoint's failure modes are explicit up front.

Dimension	Reasoning	Score
Conciseness	Lean runbook using tables, a decision tree, and executable code blocks; avoids explaining concepts Claude already knows and keeps prose minimal, so most tokens earn their place.	3 / 3
Actionability	Provides copy-paste-ready curl/bash commands, concrete secret-store update steps, and a routing decision tree with specific fixes per error code, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Clear sequence ('Quick Triage (Run First)' -> decision tree -> remediation by error type) with the triage script as a validation checkpoint and an error-handling table for recovery; severity and output checklists reinforce the flow.	3 / 3
Progressive Disclosure	Sections are well organized, but the ~200-line body is monolithic: templates, per-error remediation, and signature-debug code that could live in reference files are all inline, with no bundle files present to offload detail.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 well-crafted description that concisely states the skill's actions, gives explicit use-when guidance, and lists natural trigger phrases tied to a distinct niche. No first/second-person voice or vague fluff.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions in third person ('Execute Fireflies.ai incident response with triage, remediation, and postmortem'), matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (triage, remediation, postmortem) and when ('Use when responding to Fireflies.ai API outages, auth failures, or webhook delivery problems'), matching the top anchor.	3 / 3
Trigger Term Quality	Provides strong natural-language coverage ('fireflies incident', 'fireflies outage', 'fireflies down', 'fireflies on-call', 'fireflies emergency', 'fireflies broken') that users would plausibly say, matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Fireflies.ai incident response) with Fireflies-specific triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: 6e3a65f

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.