Agent skill · software engineering · jeremylongshore

fireflies-deploy-integration

Deploy a Fireflies GraphQL worker or Webhooks V2 receiver with managed secrets, raw-body verification, bounded queues, and reversible rollout. Use when shipping to a hosted runtime. Trigger with "deploy Fireflies integration", "host Fireflies webhook", or "Fireflies deployment".

Why this skill is useful

Adds deployment scripts and specific integration patterns for Fireflies.ai across multiple platforms that aren't in public documentation.

What it needs

Requires docker, gcloud, vercel 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 Deployment and Webhook Boundary Overview Deploy a Fireflies GraphQL worker or Webhooks V2 receiver with managed secrets, raw-body verification, bounded queues, and reversible rollout. 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 Outbound GraphQL needs a server-side bearer key. Inbound Webhooks V2 needs HTTPS, optional but strongly recommended signing-secret verification over the raw body, a 2xx response within 10 seconds, and durable asynchronous work after acknowledgement. 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. Define the exact runtime, regions, data boundary, operations, events, and owners. 2. Provision separate API and webhook secrets through the platform secret manager. 3. Preserve raw request bytes until HMAC verification and parse only after success. 4. Acknowledge valid events within 10 seconds and enqueue idempotent downstream work. 5. Set timeouts, concurrency, quotas, dead-letter handling, and content-free logs. 6. Roll out to staging with synthetic events, then canary production traffic. 7. Verify disablement, secret rotation, queue drain, and rollback receipts. 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-deploy-integration--c709c1

View the source on GitHub

Browse the @skills marketplace