CtrlK
BlogDocsLog inGet started
Tessl Logo

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

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

An actionable, concise, well-structured code skill with executable examples and clear sequencing. Its main gap is the absence of an explicit validation checkpoint within the batch fixture-recording workflow.

Suggestions

Add an explicit verify-then-proceed checkpoint after recording fixtures (e.g., 'Run npm run typecheck && npm test; only commit fixtures once tests pass') to support the batch API-recording operation.

Insert a brief feedback loop in Step 2 instructing Claude to re-record or update types if a query fails, converting the reactive Error Handling table into an inline validate-fix-retry step.

Note the fixture-recording batch operation's rate-limit risk inline at Step 2 rather than only in the Error Handling table, so the constraint is visible at the point of action.

DimensionReasoningScore

Conciseness

Code-first and lean throughout; one-line step intros followed by complete code with no padding explaining GraphQL, Vitest, or basic concepts. Every token largely earns its place.

3 / 3

Actionability

Provides fully executable TypeScript (record-fixtures.ts, mock-fireflies.ts, tests), concrete package.json scripts, and a complete bash env-setup block — all copy-paste ready and complete.

3 / 3

Workflow Clarity

Steps 1-6 are clearly sequenced and there is an Error Handling table, but the workflow involves batch recording against the live API with no explicit verify-then-proceed checkpoint in the sequence; per the rubric this caps workflow clarity at 2. It is above the score-1 anchor because the sequence and reactive error guidance are present.

2 / 3

Progressive Disclosure

No bundle files are present, so content lives in a single well-organized SKILL.md with clear sections (Overview, Prerequisites, Steps, Error Handling, Output, Resources, Next Steps) and one-level-deep signaled references to sibling skills (fireflies-install-auth, fireflies-sdk-patterns).

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, specific description that clearly states capabilities, natural trigger terms, and when to use the skill. It is concise without fluff and occupies a distinct niche.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Configure local development workflow for Fireflies.ai GraphQL integrations", "setting up a development environment, mocking transcript data", "fast iteration cycle with the Fireflies API") rather than vague language, matching the highest anchor.

3 / 3

Completeness

Explicitly answers both what (configure dev workflow, mock transcript data, fast iteration cycle) and when ("Use when setting up a development environment, mocking transcript data"), with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides natural phrasings a user would actually say ("fireflies dev setup", "fireflies local development", "fireflies dev environment", "develop with fireflies", "mock fireflies") with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

Clearly niched to Fireflies.ai GraphQL integrations with Fireflies-specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.