fireflies-local-dev-loop
Best practices for local development cycles, including mocking and testing Fireflies.ai GraphQL interactions.
Install
mkdir -p .claude/skills/fireflies-local-dev-loop && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9124" && unzip -o skill.zip -d .claude/skills/fireflies-local-dev-loop && rm skill.zipInstalls to .claude/skills/fireflies-local-dev-loop
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Configure local development workflow for Fireflies.ai GraphQL integrations.Key capabilities
- →Establish project structure for Fireflies.ai integrations
- →Record real API responses as JSON fixtures
- →Create mock clients for offline unit testing
- →Configure hot-reload development scripts
- →Manage environment variables with templates
How it works
The skill establishes a local development loop by recording real API responses into JSON files and using a mock client to serve these files during unit tests. This allows developers to iterate on business logic without making live network requests.
Inputs & outputs
When to use fireflies-local-dev-loop
- →Setting up a development environment
- →Mocking meeting transcript data
- →Configuring test workflows
About this skill
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-authsetup - 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
// 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
// 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
// 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
{
"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
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
Next Steps
See fireflies-sdk-patterns for production-ready client patterns.
When not to use it
- →Production environments requiring real-time data
- →Systems lacking Vitest for test execution
Prerequisites
Limitations
- →Requires manual re-recording of fixtures if the API schema changes
- →Not suitable for testing real-time API connectivity in CI
How it compares
Unlike manual testing against live endpoints, this approach uses recorded fixtures to ensure consistent, offline-capable test cycles.
Compared to similar skills
fireflies-local-dev-loop side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| fireflies-local-dev-loop (this skill) | 0 | 27d | Review | Intermediate |
| telegram-bot-builder | 106 | 6mo | Review | Intermediate |
| playwright-browser-automation | 29 | 7mo | Review | Intermediate |
| n8n-expression-syntax | 6 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.
playwright-browser-automation
lackeyjb
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
reddit-api
alinaqi
Reddit API with PRAW (Python) and Snoowrap (Node.js)
mcporter
openclaw
Use the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
calcom-api
calcom
Interact with the Cal.com API v2 to manage scheduling, bookings, event types, availability, and calendars. Use this skill when building integrations that need to create or manage bookings, check availability, configure event types, or sync calendars with Cal.com's scheduling infrastructure.