fireflies-reference-architecture
Design meeting intelligence architecture with Fireflies.ai GraphQL API, webhooks, and CRM sync. Use when designing new integrations, planning transcript pipelines, or establishing architecture for meeting analytics platforms. Trigger with phrases like "fireflies architecture", "fireflies design", "fireflies project structure", "meeting intelligence pipeline".
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-reference-architecture/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 solid description with excellent completeness and distinctiveness, clearly specifying both when to use the skill and its unique niche around Fireflies.ai integration architecture. The main weakness is that the capabilities described are somewhat abstract ('design architecture') rather than listing concrete actions the skill enables. The trigger terms are well-chosen and cover natural user language.
Suggestions
Replace the abstract 'design meeting intelligence architecture' with more concrete actions like 'scaffold GraphQL query modules, configure webhook listeners, map transcript data to CRM fields, and structure analytics pipelines'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Fireflies.ai) and some technologies (GraphQL API, webhooks, CRM sync), but the actions are vague — 'design meeting intelligence architecture' is abstract rather than listing concrete actions like 'query transcripts', 'configure webhook endpoints', or 'map CRM fields'. | 2 / 3 |
Completeness | Clearly answers both 'what' (design meeting intelligence architecture with Fireflies.ai GraphQL API, webhooks, CRM sync) and 'when' (explicit 'Use when' clause with triggers for designing integrations, planning transcript pipelines, establishing architecture, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes explicit trigger phrases like 'fireflies architecture', 'fireflies design', 'fireflies project structure', 'meeting intelligence pipeline', plus natural terms like 'transcript pipelines', 'meeting analytics platforms', 'GraphQL API', 'webhooks', and 'CRM sync' — good coverage of terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of Fireflies.ai, GraphQL API, meeting intelligence, and transcript pipelines creates a very specific niche that is 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 reference architecture skill with highly actionable, executable TypeScript code and a clear architectural overview. Its main weaknesses are verbosity (too much inline implementation code that could be summarized or split into bundle files) and missing explicit validation/feedback loops in the processing workflow. The content would benefit from being more concise in the main file with detailed implementations referenced externally.
Suggestions
Move full component implementations into separate bundle files (e.g., services/webhook-processor.ts) and keep only key signatures, GraphQL query shapes, and critical patterns in SKILL.md
Add explicit validation checkpoints in the webhook processing workflow, such as verifying transcript completeness before storage and confirming CRM sync success before marking as processed
Trim the transcript storage and action items code to show only the Fireflies-specific patterns (field mappings, API quirks) rather than generic database upsert and iteration logic
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly well-structured but includes substantial boilerplate code (full TypeScript implementations for storage, action items, analytics) that could be more concise. The architecture diagram and error handling table are efficient, but the code blocks are verbose for what is essentially a reference architecture—many of these patterns (fetch wrappers, upsert logic) are things Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript code for every component: GraphQL client, webhook processor, transcript storage, action item sync, analytics, and audio upload. The GraphQL queries include specific field selections matching the Fireflies API, and the code is copy-paste ready with realistic type definitions. | 3 / 3 |
Workflow Clarity | The architecture diagram clearly shows the event-driven flow (meeting → Fireflies → webhook → processing), and the webhook receiver lists steps (verify signature, ACK 200, queue). However, there are no explicit validation checkpoints or feedback loops for error recovery in the processing pipeline—the error handling table lists issues but doesn't integrate them into the workflow as verification steps. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and a project layout, but it's essentially monolithic—all implementation details are inline rather than split into referenced files. The 'Next Steps' reference to 'fireflies-multi-env-setup' and external resource links are good, but the bulk of the code (6 full component implementations) could benefit from being in separate referenced files with just signatures/summaries in the main SKILL.md. | 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.