Agent skill · marketing growth · jeremylongshore
fireflies-incident-runbook
Triage Fireflies auth, privacy, webhook, quota, data exposure, processing, and privileged-mutation incidents with containment and evidence boundaries. Use when responding during a live failure or suspected leak. Trigger with "Fireflies incident", "Fireflies outage", or "Fireflies data leak".
Why this skill is useful
Adds executable scripts for incident triage and remediation specific to Fireflies.ai API issues that aren't publicly documented.
What it needs
Requires jq installed locally. Requires fireflies account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Fireflies Integration Incident Runbook Overview Triage Fireflies auth, privacy, webhook, quota, data exposure, processing, and privileged-mutation incidents with containment and evidence boundaries. Prerequisites The target repository or integration path and the requested operator outcome. The Fireflies principal, team, environment, and data classification for the work. Current Fireflies documentation, credentials only when needed, and an accountable approver. Current Contract Classify incidents by confidentiality, integrity, availability, and destructive impact. Containment may mean disabling a consumer, revoking a key, pausing a queue, rejecting webhooks, or blocking mutations; preserve content-free evidence and coordinate destructive actions. Authentication For authenticated operations, inject FIREFLIESAPIKEY from an approved secret manager and send it only as Authorization: Bearer REDACTEDKEY to https://api.fireflies.ai/graphql. Never print, commit, place in a URL, forward to a browser, or include the key in evidence. Webhook signing secrets are separate credentials and must not be reused as API keys. Instructions 1. Declare an owner, severity, affected environment, timeline, and known operation or event family. 2. Contain the smallest boundary: caller, key, webhook endpoint, queue, worker, or mutation feature. 3. Preserve redacted logs, request IDs, GraphQL codes, signature results, deployments, and configuration revisions. 4. Determine whether meeting data, bearer keys, signing secrets, roles, privacy, shares, channels, or deletions were affected. 5. Rotate secrets or disable access only through the accountable owner and record the action. 6. Recover with synthetic or metadata-only probes and bounded traffic. 7. Document root cause, affected records through an approved channel, corrective actions, and follow-up tests. Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, tests, and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fireflies-incident-runbook