Agent skill · software engineering · jeremylongshore
fireflies-ci-integration
Build a Fireflies CI lane with static GraphQL validation, synthetic fixtures, secret scanning, webhook vectors, and narrowly gated live tests. Use when adding automated verification. Trigger with "Fireflies CI", "test Fireflies GraphQL", or "Fireflies contract test".
Why this skill is useful
Provides specific GitHub Actions workflows and integration testing patterns for Fireflies.ai that the AI wouldn't reliably generate on its own.
What it needs
Requires gh, vitest 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 Contract-Safe CI Overview Build a Fireflies CI lane with static GraphQL validation, synthetic fixtures, secret scanning, webhook vectors, and narrowly gated live tests. 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 Most CI should be offline and deterministic. Live tests require an explicitly provisioned read-only test identity, selected metadata fields, strict budgets, and no production meeting data. 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. Collect named GraphQL documents and validate syntax and variable declarations offline. 2. Test success, partial data, errors, nulls, pagination, and throttling with synthetic fixtures. 3. Verify Webhooks V2 HMAC vectors against raw bytes, malformed signatures, and duplicate events. 4. Add secret and sensitive-output assertions for logs and artifacts. 5. Gate optional live tests behind protected secrets and an explicit environment approval. 6. Limit live queries to approved metadata and one bounded request budget. 7. Publish test counts and safe failure metadata, never response bodies. Tool Discipline Use Read, Glob, and Grep to inspect code, configuration, tests, and evidence. Use Write/Edit only for approved implementation or documentation changes. Do not query Fireflies, retrieve meeting content, create an AskFred thread, upload media, change account state, replay an event, or deploy merely because this skill was invoked. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fireflies-ci-integration