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".
80
77%
Does it follow best practices?
Impact
Pending
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-crafted skill description that clearly identifies its niche (Fireflies.ai local development), provides explicit trigger phrases, and answers both what and when. The main weakness is that the specific capabilities could be more concrete — listing actual actions like configuring API keys, creating mock servers, or scaffolding project files would strengthen the specificity dimension.
Suggestions
Add more concrete action verbs describing specific capabilities, e.g., 'scaffold project structure, configure GraphQL client, create mock transcript responses, set up hot-reload development server'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Fireflies.ai GraphQL integrations) and some actions (setting up dev environment, mocking transcript data, establishing iteration cycle), but the actions are somewhat general and not as concrete as listing specific steps like 'create mock server, configure API keys, scaffold project structure'. | 2 / 3 |
Completeness | Clearly answers both 'what' (configure local dev workflow for Fireflies.ai GraphQL integrations) and 'when' (setting up dev environment, mocking transcript data, establishing fast iteration cycle) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases that users would naturally say: 'fireflies dev setup', 'fireflies local development', 'fireflies dev environment', 'develop with fireflies', 'mock fireflies'. These cover multiple natural variations and are specific to the skill's niche. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Fireflies.ai GraphQL local development). The combination of 'Fireflies.ai', 'GraphQL', and 'local development workflow' makes it extremely unlikely to conflict with other 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 loop. Its main strengths are the concrete, copy-paste-ready code examples and logical step sequencing. Weaknesses include the lack of validation checkpoints between steps and the monolithic structure that could benefit from better progressive disclosure.
Suggestions
Add explicit validation checkpoints after key steps, e.g., 'Verify fixtures exist: ls tests/fixtures/*.json should show 3 files' after Step 2, and 'Run vitest to confirm tests pass' after Step 4.
Consider extracting the longer code blocks (fixture recorder, mock client) into referenced files and keeping only usage summaries inline to improve progressive disclosure and reduce document length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some unnecessary sections like the 'Output' summary which restates what was already built, and the 'Resources' section adds minimal value. The code examples are thorough but could be slightly tighter. | 2 / 3 |
Actionability | Fully executable TypeScript code throughout — the fixture recorder, mock client, test suite, package.json scripts, and environment setup are all copy-paste ready with specific commands and complete implementations. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-6) and logically ordered, but there are no explicit validation checkpoints between steps. For example, there's no verification that fixtures were recorded correctly before proceeding to write tests, and no feedback loop for when the record-fixtures script fails or produces unexpected output. | 2 / 3 |
Progressive Disclosure | References to `fireflies-install-auth` and `fireflies-sdk-patterns` provide some cross-referencing, but the skill itself is a long monolithic document with ~150 lines of inline code that could benefit from splitting the fixture recorder and mock client into referenced files rather than embedding everything. | 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
c8a915c
- 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.