integration-webhooks

Cross-platform pattern for handling messaging integration webhooks (Slack, Telegram, WhatsApp, email, etc.) on serverless hosts. Use when adding a new integration adapter, debugging dropped messages, or wiring long-running agent work into a webhook handler.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%Weight 40%Scale 1-5

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

The body is a dense, actionable engineering reference with full code, schema, routes, and a well-sequenced flow plus debugging checklist with validation feedback loops. Its main weakness is mild verbosity from overlapping 'Why' sections and a long single-file layout that could split some reference material out.

Suggestions

Consolidate the 'Why' and 'Why Fire-and-Forget on Serverless Is Unreliable' sections to remove overlapping explanations of the freeze-on-return failure mode.

Consider moving the Netlify durable recovery detail and SQL schema into separate reference files referenced one level deep from SKILL.md to improve progressive disclosure.

Tighten the Netlify recovery paragraph cluster; the lease-cutoff and telemetry details repeat the atomic-claim rationale already covered earlier.

Dimension	Reasoning	Score
Conciseness	Dense engineering specifics that assume Claude's competence (no generic explanations of SQL, webhooks, or HMAC), but the 'Why' and 'Why Fire-and-Forget on Serverless Is Unreliable' sections overlap and the Netlify recovery section is lengthy.	4 / 5
Actionability	Fully executable guidance: complete SQL DDL, a copy-paste-ready TypeScript adapter template, concrete file paths and routes, explicit env vars, and runnable debugging queries covering the common cases.	5 / 5
Workflow Clarity	The Flow is a clear numbered 1–9 sequence with an explicit recovery sweep, the adapter walkthrough is a 1–4 sequence, and the debugging checklist provides status-based checkpoints with a retry feedback loop (3 attempts → 'failed').	5 / 5
Progressive Disclosure	Well-organized single-file structure with clearly signaled one-level skill pointers and no nested references, but at ~350 lines some bulk (SQL schema, Netlify recovery, automation connectors) is inline rather than split into separate files.	4 / 5
	Total	18 / 20 Passed

Description

88%Weight 40%Scale 1-5

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 strong and specific, naming a clear domain with multiple concrete actions and explicit 'Use when...' trigger guidance covering three scenarios. It is just short of a perfect score on trigger-term breadth and has minor overlap risk with adjacent infrastructure skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions for a named domain — 'handling messaging integration webhooks', 'adding a new integration adapter', 'debugging dropped messages', 'wiring long-running agent work into a webhook handler' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('Cross-platform pattern for handling messaging integration webhooks on serverless hosts') and when ('Use when adding a new integration adapter, debugging dropped messages, or wiring long-running agent work') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keyword coverage (webhook, integration adapter, Slack, Telegram, WhatsApp, dropped messages, serverless) but a few natural synonyms (bot, event handler) are missing, placing it just below exhaustive.	4 / 5
Distinctiveness Conflict Risk	Clear niche with distinct platform/webhook triggers, but minor overlap risk with closely related skills (server-plugins, recurring-jobs, actions) noted in the Related Skills section.	4 / 5
	Total	18 / 20 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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/integration-webhooks/SKILL.md
Commit: b0df876

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.