apollo-webhooks-events
Implement Apollo.io webhook and event-driven integrations. Use when receiving Apollo notifications, syncing data on changes, or building event-driven pipelines from Apollo activity. Trigger with phrases like "apollo webhooks", "apollo events", "apollo notifications", "apollo webhook handler", "apollo triggers".
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/apollo-pack/skills/apollo-webhooks-events/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 skill description that clearly identifies its niche (Apollo.io webhooks/events), provides explicit trigger terms, and answers both what and when. The main weakness is that the specific capabilities could be more concrete—listing particular actions like parsing webhook payloads, configuring webhook endpoints, or handling specific Apollo event types would strengthen specificity.
Suggestions
Add more concrete actions such as 'parse webhook payloads', 'configure webhook endpoints', 'handle contact/account update events' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Apollo.io webhook/event-driven integrations) and some actions (receiving notifications, syncing data on changes, building event-driven pipelines), but the actions are somewhat general and not deeply concrete—e.g., it doesn't specify specific webhook types, payload handling, or configuration steps. | 2 / 3 |
Completeness | Clearly answers both 'what' (implement Apollo.io webhook and event-driven integrations) and 'when' (receiving Apollo notifications, syncing data on changes, building event-driven pipelines) with explicit trigger phrases provided. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger phrases like 'apollo webhooks', 'apollo events', 'apollo notifications', 'apollo webhook handler', 'apollo triggers'. These are terms a user would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Apollo.io webhooks and event-driven integrations. The 'apollo' prefix on all trigger terms makes it very unlikely to conflict with generic webhook or event-driven 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 fully executable TypeScript examples covering Apollo's polling-based event integration pattern. Its main weaknesses are the monolithic structure (all code inline rather than split into referenced files) and the lack of explicit validation checkpoints in the workflow for what is essentially a batch polling operation prone to missed changes and duplicates. The error handling table is helpful but reactive rather than integrated into the workflow steps.
Suggestions
Add explicit validation checkpoints within the workflow, e.g., after polling verify no gaps in timestamps, and before task creation check for duplicates — these should be in the step-by-step flow, not just the error table.
Extract the detailed code implementations into separate referenced files (e.g., POLLING.md, STAGES.md) and keep SKILL.md as a concise overview with quick-start examples and navigation links.
Remove unnecessary inline comments that explain obvious intent (e.g., '// Sync to your CRM, database, or notification system') to improve token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary verbosity — comments like '// Sync to your CRM, database, or notification system' and the overview explaining what Apollo lacks are somewhat padded. The code examples are substantial but justified given the complexity; however, some inline comments and console.log statements could be trimmed. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with concrete API endpoints, request payloads, and response handling. The examples are copy-paste ready with real Apollo API paths and proper axios configuration. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (poll → track stages → monitor engagement → create tasks → schedule), but there are no explicit validation checkpoints. For a polling-based system that could miss changes or create duplicates, the skill mentions these issues only in the error handling table rather than building verification into the workflow itself. | 2 / 3 |
Progressive Disclosure | The skill is quite long (~180 lines of code) and could benefit from splitting detailed implementations into separate files. The Resources section provides good external links, and there's a reference to apollo-performance-tuning, but the main body is monolithic with all code inline rather than referenced. | 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
3e83543
- 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.