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".

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

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.md

Quality

Content

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 executable TypeScript examples covering the full polling-based integration pattern for Apollo.io. Its main weaknesses are the monolithic structure (all code inline with no supporting files) and the lack of explicit validation/verification steps in the workflow, which is important for a data sync system prone to missed changes and duplicates. The content could be tightened by removing explanatory context Claude doesn't need and splitting detailed implementations into bundle files.

Suggestions

Add explicit validation checkpoints in the workflow, e.g., after polling verify the count of processed records matches expectations, and add a deduplication check before task creation.

Split the detailed code implementations (stage-tracker.ts, sequence-monitor.ts, task-creator.ts) into bundle files and keep SKILL.md as a concise overview with references.

Remove the explanatory comparison to Stripe in the overview — Claude doesn't need this context; just state that Apollo uses polling-based sync.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary verbosity — the overview explains what Apollo lacks vs Stripe (Claude would know this from context), and some inline comments are redundant. The code blocks are substantial but mostly justified given the complexity of the polling pattern.	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 sequences → create tasks → schedule), but there are no explicit validation checkpoints or feedback loops. For a polling-based sync system that could miss data or create duplicates, the error handling table mentions these risks but doesn't embed verification steps into the workflow itself.	2 / 3
Progressive Disclosure	The content is well-structured with clear sections, but it's a long monolithic file (~200 lines of code) with no bundle files to offload detail into. The stage tracker, sequence monitor, and task creator could each be separate reference files, with SKILL.md providing a concise overview and links.	2 / 3
	Total	9 / 12 Passed

Description

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 phrases, 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 beyond 'receiving notifications' and 'syncing data'—e.g., 'parse webhook payloads, configure webhook endpoints, handle contact/account update events, verify webhook signatures'.

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 users would say: 'apollo webhooks', 'apollo events', 'apollo notifications', 'apollo webhook handler', 'apollo triggers'. These are realistic and cover common variations a user might use.	3 / 3
Distinctiveness Conflict Risk	Highly specific to Apollo.io webhooks and event-driven integrations, which is a clear niche. The Apollo-specific trigger terms make it very unlikely to conflict with generic webhook or integration skills.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

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

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 00c0702

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.