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".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, mostly executable dev-loop skill with clear sequencing and useful error guidance. Its main gaps are a couple of unshown implementations, a missing explicit validation checkpoint, and inline scripts that could be split into bundled files.

Suggestions

Add an explicit validation step after recording fixtures (e.g. 'Verify tests/fixtures/*.json are non-empty and parse before proceeding') to strengthen workflow clarity.

Provide the referenced FirefliesClient and transcript-service code, or link explicitly to where their implementation lives, so the examples are fully self-contained.

Move the full record-fixtures and mock-client scripts into a bundled scripts/ or references/ directory and reference them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable code with minimal concept explanation, but the 'Output' section recaps what the steps already produce and the error-handling table adds mild padding, keeping it just below a 5.	4 / 5
Actionability	Provides concrete, copy-paste-ready code for fixture recording, a mock client, tests, scripts, and env setup, but the FirefliesClient and transcript-service implementations are referenced rather than shown, leaving minor gaps.	4 / 5
Workflow Clarity	Six steps are clearly sequenced with tests serving as a verification checkpoint and an error-handling table providing feedback loops, but there is no explicit validate-after-record checkpoint before relying on fixtures.	4 / 5
Progressive Disclosure	Sections are well organized with signaled cross-skill references ('See fireflies-sdk-patterns'), but the body inlines full scripts (e.g. record-fixtures.ts) and describes files that are not provided as actual bundle files, leaving minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use when' clause, concrete trigger phrases, and a clear niche. The main weakness is slightly abstract action wording ('fast iteration cycle') and a few missing trigger synonyms.

Suggestions

Replace or sharpen the abstract phrase 'fast iteration cycle' with a concrete action like 'record and replay API responses' to lift specificity toward a 5.

Add one or two more natural trigger variations (e.g. 'fireflies testing', 'fireflies offline dev') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Fireflies.ai GraphQL integrations') and several concrete actions ('setting up a development environment, mocking transcript data...fast iteration cycle'), but 'fast iteration cycle' is somewhat abstract and coverage is not fully comprehensive, so it sits just below a 5.	4 / 5
Completeness	Clearly answers both 'what' (configure local dev workflow, mock transcript data) and 'when' ('Use when setting up a development environment...') with explicit concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Provides good natural trigger phrases ('fireflies dev setup', 'fireflies local development', 'fireflies dev environment', 'develop with fireflies', 'mock fireflies') a user would plausibly say, but a few natural variations (e.g. 'test fireflies', 'fireflies testing') are missing.	4 / 5
Distinctiveness Conflict Risk	Niched specifically to Fireflies.ai GraphQL local development with distinct 'fireflies'-prefixed triggers, giving minimal overlap risk with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/fireflies-pack/skills/fireflies-local-dev-loop/SKILL.md
Commit: 0540a62

Reviewed: 41 minutes ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.