CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-sendgrid-inbound-parse

Receive inbound email via SendGrid Inbound Parse webhook. Covers MX record setup, parsed vs raw mode, handling attachments, and common pitfalls. Use when building email-to-app workflows like support ticket creation or email processing pipelines. Requires a SendGrid API key (SG.-prefix) — not applicable to the Twilio Email API (comms.twilio.com).

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, mostly executable reference with a solid code example and a thorough CANNOT boundary list. Main gaps are the missing signature-verification implementation and the split Security presentation.

Suggestions

Add an executable ECDSA signature-verification code snippet (or a clear reference) to the Signed Inbound Parse section so the recommended security control is actionable, not just described.

Consolidate the Security material into one section instead of splitting it between the inline blockquote in Parsed Mode and the standalone Signed Inbound Parse Webhook section.

De-duplicate the repeated 'All email sent to the configured domain reaches your endpoint' phrasing across the filtering and rate-limiting CANNOT bullets.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no padding about what email/Flask is), but a few CANNOT bullets repeat 'All email sent to the configured domain reaches your endpoint' and the security blockquote could be trimmed, keeping it just below the fully lean anchor 5.

4 / 5

Actionability

Provides a copy-paste-ready Flask handler and a concrete field table, but the Signed Inbound Parse section recommends ECDSA verification without showing the verification code, leaving a gap versus the fully-executable anchor 5.

4 / 5

Workflow Clarity

Setup is a clear numbered 3-step sequence with a useful subdomain tip; this is a webhook-receiver reference rather than a destructive/batch workflow, so no validation cap applies, though an explicit 'verify MX propagation' checkpoint is absent.

4 / 5

Progressive Disclosure

No bundle files exist and content is well-organized into clearly headed sections with one-level Next Steps links to sibling skills; the Security material is split between an inline callout and a separate section, a minor organization gap below anchor 5.

4 / 5

Total

16

/

20

Passed

Description

87%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, third-person description that concretely states capabilities and gives explicit trigger guidance with a useful disambiguation constraint. Minor specificity gains are possible by replacing the generic 'common pitfalls' phrase with named pitfalls.

DimensionReasoningScore

Specificity

Names the domain ('Receive inbound email via SendGrid Inbound Parse webhook') and several concrete sub-capabilities ('MX record setup, parsed vs raw mode, handling attachments, and common pitfalls'), but 'common pitfalls' is generic, leaving minor coverage gaps versus the comprehensive anchor 5.

4 / 5

Completeness

Clearly answers 'what' (receive inbound email via SendGrid Inbound Parse webhook, covering MX setup/modes/attachments) and explicitly answers 'when' with concrete trigger phrases ('Use when building email-to-app workflows like support ticket creation or email processing pipelines').

5 / 5

Trigger Term Quality

Natural workflow phrases a user would say ('email-to-app workflows', 'support ticket creation', 'email processing pipelines', 'inbound email') give good keyword coverage; a few common synonyms are absent, so it sits below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (SendGrid Inbound Parse) and explicitly disambiguates from a sibling ('not applicable to the Twilio Email API (comms.twilio.com)'), minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
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.