fireflies-local-dev-loop
Configure local development workflow for Fireflies.ai GraphQL integrations. Use when setting up a development environment, mocking transcript data, or establishing a fast iteration cycle with the Fireflies API. Trigger with phrases like "fireflies dev setup", "fireflies local development", "fireflies dev environment", "develop with fireflies", "mock fireflies".
Best use case
fireflies-local-dev-loop is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure local development workflow for Fireflies.ai GraphQL integrations. Use when setting up a development environment, mocking transcript data, or establishing a fast iteration cycle with the Fireflies API. Trigger with phrases like "fireflies dev setup", "fireflies local development", "fireflies dev environment", "develop with fireflies", "mock fireflies".
Teams using fireflies-local-dev-loop should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/fireflies-local-dev-loop/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How fireflies-local-dev-loop Compares
| Feature / Agent | fireflies-local-dev-loop | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure local development workflow for Fireflies.ai GraphQL integrations. Use when setting up a development environment, mocking transcript data, or establishing a fast iteration cycle with the Fireflies API. Trigger with phrases like "fireflies dev setup", "fireflies local development", "fireflies dev environment", "develop with fireflies", "mock fireflies".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# Fireflies.ai Local Dev Loop
## Overview
Set up a fast local development workflow for Fireflies.ai integrations: project structure, mock data for offline development, test helpers, and API response recording for replay.
## Prerequisites
- Completed `fireflies-install-auth` setup
- Node.js 18+ with npm/pnpm
- Vitest for testing
## Instructions
### Step 1: Project Structure
```
my-fireflies-app/
src/
lib/
fireflies-client.ts # GraphQL client (see fireflies-sdk-patterns)
transcript-service.ts # Business logic layer
types/
fireflies.ts # TypeScript interfaces
tests/
fixtures/
transcript.json # Recorded API responses
fireflies-client.test.ts
transcript-service.test.ts
.env.local # FIREFLIES_API_KEY (git-ignored)
.env.example # Template without secrets
```
### Step 2: Record Real API Responses as Fixtures
```typescript
// scripts/record-fixtures.ts
import { FirefliesClient } from "../src/lib/fireflies-client";
import { writeFileSync, mkdirSync } from "fs";
async function recordFixtures() {
const client = new FirefliesClient();
mkdirSync("tests/fixtures", { recursive: true });
// Record user
const user = await client.query(`{ user { name email user_id is_admin } }`);
writeFileSync("tests/fixtures/user.json", JSON.stringify(user, null, 2));
// Record transcript list
const list = await client.query(`{
transcripts(limit: 3) {
id title date duration organizer_email
summary { overview action_items keywords }
}
}`);
writeFileSync("tests/fixtures/transcripts.json", JSON.stringify(list, null, 2));
// Record single transcript with sentences
const id = list.transcripts[0]?.id;
if (id) {
const full = await client.query(`
query($id: String!) {
transcript(id: $id) {
id title date duration
speakers { id name }
sentences { speaker_name text start_time end_time }
summary { overview action_items keywords }
analytics {
sentiments { positive_pct negative_pct neutral_pct }
speakers { name duration word_count }
}
}
}
`, { id });
writeFileSync("tests/fixtures/transcript-full.json", JSON.stringify(full, null, 2));
}
console.log("Fixtures recorded in tests/fixtures/");
}
recordFixtures().catch(console.error);
```
### Step 3: Mock Client for Tests
```typescript
// tests/helpers/mock-fireflies.ts
import { readFileSync } from "fs";
export function createMockClient() {
const fixtures: Record<string, any> = {};
return {
loadFixture(name: string) {
fixtures[name] = JSON.parse(
readFileSync(`tests/fixtures/${name}.json`, "utf-8")
);
},
async query(gql: string, variables?: Record<string, any>) {
// Match query to fixture by operation
if (gql.includes("transcripts(")) return fixtures["transcripts"];
if (gql.includes("transcript(id:")) return fixtures["transcript-full"];
if (gql.includes("user {")) return fixtures["user"];
throw new Error(`No fixture for query: ${gql.slice(0, 50)}`);
},
};
}
```
### Step 4: Write Tests
```typescript
// tests/transcript-service.test.ts
import { describe, it, expect, vi, beforeEach } from "vitest";
import { createMockClient } from "./helpers/mock-fireflies";
describe("Transcript Service", () => {
let mockClient: ReturnType<typeof createMockClient>;
beforeEach(() => {
mockClient = createMockClient();
mockClient.loadFixture("transcripts");
mockClient.loadFixture("transcript-full");
});
it("should list recent transcripts", async () => {
const data = await mockClient.query("{ transcripts(limit: 3) { id title } }");
expect(data.transcripts).toBeDefined();
expect(data.transcripts.length).toBeGreaterThan(0);
});
it("should fetch full transcript with sentences", async () => {
const data = await mockClient.query(
`query($id: String!) { transcript(id: $id) { sentences { text } } }`,
{ id: "test-id" }
);
expect(data.transcript.sentences).toBeDefined();
});
it("should handle API errors gracefully", async () => {
const errorClient = {
query: vi.fn().mockRejectedValue(new Error("Fireflies: auth_failed")),
};
await expect(errorClient.query("{ user { email } }"))
.rejects.toThrow("auth_failed");
});
});
```
### Step 5: Development Scripts
```json
{
"scripts": {
"dev": "tsx watch src/index.ts",
"test": "vitest",
"test:watch": "vitest --watch",
"record-fixtures": "tsx scripts/record-fixtures.ts",
"typecheck": "tsc --noEmit"
}
}
```
### Step 6: Environment Setup
```bash
set -euo pipefail
# Create .env from template
cp .env.example .env.local
# .env.example
echo 'FIREFLIES_API_KEY=your-key-here' > .env.example
# .gitignore additions
echo '.env.local' >> .gitignore
echo 'tests/fixtures/*.json' >> .gitignore
```
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| Fixture not found | Fixtures not recorded | Run `npm run record-fixtures` |
| Auth error in tests | Using real API key in CI | Use mock client, not real API |
| Type mismatch | API schema changed | Re-record fixtures, update types |
| Rate limit during recording | Too many fixture requests | Record once, commit fixtures |
## Output
- Project structure with typed client and service layers
- Recorded API fixtures for offline testing
- Mock client for unit tests
- Dev scripts with hot reload and watch mode
## Resources
- [Vitest Documentation](https://vitest.dev/)
- [Fireflies API Docs](https://docs.fireflies.ai/)
## Next Steps
See `fireflies-sdk-patterns` for production-ready client patterns.Related Skills
workhuman-local-dev-loop
Workhuman local dev loop for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman local dev loop".
wispr-local-dev-loop
Wispr Flow local dev loop for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr local dev loop".
windsurf-local-dev-loop
Configure Windsurf local development workflow with Cascade, Previews, and terminal integration. Use when setting up a development environment, configuring Turbo mode, or establishing a fast iteration cycle with Windsurf AI. Trigger with phrases like "windsurf dev setup", "windsurf local development", "windsurf dev environment", "windsurf workflow", "develop with windsurf".
webflow-local-dev-loop
Configure a Webflow local development workflow with TypeScript, hot reload, mocked API tests, and webhook tunneling via ngrok. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with the Webflow Data API. Trigger with phrases like "webflow dev setup", "webflow local development", "webflow dev environment", "develop with webflow".
vercel-local-dev-loop
Configure Vercel local development with vercel dev, environment variables, and hot reload. Use when setting up a development environment, testing serverless functions locally, or establishing a fast iteration cycle with Vercel. Trigger with phrases like "vercel dev setup", "vercel local development", "vercel dev environment", "develop with vercel locally".
veeva-local-dev-loop
Veeva Vault local dev loop for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva local dev loop".
vastai-local-dev-loop
Configure Vast.ai local development with testing and fast iteration. Use when setting up a development environment, testing instance provisioning, or building a fast iteration cycle for GPU workloads. Trigger with phrases like "vastai dev setup", "vastai local development", "vastai dev environment", "develop with vastai".
twinmind-local-dev-loop
Set up local development workflow with TwinMind API integration. Use when building applications that integrate TwinMind transcription, testing API calls locally, or developing meeting automation tools. Trigger with phrases like "twinmind dev setup", "twinmind local development", "twinmind API testing", "build with twinmind".
together-local-dev-loop
Together AI local dev loop for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together local dev loop".
techsmith-local-dev-loop
TechSmith local dev loop for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith local dev loop".
supabase-local-dev-loop
Configure Supabase local development with the CLI, Docker, and migration workflow. Use when initializing a Supabase project locally, starting the local stack, writing migrations, seeding data, or iterating on schema changes. Trigger with phrases like "supabase local dev", "supabase start", "supabase init", "supabase db reset", "supabase local setup".
stackblitz-local-dev-loop
Configure local development for WebContainer applications with hot reload and testing. Use when building browser-based IDEs, testing WebContainer file operations, or setting up development workflows for WebContainer projects. Trigger: "stackblitz dev setup", "webcontainer local", "test webcontainers locally".