Agent skill · software engineering · jeremylongshore
fireflies-multi-env-setup
Separate Fireflies development, staging, and production identities, webhook endpoints, secrets, quotas, fixtures, and observability. Use when preventing cross-environment leakage. Trigger with "Fireflies environments", "staging Fireflies", or "separate Fireflies keys".
Why this skill is useful
Adds a detailed multi-environment setup for Fireflies.ai with specific API keys and configurations that the AI wouldn't reliably generate on its own.
What it needs
Requires gcloud 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 Multi-Environment Isolation Overview Separate Fireflies development, staging, and production identities, webhook endpoints, secrets, quotas, fixtures, and observability. Prove isolation through configuration and failure-path evidence rather than environment names alone. 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 Each environment should have an explicit Fireflies principal, API key, webhook signing secret, endpoint, allowed operations, event subscriptions, data policy, quota, and owner. Configuration names are not isolation if credentials or queues are shared. 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. Inventory every environment and its Fireflies user or team context. 2. Provision distinct bearer and signing secrets and prohibit production fallback. 3. Use environment-specific HTTPS webhook URLs, queues, stores, and dead letters. 4. Allow only synthetic data in development and reviewed test records in staging. 5. Validate configuration at startup without logging secret values. 6. Tag content-free metrics with environment and operation, never meeting identity. 7. Test rotation and rollback independently in each environment. 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-multi-env-setup