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
—
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 identifies a specific niche (Fireflies.ai webhook integration), lists concrete actions, provides explicit 'Use when' guidance, and includes well-chosen trigger phrases. It uses proper third-person voice throughout and is concise without being vague. The description would effectively differentiate this skill from other webhook or meeting-related skills.
| 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 | Includes excellent natural trigger terms that users would actually say: 'fireflies webhook', 'fireflies events', 'fireflies webhook signature', 'handle fireflies events', 'fireflies notifications'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Fireflies.ai-specific webhook handling with HMAC signature verification. The 'fireflies' qualifier throughout makes it very unlikely to conflict with generic webhook or other integration skills. | 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 patterns (HMAC verification with timing-safe comparison), and a clear multi-step workflow. Its main weakness is length—the downstream processing stubs and per-upload alternative add bulk that could be offloaded to bundle files. The content demonstrates good domain knowledge of Fireflies.ai's specific constraints (owner-only webhooks, single event type).
Suggestions
Extract the downstream processing stubs (storeTranscript, createTasksFromActionItems, notifyTeam) and the per-upload webhook alternative into a separate EXAMPLES.md bundle file to reduce the main skill's token footprint.
Remove or shorten placeholder function bodies that just console.log—Claude can infer these patterns without scaffolding code.
| 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 teaching anything new. 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 HMAC verification, GraphQL queries, and curl test commands. The code is copy-paste ready with real API endpoints, correct header names (x-hub-signature), and proper patterns like raw body parsing and timingSafeEqual for timing-safe comparison. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence from dashboard registration through testing. Includes explicit validation via signature verification with rejection handling, immediate acknowledgment before async processing, and error recovery patterns. The workflow has a proper feedback loop with the error handling table addressing common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a reference table, but it's quite long (~180 lines of substantive content) with no bundle files to offload detail into. The GraphQL query, downstream processing stubs, and per-upload alternative could be split into separate reference files. The 'Next Steps' reference to 'fireflies-deploy-integration' is unresolvable with no bundle. | 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 | |
a04d1a2
Table of Contents
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.