Agent skill · software engineering · jeremylongshore
fireflies-sdk-patterns
Build a typed, bounded Fireflies GraphQL client with operation names, variables, error handling, redaction, and dependency injection. Use when replacing ad hoc requests or a fictional SDK wrapper. Trigger with "Fireflies client pattern", "type Fireflies GraphQL", or "Fireflies API wrapper".
Why this skill is useful
Provides specific GraphQL client patterns and error handling for Fireflies.ai that the AI wouldn't reliably generate on its own.
What it needs
Requires python, typescript 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 Typed GraphQL Client Patterns Overview Fireflies documents a GraphQL API, not a required first-party language SDK. Keep the transport standards-based and generate or hand-maintain types only from reviewed schema evidence. 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 Every call should carry an operation name, static document, typed variables, an explicit field selection, timeout, and response parser that handles both data and errors. Never interpolate values into GraphQL source or expose bearer keys to clients. 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 operations and remove undocumented SDK method assumptions. 2. Choose a maintained GraphQL transport compatible with the repository rather than adding a redundant wrapper stack. 3. Define static documents and typed variables for each approved operation. 4. Centralize endpoint, bearer injection, timeouts, request IDs, redaction, and GraphQL error normalization. 5. Return domain-specific results that preserve nullability and partial-data semantics. 6. Inject the client into callers and provide a fixture transport for tests. 7. Pin dependencies and add schema-drift checks without enabling unrestricted introspection in production. 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-sdk-patterns