Agent skill · marketing growth · jeremylongshore
fireflies-install-auth
Establish a least-privilege Fireflies API identity, protect its bearer key, and prove the authenticated GraphQL boundary without exposing meeting data. Use when bootstrapping or repairing an integration. Trigger with "configure Fireflies API", "Fireflies auth failed", or "rotate Fireflies key".
Why this skill is useful
Provides specific commands and scripts for authenticating and verifying connectivity with the Fireflies.ai GraphQL API that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python 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 API Identity and Access Setup Overview Create an auditable identity boundary before any transcript query or mutation. A successful request proves only that the key is accepted; it does not grant permission to enumerate or export meeting content. 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 Fireflies uses POST requests to https://api.fireflies.ai/graphql with Content-Type application/json and Authorization: Bearer <API key>. Obtain the key from the Fireflies Integrations page, keep it server-side, and use the smallest identity query needed to confirm the principal and team context. 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. Identify the owning Fireflies user or team, intended environment, and exact read or mutation capabilities. 2. Create or retrieve the API key through the Fireflies dashboard; never ask a user to paste it into chat. 3. Store the key in the approved secret manager and inject it as FIREFLIESAPIKEY only at runtime. 4. Send a minimal user query from a controlled server-side client and inspect both HTTP status and the GraphQL errors array. 5. Record the authenticated user ID, team context, key owner, storage location, and rotation owner without recording the key. 6. Test an invalid-key path and confirm logs redact Authorization and response data. 7. Document rotation and revocation steps before enabling production access. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/fireflies-install-auth