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".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/fireflies-pack/skills/fireflies-local-dev-loop/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong completeness and distinctiveness. It clearly identifies both what the skill does and when to use it, with explicit trigger phrases. The main area for improvement is adding more specific concrete actions beyond the somewhat general 'configure workflow' and 'mocking transcript data'.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'generate mock GraphQL schemas, configure API authentication, set up local test harnesses for transcript queries'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (Fireflies.ai GraphQL integrations) and some actions (setting up development environment, mocking transcript data, establishing iteration cycle), but the actions are somewhat general and not as concrete as listing specific operations like 'create mock schemas, configure API keys, set up hot-reload'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure local dev workflow for Fireflies.ai GraphQL integrations) and 'when' (explicit 'Use when' clause with triggers, plus a 'Trigger with phrases' section listing specific activation terms). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'fireflies dev setup', 'fireflies local development', 'mock fireflies', plus natural keywords like 'development environment', 'GraphQL', 'Fireflies API', and 'transcript data'. Good coverage of terms a user would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Fireflies.ai local development workflow) with unique trigger terms that are unlikely to conflict with other skills like general GraphQL skills or other API integration skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with complete executable code for setting up a Fireflies.ai local dev workflow. Its main strengths are concrete, copy-paste ready code examples and a logical step sequence. Weaknesses include missing validation checkpoints between steps and a somewhat monolithic structure that could benefit from splitting helper code into bundle files.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Run `npx tsx scripts/record-fixtures.ts` and verify that `tests/fixtures/` contains user.json, transcripts.json, and transcript-full.json before proceeding to Step 3.'
Move the fixture recording script and mock client helper into bundle files (e.g., `scripts/record-fixtures.ts` and `tests/helpers/mock-fireflies.ts`) and reference them from the SKILL.md to improve progressive disclosure.
Trim the 'Output' section which restates what was already demonstrated, and remove the generic 'Resources' links to save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary sections like the 'Output' summary which restates what was already shown, and the 'Resources' section adds little value. The error handling table is useful but some entries are obvious. Overall reasonably lean but could be tightened. | 2 / 3 |
Actionability | Every step provides fully executable, copy-paste ready code: the fixture recording script, mock client, test suite, package.json scripts, and bash setup commands are all concrete and complete. The code is TypeScript with proper imports and realistic GraphQL queries. | 3 / 3 |
Workflow Clarity | The six steps are clearly sequenced and logically ordered (structure → record → mock → test → scripts → env). However, there are no explicit validation checkpoints between steps—e.g., no 'verify fixtures were recorded correctly before proceeding' or 'run tests to confirm mock client works'. For a multi-step setup workflow, validation/verification steps are missing. | 2 / 3 |
Progressive Disclosure | The skill references other skills ('fireflies-install-auth', 'fireflies-sdk-patterns') which is good for navigation, but the body itself is quite long with all code inline. The mock client helper and fixture recording script could reasonably be separate bundle files. With no bundle files provided, all content is monolithic in one file. | 2 / 3 |
Total | 9 / 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.
Validation — 9 / 11 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 |
Total | 9 / 11 Passed | |
- Commit
a04d1a2
- 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.