Agent skill · product strategy · jeremylongshore
fireflies-reference-architecture
Design a Fireflies architecture that separates identity, GraphQL reads, privileged mutations, Webhooks V2 intake, queues, sensitive data, and derived outputs. Use when performing system design or review. Trigger with "Fireflies architecture", "design Fireflies pipeline", or "Fireflies integration blueprint".
Why this skill is useful
Provides specific integration patterns and GraphQL commands for Fireflies.ai that the AI wouldn't reliably 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 Governed Integration Architecture Overview Design a Fireflies architecture that separates identity, GraphQL reads, privileged mutations, Webhooks V2 intake, queues, sensitive data, and derived outputs. 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 Use separate trust boundaries for bearer-authenticated outbound GraphQL, signature-authenticated inbound events, durable orchestration, meeting-content storage, and derived destinations. An event carries an identity, not permission to fetch every field. 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 actors, principals, environments, operations, event types, data classes, and sinks. 2. Keep API and signing secrets in separate managed stores and rotation paths. 3. Place static GraphQL documents behind a policy-aware service boundary. 4. Verify and acknowledge webhooks at the edge, then enqueue idempotent jobs. 5. Fetch only authorized fields and isolate raw, summarized, and derived data stores. 6. Add per-operation budgets, audit receipts, dead letters, deletion propagation, and rollback controls. 7. Threat-model cross-team access, replay, duplicate events, stale processing, and downstream leakage. 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-reference-architecture