CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/integration-webhooks/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, highly actionable internal skill: every section carries project-specific knowledge with executable code, exact paths, and a concrete debugging checklist. Its weaknesses are repetition of the core enqueue-then-dispatch rule across four sections and a monolithic single-file layout where the SQL schema, Netlify specifics, and channel-settings rules could be split into reference files.

Suggestions

Consolidate the recurring statement of the core rule ('enqueue to SQL, return 200, process in a fresh execution, sweep for recovery') so it is stated fully once in 'Rule' and only referenced from 'Why', 'Cross-Platform Considerations', and 'Why Fire-and-Forget on Serverless Is Unreliable'.

Move the `integration_pending_tasks` SQL DDL and the Netlify durable-dispatch rollout details (flags, scopes, lease cutoffs) into a references/ file (e.g. references/pending-tasks-schema.md and references/durable-dispatch.md), keeping only the claim semantics and default behavior in SKILL.md.

Add an explicit verify step to 'Adding a New Platform Adapter' (e.g. 'run the catalog and adapter tests, then send a signed test webhook and confirm the task row reaches completed') so the sequence has a validation checkpoint like the debugging checklist already does.

DimensionReasoningScore

Conciseness

Mostly project-specific, non-obvious knowledge (host freeze behavior, atomic claims, retry cutoffs) that earns its tokens, but the core 'persist, then self-fire, with a recovery sweep' rule is restated across 'Rule', 'Why', 'Cross-Platform Considerations', and 'Why Fire-and-Forget on Serverless Is Unreliable', and the 'Netlify durable recovery' subsection repeats lease/cutoff details twice. This is more than anchor 4's 'minor instances of over-explanation' — several sections could be consolidated — but it is not the padding of anchors 1-2.

3 / 5

Actionability

Fully executable guidance throughout: a complete `PlatformAdapter` TypeScript template with all required methods, the exact `integration_pending_tasks` SQL DDL, real file paths (`packages/core/src/integrations/webhook-handler.ts`), concrete env vars (`AGENT_INTEGRATION_DURABLE_DISPATCH`, `WEBHOOK_BASE_URL`), a copy-paste debug query (`SELECT * FROM integration_pending_tasks WHERE external_thread_id = '...'`), and named functions (`claimPendingTask`, `setMountedChannels`). Matches anchor 5's copy-paste-ready coverage of common cases.

5 / 5

Workflow Clarity

The main flow is a numbered 9-step diagram with a recovery sweep, and 'Adding a New Platform Adapter' is a clear 4-step sequence with a built-in validation gate ('catalog.spec.ts fails until the catalog and BUILT_IN_INTEGRATION_ADAPTER_IDS match') plus a 6-item debugging checklist with error-recovery guidance. It falls short of anchor 5 because the adapter-creation steps themselves lack an explicit verify/test checkpoint after registration, and the checklist is diagnostic rather than a validate→fix→retry loop inside the workflow.

4 / 5

Progressive Disclosure

Section headers, tables, and a 'Related Skills' list give the 390-line body real structure, but everything lives in one file: the SQL schema, the Netlify durable-dispatch rollout details, and the Settings › Channels rules are each substantial enough to be separate reference files, and no bundle files (references/, scripts/, assets/) exist to offload them. This matches anchor 3's 'content that should be separate is inline' with decent organization, not anchor 2's structureless inline dump.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description: third-person, concrete, and with an explicit 'Use when...' clause covering three realistic triggers. Platform names provide natural trigger terms, and the niche is well-differentiated. Only minor gaps in action coverage and synonym breadth keep it from full marks.

DimensionReasoningScore

Specificity

Names the domain ('messaging integration webhooks (Slack, Telegram, WhatsApp, email, etc.) on serverless hosts') and several concrete scenarios — 'adding a new integration adapter', 'debugging dropped messages', 'wiring long-running agent work into a webhook handler'. It falls short of anchor 5 because 'Cross-platform pattern for handling...' is more scenario-shaped than a comprehensive list of concrete actions, but it is well above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Explicitly answers both questions: the 'what' ('Cross-platform pattern for handling messaging integration webhooks ... on serverless hosts') and an explicit 'Use when...' clause with three concrete triggers. Third person throughout. Anchor 4 ('when could be more explicit') does not apply — the when-clause is fully explicit, matching anchor 5.

5 / 5

Trigger Term Quality

Good natural keyword coverage: users would literally say 'Slack', 'Telegram', 'WhatsApp', 'webhook', 'integration', 'dropped messages', 'serverless'. A few natural variations are missing ('bot', 'channel', 'callback', 'messaging platform'), so it does not reach anchor 5's comprehensive synonym coverage, but it clearly exceeds anchor 3's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (messaging-platform webhooks on serverless hosts) with distinct triggers like 'adding a new integration adapter' and 'debugging dropped messages'. Minor overlap risk remains with generic webhook-handling or agent-delegation skills via the phrases 'webhook handler' and 'long-running agent work', keeping it just below anchor 5's 'minimal conflict risk'.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

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.