Agent skill · software engineering · jeremylongshore
fireflies-local-dev-loop
Build a deterministic Fireflies development loop with recorded synthetic GraphQL fixtures, schema-contract tests, and no dependency on production meeting data. Use when implementing or debugging locally. Trigger with "Fireflies local development", "mock Fireflies GraphQL", or "Fireflies test fixture".
Why this skill is useful
Adds specific scripts and patterns for mocking Fireflies.ai API responses that the AI wouldn't generate on its own.
What it needs
Requires node 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 Privacy-Safe Local Development Overview Make local work reproducible without copying real transcripts, participant lists, summaries, or bearer keys onto developer machines. 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 Model GraphQL responses as data plus optional errors, preserve nullability, and keep separate fixtures for success, partial data, validation failure, authorization failure, rate limiting, and delayed processing. 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. Map the integration's operations and selected fields before creating fixtures. 2. Create synthetic meetings with invented IDs, speakers, sentences, summaries, and timestamps. 3. Record the exact GraphQL envelope shape, including errors and extensions where used. 4. Place the transport behind an injectable interface and route local tests to a deterministic mock server. 5. Add contract tests for null fields, pagination, partial data, and redaction. 6. Keep live tests opt-in, read-only, narrowly selected, and disabled without an explicit test key. 7. Document how fixtures are refreshed after a reviewed schema change. 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-local-dev-loop