apollo-webhooks-events
Implement Apollo.io webhook handling. Use when receiving Apollo webhooks, processing event notifications, or building event-driven integrations. Trigger with phrases like "apollo webhooks", "apollo events", "apollo notifications", "apollo webhook handler", "apollo triggers".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill apollo-webhooks-events88
Quality
83%
Does it follow best practices?
Impact
100%
1.63xAverage score across 3 eval scenarios
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 excellent trigger term coverage and clear 'what/when' guidance. The main weakness is the lack of specific concrete actions - it describes the general domain but doesn't enumerate the specific webhook types or operations it handles (e.g., contact created, sequence completed, etc.).
Suggestions
Add specific concrete actions like 'validate webhook signatures, process contact/account updates, handle sequence completion events' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io webhooks) and some actions ('webhook handling', 'processing event notifications', 'building event-driven integrations'), but lacks specific concrete actions like 'validate webhook signatures', 'parse contact updates', or 'handle sequence events'. | 2 / 3 |
Completeness | Clearly answers both what ('Implement Apollo.io webhook handling') and when ('Use when receiving Apollo webhooks, processing event notifications, or building event-driven integrations') with explicit trigger guidance including a 'Trigger with phrases' clause. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases users would say: 'apollo webhooks', 'apollo events', 'apollo notifications', 'apollo webhook handler', 'apollo triggers'. Good coverage of variations a user might naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Apollo.io webhooks with distinct triggers. The 'apollo' prefix on all trigger terms makes it unlikely to conflict with generic webhook skills or other CRM integrations. | 3 / 3 |
Total | 11 / 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 complete, executable code for Apollo webhook handling. The workflow is clear with proper validation checkpoints (signature verification, error handling). Main weakness is length - the comprehensive code examples could be split into referenced files to improve token efficiency.
Suggestions
Consider moving the detailed event handlers (handleContactEvent, handleSequenceEvent, handleEmailEvent) to a separate HANDLERS.md reference file to reduce main skill length
Remove the event table since the same information is captured in the Zod schemas - this eliminates redundancy
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - the event table duplicates information found in the schemas, and some code comments explain obvious behavior. However, it largely avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully executable TypeScript code with complete implementations for webhook handlers, signature verification, event processing, and testing. All code is copy-paste ready with proper imports and type definitions. | 3 / 3 |
Workflow Clarity | Clear multi-step workflow for webhook implementation: handler setup → signature verification → event routing → database sync. Includes explicit validation (signature verification middleware), error handling table, and testing workflow with ngrok instructions. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill is quite long (~300 lines) and could benefit from splitting detailed handler implementations or test code into separate reference files. The 'Next Steps' reference to another skill is good, but inline content is heavy. | 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 | |
- 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.