sendgrid-webhooks

Receive and verify SendGrid webhooks. Use when setting up SendGrid webhook handlers, debugging signature verification, or handling email delivery events.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sendgrid-webhooks/SKILL.md

Quality

Content

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

Highly actionable with complete, executable code and a clean event reference, but it over-explains known concepts, lacks an explicit validation workflow with checkpoints, and references a missing examples/ directory. Tightening inline duplication and adding a verification-gate workflow would raise the weaker dimensions.

Suggestions

Add an explicit sequenced workflow for handling a webhook (1. receive raw body, 2. verify signature via the gate, 3. on failure reject with 400, 4. only then parse and process events) with a validation checkpoint, instead of burying it in middleware code.

Move the manual ECDSA verification detail into verification.md and keep only the SDK approach inline (or vice versa) to reduce duplication and tokens; remove concepts Claude already knows.

Either create the examples/ directory with the Express/Next.js/FastAPI implementations or remove the dead [examples/](examples/) link to avoid a broken reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable code and a tight event table, but includes light over-explanation Claude already knows (e.g. spelling out 'ECDSA (Elliptic Curve Digital Signature Algorithm)' and inline comments like 'Decode the base64 signature') that could be trimmed.	4 / 5
Actionability	It provides two complete, copy-paste-ready verification implementations (manual crypto + official SDK), an Express middleware handler, concrete env vars, and an exact CLI command, covering the common cases fully.	5 / 5
Workflow Clarity	The verification handler is shown as code rather than an explicit validate/parse/respond sequence, and lacks an error-recovery or re-validation checkpoint for the signature-verification gate; the destructive/batch validation cap applies since unverified payloads should not be processed.	3 / 5
Progressive Disclosure	Structure is reasonable with clear references to overview.md, setup.md, and verification.md, but the body inlines a large manual-verification code block and event table that overlap with verification.md/overview.md, and it links an [examples/](examples/) directory that does not exist in the bundle.	3 / 5
	Total	15 / 20 Passed

Description

78%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 with concrete actions, an explicit 'Use when' trigger, and a distinct SendGrid-specific niche. The main gap is slightly broader trigger phrasing (synonyms/file extensions) that would lift completeness and trigger-term quality to the top anchor.

Suggestions

Add natural synonyms and concrete trigger phrases to the 'Use when' clause, e.g. '...or when the user mentions SendGrid Event Webhooks, email bounce/delivery events, or X-Twilio-Email-Event-Webhook signature headers'.

Consider naming the specific event categories (bounce, delivered, open, click, spam) in the description so users who mention those events trigger the skill directly.

Dimension	Reasoning	Score
Specificity	The description names concrete actions ('Receive and verify SendGrid webhooks', 'setting up... handlers', 'debugging signature verification', 'handling email delivery events'), giving several specific actions with only minor gaps in coverage rather than a comprehensive list.	4 / 5
Completeness	It clearly states what the skill does ('Receive and verify SendGrid webhooks') and provides an explicit 'Use when setting up... debugging... or handling...' clause; the 'when' could be more specific (e.g., naming concrete trigger phrases) so it sits just below the top anchor.	4 / 5
Trigger Term Quality	It surfaces natural terms users say ('SendGrid webhooks', 'signature verification', 'email delivery events') plus a 'Use when...' clause, but omits common synonyms/extensions like 'Inbound Parse' or event names a user might mention.	4 / 5
Distinctiveness Conflict Risk	'SendGrid webhooks' is a clear, narrow niche with distinct triggers; it is unlikely to fire for other webhook/email skills, matching the clear-niche anchor.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: hookdeck/webhook-skills
Path: skills/sendgrid-webhooks/SKILL.md
Commit: daaf3db

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.