Agent skill · software engineering · jeremylongshore
fireflies-prod-checklist
Run a fail-closed readiness review for a Fireflies integration covering identity, schema contracts, privacy, quotas, webhooks, observability, rollback, and ownership. Use when preparing before enabling production traffic. Trigger with "Fireflies production checklist", "ship Fireflies integration", or "Fireflies go-live review".
Why this skill is useful
Adds executable scripts for Fireflies.ai deployment health checks and rollback procedures that are not publicly documented.
What it needs
Requires curl, 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 Production Readiness Gate Overview Run a fail-closed readiness review for a Fireflies integration covering identity, schema contracts, privacy, quotas, webhooks, observability, rollback, and ownership. 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 Readiness is evidence, not a successful demo. The release must prove its exact operations, selected fields, permission model, quotas, webhook behavior, failure modes, rollback, and retention controls against the current public contract. 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. Pin the release revision and enumerate GraphQL operations and Webhooks V2 events. 2. Verify secret ownership, rotation, redaction, and environment isolation. 3. Review every selected field and derived output against classification and retention. 4. Exercise success, GraphQL error, timeout, throttling, null/processing, invalid signature, and duplicate webhook paths. 5. Confirm operation-specific budgets, queue limits, alerts, dashboards, and runbooks. 6. Test rollback or feature disablement without deleting source records. 7. Obtain accountable approvals and archive a content-free launch receipt. Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, tests, and evidence. Use Write/Edit only for approved implementation or documentation changes. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fireflies-prod-checklist--ee9704