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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable TypeScript and a clear step sequence, but it is over-inlined: the existing implementation-guide.md reference is orphaned (never linked) and the batch-sync workflow lacks validation checkpoints. Notably, the body states Apollo has no native webhooks while the reference file assumes native webhook payloads, a factual inconsistency to reconcile.

Suggestions

Link the bundled reference from the body (e.g., 'See references/implementation-guide.md for the full Express webhook handler, event schemas, and tests') so progressive disclosure is actually signaled.

Add an inline validation/verification checkpoint to the sync workflow — e.g., verify the polled page was fully processed and update lastSyncAt only on success, with a dedup check before creating tasks — to earn workflow_clarity 3.

Reconcile the factual contradiction: the body says Apollo lacks native webhooks (polling/third-party only), but references/implementation-guide.md implements native Apollo webhook handlers with HMAC signatures and event payloads.

Dimension	Reasoning	Score
Conciseness	Prose is lean and the Overview conveys genuinely non-obvious domain knowledge (Apollo lacks native webhooks), but the ~230-line body bundles five full TypeScript implementations inline with some redundancy across snippets, so it could be tightened to earn a 3.	2 / 3
Actionability	Provides fully-typed, concrete, copy-paste-ready TypeScript for polling, stage tracking, sequence monitoring, task creation, and a cron scheduler — real executable code rather than pseudocode, matching the score-3 anchor.	3 / 3
Workflow Clarity	Steps 1–5 are clearly sequenced and an Error Handling table exists, but the batch sync workflow has no inline validation/verification checkpoints or validate-fix-retry feedback loops; per the rubric this caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The body is sectioned, but a bundle file (references/implementation-guide.md) exists and is never linked or signaled from SKILL.md, and full implementations are inlined that could live in that reference — matching 'references present but not clearly signaled; content that should be separate is inline'.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is well-constructed with explicit what/when guidance and natural, distinct Apollo-specific trigger phrases. Its only weakness is that the stated capabilities are somewhat abstract rather than listing concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Apollo.io webhook and event-driven integrations') and three actions ('receiving Apollo notifications, syncing data on changes, building event-driven pipelines'), but the actions are high-level rather than concrete operations like 'extract text, fill forms, merge documents', matching the score-2 anchor rather than the comprehensive score-3 example.	2 / 3
Completeness	Explicitly answers both what ('Implement Apollo.io webhook and event-driven integrations') and when ('Use when receiving Apollo notifications, syncing data on changes...') with an explicit 'Trigger with phrases like' clause, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would actually say — 'apollo webhooks', 'apollo events', 'apollo notifications', 'apollo webhook handler', 'apollo triggers' — giving good coverage of common variations, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Targets a clear Apollo.io-specific niche with Apollo-scoped triggers ('apollo webhooks', 'apollo events'), making it unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 02d6341

Reviewed: 1 day 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.