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?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/apollo-pack/skills/apollo-webhooks-events/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

Highly actionable with complete, executable code and a clear step sequence, but it is held back by an unreferenced bundle file and missing validation checkpoints on mutating operations. The body inlines material that the bundled implementation guide was meant to hold.

Suggestions

Link the existing references/implementation-guide.md from the body (e.g. 'See [implementation-guide.md](references/implementation-guide.md) for full handler code') and move the long inline modules there to reach anchor-3 progressive disclosure.

Add explicit validation checkpoints to the mutating workflow steps (e.g. verify the PUT/PATCH response status and re-fetch the contact to confirm the stage changed before proceeding).

Tighten the scheduler and monitor examples by dropping console.log scaffolding and consolidating the duplicated axios client definition, which is re-implied across modules.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and does not explain concepts Claude already knows, but five full inline TypeScript modules plus console.log scaffolding make it longer than necessary; it could be tightened by moving detail to the bundled reference, so it is not the lean anchor-3 case.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript (axios client, poller, stage tracker, sequence monitor, task creator, cron scheduler) with real endpoints and payloads, matching the anchor-3 executable-example standard.	3 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced and an error-handling table exists, but mutating/batch operations (updateContactStage PUT, createFollowUpTask POST, polling sync) lack explicit validate-then-proceed feedback loops, which caps workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	A 436-line references/implementation-guide.md bundle exists but is never linked from the body, and content that could live in that reference is inlined monolithically; structure is present but the reference is unsignaled and the split is poor, matching anchor 2 rather than the well-signaled anchor 3.	2 / 3
	Total	9 / 12 Passed

Description

90%Weight 40%Scale 1-3

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

A clear, third-person description with explicit 'Use when' triggers and good natural-language trigger coverage. It is slightly held back by repetitive 'event-driven' phrasing that keeps the capability list from being crisply distinct.

Suggestions

Replace one of the repeated 'event-driven' phrases with a distinct concrete action (e.g. 'auto-create follow-up tasks') to sharpen specificity toward anchor 3.

Trim the redundant 'building event-driven pipelines from Apollo activity' clause, which overlaps with 'event-driven integrations' earlier in the same sentence.

Dimension	Reasoning	Score
Specificity	Names the Apollo domain and several actions ('Implement Apollo.io webhook and event-driven integrations', 'receiving Apollo notifications, 'syncing data on changes', 'building event-driven pipelines'), but the 'event-driven' phrasing repeats and overlaps rather than listing crisp distinct concrete actions, so it stops short of anchor 3.	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, or building event-driven pipelines'), with an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	Good coverage of natural phrases a user would say ('apollo webhooks', 'apollo events', 'apollo notifications', 'apollo webhook handler', 'apollo triggers'), matching the anchor-3 example of varied natural terms.	3 / 3
Distinctiveness Conflict Risk	Apollo-specific niche with distinctive triggers ('apollo webhooks', 'apollo webhook handler') unlikely to fire for unrelated skills.	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
Path: plugins/saas-packs/apollo-pack/skills/apollo-webhooks-events/SKILL.md
Commit: 4c47e33

Reviewed: 3 days 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.