Agent skill · data analytics · jeremylongshore
fireflies-observability
Instrument Fireflies GraphQL and webhook workflows with operation, latency, quota, queue, signature, and processing metrics that exclude meeting content and identities. Use when building dashboards or alerts. Trigger with "monitor Fireflies", "Fireflies metrics", or "Fireflies webhook alerts".
Why this skill is useful
Adds specific metrics and monitoring patterns for Fireflies.ai integration that the AI wouldn't reliably generate on its own.
What it needs
Requires grafana, prometheus 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 Content-Free Observability Overview Instrument Fireflies GraphQL and webhook workflows with operation, latency, quota, queue, signature, and processing metrics that exclude meeting content and identities. 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 Observability may include operation name, result class, GraphQL code, duration, response size bucket, retryAfter, event type, signature result, queue depth, and processing latency. It must exclude Authorization, queries with variables, meeting IDs, emails, titles, sentences, summaries, and media URLs. 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 service-level indicators for GraphQL success, webhook acknowledgement, queue processing, and freshness. 2. Instrument safe dimensions with a strict allowlist and cardinality budget. 3. Track plan and operation-specific throttles separately. 4. Measure transcribed-to-summarized and event-to-processing latency without meeting IDs in metrics. 5. Alert on auth failures, signature failures, throttle spikes, backlog, dead letters, and stale processing. 6. Keep detailed identifiers only in access-controlled audit records when approved. 7. Test telemetry redaction with synthetic secrets and meeting data. 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-observability