Agent skill · software engineering · jeremylongshore
fireflies-upgrade-migration
Migrate Fireflies GraphQL documents and webhook consumers away from deprecated fields and legacy event shapes with dual-read evidence and rollback. Use when responding after schema drift or documentation changes. Trigger with "upgrade Fireflies API", "Fireflies deprecated field", or "migrate Fireflies webhook".
Why this skill is useful
Adds executable scripts and migration patterns for handling Fireflies.ai API deprecations that are not publicly documented.
What it needs
Requires curl, grep, npm 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 Schema and Contract Migration Overview Migrate Fireflies GraphQL documents and webhook consumers away from deprecated fields and legacy event shapes with dual-read evidence and rollback. 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 Current transcript-list filters replace title with keyword and replace organizeremail and participantemail with organizers and participants. Webhooks V2 uses event, timestamp, meetingid, and granular meeting.transcribed or meeting.summarized events instead of the V1 eventType shape. 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. Inventory static GraphQL documents, selected fields, response parsers, webhook payloads, and fixtures. 2. Map deprecated fields and V1 webhook assumptions to current documented contracts. 3. Add compatibility parsing only where a measured transition requires it. 4. Update synthetic fixtures and contract tests before production traffic. 5. Run shadow comparisons on authorized metadata and compare IDs, counts, nullability, and event sequencing. 6. Cut over one operation or event family at a time with rollback flags. 7. Remove compatibility code only after the observation window and owner sign-off. 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-upgrade-migration