CtrlK
BlogDocsLog inGet started
Tessl Logo

instantly-webhooks-events

Implement Instantly.ai webhook event handling with real API v2 event types. Use when setting up webhook endpoints, processing email events, or building CRM sync pipelines from Instantly notifications. Trigger with phrases like "instantly webhook", "instantly events", "instantly webhook handler", "handle instantly events", "instantly notifications".

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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 and token-efficient with concrete executable code and useful reference tables, but workflow checkpoints for destructive operations and genuine external references are missing.

Suggestions

Add an explicit validation checkpoint after webhook creation (e.g., call POST /webhooks/{id}/test and confirm receipt before relying on the subscription).

Add a verify-before-act step for destructive/state-changing operations — confirm before DELETE /webhooks/{id} and before adding leads to the block list on bounce/unsubscribe.

Replace the unlinked 'Resources' plain-text bullets and the dangling 'instantly-performance-tuning' reference with real linked files, or split the event catalog and handler implementations into one-level-deep reference files.

DimensionReasoningScore

Conciseness

Lean, code-and-table heavy content that assumes Claude's competence; no padding with explanations of webhooks, TypeScript, or basic concepts, and nearly every token is API-specific reference or executable code.

3 / 3

Actionability

Fully executable TypeScript with real endpoints, real event types, concrete handler logic, and specific API endpoint/error tables — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Steps are clearly sequenced (Step 1–4) with secret validation and an error-recovery table, but lacks explicit inline checkpoints (e.g., test-after-create) and destructive operations (webhook deletion, block-list additions) have no verification step, capping it at 2.

2 / 3

Progressive Disclosure

Well-organized into clear sections, but the ~290-line body keeps content that could be split (full event catalog, per-handler implementations) inline, and its references are not real — 'Instantly Webhook API'/'Instantly Webhook Events' are unlinked plain text and 'instantly-performance-tuning' points to a non-existent file.

2 / 3

Total

10

/

12

Passed

Description

100%

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 concise, third-person, and clearly states both capability and trigger conditions with natural keyword coverage. It is a strong, low-conflict skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'setting up webhook endpoints, processing email events, or building CRM sync pipelines from Instantly notifications' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Implement Instantly.ai webhook event handling with real API v2 event types') and when ('Use when setting up webhook endpoints, processing email events...') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Provides natural trigger phrases a user would actually say ('instantly webhook', 'instantly events', 'instantly webhook handler', 'handle instantly events', 'instantly notifications') with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Niche is clearly scoped to Instantly.ai webhooks with 'instantly'-prefixed triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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