Agent skill · software engineering · jeremylongshore
fireflies-hello-world
Run the smallest current Fireflies GraphQL query and verify identity, response structure, and data-minimization controls without dumping transcripts. Use when testing a new server-side integration. Trigger with "Fireflies hello world", "first Fireflies query", or "verify Fireflies setup".
Why this skill is useful
Adds executable scripts for Fireflies.ai GraphQL API interactions that are not available in public documentation.
What it needs
Requires curl, jq 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 First Metadata Query Overview Prove the GraphQL transport with low-sensitivity metadata. Do not use a real meeting transcript as a quick-start fixture or log user email addresses merely to show that the request worked. 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 The public API is GraphQL over POST. A minimal user or users selection is the documented quickstart; clients must examine the top-level errors array even when the HTTP response is 200 and request only fields necessary for the smoke test. 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. Confirm the API key owner and test environment are authorized for the request. 2. Choose the user query and select only an opaque identifier or other approved metadata. 3. Send one POST request with JSON query and variables from a server-side client. 4. Assert HTTP success, absence of GraphQL errors, presence of data, and the expected response shape. 5. Log only timing, operation name, correlation ID, and pass/fail status. 6. Exercise a synthetic failure without exposing the bearer key. 7. Keep the smoke test only if its data access and request budget are acceptable. 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-hello-world