fireflies-webhooks-events
Implement Fireflies.ai webhook receiver with HMAC signature verification and event processing. Use when setting up webhook endpoints, handling transcript-ready notifications, or building real-time meeting intelligence pipelines. Trigger with phrases like "fireflies webhook", "fireflies events", "fireflies webhook signature", "handle fireflies events", "fireflies notifications".
89
88%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 strong skill description that clearly defines its scope around Fireflies.ai webhook integration with specific technical capabilities. It includes explicit 'Use when' guidance and a comprehensive list of trigger phrases, making it easy for Claude to select appropriately. The description is concise, uses third-person voice, and covers both the what and when thoroughly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Implement webhook receiver', 'HMAC signature verification', 'event processing', 'handling transcript-ready notifications', 'building real-time meeting intelligence pipelines'. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement webhook receiver with HMAC verification and event processing) and 'when' (explicit 'Use when' clause covering webhook endpoints, transcript-ready notifications, and meeting intelligence pipelines, plus explicit trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including 'fireflies webhook', 'fireflies events', 'fireflies webhook signature', 'handle fireflies events', 'fireflies notifications'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with the specific 'Fireflies.ai' domain, HMAC signature verification, and transcript-ready notifications. Very unlikely to conflict with other webhook or meeting-related skills due to the specific product and technical scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with executable code, proper security practices (HMAC verification with timingSafeEqual), and a clear multi-step workflow. Its main weakness is length—the downstream processing stubs and some inline code could be trimmed or referenced externally to improve token efficiency. The error handling table and payload reference are valuable additions.
Suggestions
Trim the placeholder downstream functions (storeTranscript, createTasksFromActionItems, notifyTeam) to brief comments or a single stub, since they're not Fireflies-specific logic.
Consider moving the full GraphQL query and per-upload webhook example to a referenced file to reduce the main skill's token footprint.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary verbosity—the downstream processing stubs (storeTranscript, createTasksFromActionItems, notifyTeam) are placeholder code that adds bulk without real value. The error handling table and output section are useful but could be tighter. Some explanatory comments in code are redundant for Claude. | 2 / 3 |
Actionability | Fully executable TypeScript code with proper imports, HMAC verification using timingSafeEqual, complete GraphQL queries, and a curl test command. The code is copy-paste ready with real API endpoints, headers, and payload structures. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence from dashboard registration through building the receiver, processing transcripts, alternative per-upload webhooks, and testing. Includes validation via signature verification, immediate acknowledgment pattern, error handling table, and async processing best practices. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a reference table, but it's quite long (~170 lines of substantive content) with inline code that could be split into separate files. The GraphQL query and downstream processing stubs could be referenced rather than inlined. The 'Next Steps' reference to fireflies-deploy-integration is good but the main content is monolithic. | 2 / 3 |
Total | 10 / 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.