Skip to content
Skills Library
Programming · Testing

fireflies-local-dev-loop

/fireflies-local-dev-loop

Build a deterministic Fireflies development loop with recorded synthetic GraphQL fixtures, schema-contract tests, and no dependency on production meeting data. Use when implementing or debugging locally. Trigger with "Fireflies local development", "mock Fireflies GraphQL", or "Fireflies test fixture".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build a deterministic Fireflies development loop with recorded synthetic GraphQL fixtures, schema-contract tests, and no dependency on production meeting data. Use when implementing or debugging locally. Trigger with "Fireflies local development", "mock Fireflies GraphQL", or "Fireflies test fixture".

Triggers from the description

Fireflies local developmentmock Fireflies GraphQLFireflies test fixture

Arguments

/fireflies-local-dev-loop <repository-path> <test-command>
Original author description

Build a deterministic Fireflies development loop with recorded synthetic GraphQL fixtures, schema-contract tests, and no dependency on production meeting data. Use when implementing or debugging locally. Trigger with "Fireflies local development", "mock Fireflies GraphQL", or "Fireflies test fixture".

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Output
  9. Validation
  10. Error Handling
Original SKILL.md headings · 61 lines, 469 words
SKILL.md preview
---
name: fireflies-local-dev-loop
description: >-
  Build a deterministic Fireflies development loop with recorded synthetic GraphQL fixtures, schema-contract tests, and no dependency on production meeting data. Use when implementing or debugging locally. Trigger with "Fireflies local development", "mock Fireflies GraphQL", or "Fireflies test fixture".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<repository-path> <test-command>"
version: 1.12.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, fireflies, development, testing]
model: inherit
effort: medium
compatibility: "Designed for Claude Code; live Fireflies work requires network access"
---
# Fireflies Privacy-Safe Local Development

## Overview

Make local work reproducible without copying real transcripts, participant lists, summaries, or bearer keys onto developer machines.

## 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

Model GraphQL responses as data plus optional errors, preserve nullability, and keep separate fixtures for success, partial data, validation failure, authorization failure, rate limiting, and delayed processing.

## Authentication

For authenticated operations, inject `FIREFLIES_API_KEY` from an approved secret manager and send it only as `Authorization: Bearer REDACTED_KEY` 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. Map the integration's operations and selected fields before creating fixtures.
2. Create synthetic meetings with invented IDs, speakers, sentences, summaries, and timestamps.
3. Record the exact GraphQL envelope shape, including errors and extensions where used.
4. Place the transport behind an injectable interface and route local tests to a deterministic mock server.
5. Add contract tests for null fields, pagination, partial data, and redaction.
6. Keep live tests opt-in, read-only, narrowly selected, and disabled without an explicit test key.
7. Document how fixtures are refreshed after a reviewed schema change.

## Tool Discipline

Use Read, Glob, and Grep to inspect code, configuration, tests, and evidence. Use Write/Edit only for approved implementation or documentation changes. Do not query Fireflies, retrieve meeting content, create an AskFred thread, upload media, change account state, replay an event, or deploy merely because this skill was invoked.

## Approval Boundaries

Require approval before recording a live response, connecting a local process to production, or storing any real meeting-derived content.

## Output

Return the exact operation or event surface, environment, authorization class, selected field groups, validation results, content-free metrics, decisions, and a concise pass/fail receipt. Keep secrets and meeting-derived content out of general output.

## Validation

Before reporting success, rerun the smallest relevant deterministic check, compare actual state with the requested outcome and current contract, verify no secret or meeting-derived content entered logs or artifacts, and record unresolved uncertainty explicitly.

## Error Handling

- Fixture drift: update only from current schema evidence and review the diff.
- Secret appears in snapshot: stop, revoke if exposed, and remove it from history through the approved incident path.
- Mock-only success: run the authorized read-only contract lane before release.

## Examples

- "Mock a completed transcript" uses invented participant and sentence data.
- "Download one customer meeting for fixtures" is rejected.

## Resources

Read [official Fireflies.ai evidence](references/official-docs.md) before relying on a field, filter, event, permission, plan limit, mutation, or processing state.
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 2 KB

Versions

RepositoryScoreLicence
This page · jeremylongshore/tons-of-skills-marketplace100MIT
HelixDevelopment/agent100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 734eeb27676e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100fireflies-ci-integration
    Build a Fireflies CI lane with static GraphQL validation, synthetic fixtures, secret scanning, webhook vectors, and narrowly gated live tests. Use when adding automated verification. Trigger with "Fireflies CI", "test Fireflies GraphQL", or "Fireflies contract test".
  • 100firecrawl-local-dev-loop
    Build a deterministic Firecrawl development loop with SDK fakes, recorded synthetic contracts, and an optional trusted-network self-hosted stack. Use when developing without production data or routine Cloud spend. Trigger with "Firecrawl local dev", "mock Firecrawl", or…
  • 100fireflies-common-errors
    Diagnose and fix Fireflies.ai common errors and exceptions. Use when encountering Fireflies.ai errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "fireflies error", "fix fireflies", "fireflies not working", "debug fireflies".
  • 100fireflies-install-auth
    Install and configure Fireflies.ai SDK/CLI authentication. Use when setting up a new Fireflies.ai integration, configuring API keys, or initializing Fireflies.ai in your project. Trigger with phrases like "install fireflies", "setup fireflies", "fireflies auth", "configure fireflies API key".
  • 100fireflies
    Query Fireflies.ai meeting transcripts, meeting notes, summaries, contacts, channels, AI meeting analytics, AskFred, audio uploads, and webhook signatures through its GraphQL API. Use when a user mentions Fireflies, Fireflies.ai, meeting transcripts or notes stored in Fireflies,…
  • 100fireflies-transcript
    Fetch raw Fireflies.ai meeting transcripts. Use only when the user explicitly invokes /fireflies-transcript; for YouTube, use youtube-transcript.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.