CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

twilio-sendgrid-deliverability-advisor

Diagnostic and advisory skill for email deliverability problems. Use when a developer asks why emails are going to spam, not reaching the inbox, getting blocked, bouncing, or how to improve sender reputation — with or without a specified platform. Covers SendGrid-specific tooling: SPF, DKIM, DMARC, BIMI, IP warmup, list hygiene, bounce/spam rate thresholds, and Engagement Quality Score (SEQ). Do NOT use for Twilio Email (comms.twilio.com / Account SID + Auth Token) — use twilio-email-deliverability-advisor instead. Do NOT use for general email sending questions — use twilio-sendgrid-email-send (SendGrid) or twilio-email-deliverability-advisor instead.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, information-dense advisory body: concrete thresholds, named tools, provider-specific facts, and a clear staged diagnostic workflow with an output template. Its weaknesses are modest: some editorial padding, no post-fix verification loop, and two reference-grade tables inlined in SKILL.md rather than split into a reference file.

Suggestions

Add a closing verification step to the workflow (e.g., 'After 2-4 weeks of consistent sending, re-check SEQ score, bounce rate, and complaint rate; if not recovered, re-run diagnosis') to create a feedback loop.

Move the Inbox Provider Requirements and Blocklist Quick Reference tables into a references/ file (e.g., references/provider-requirements.md), keeping a one-line summary plus pointer in SKILL.md.

Trim editorial asides ('no history = no trust', 'slower is better', 'they permanently damage reputation') to pure directive statements to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, Twilio-specific facts (41-day warmup schedule, June 2025 overflow change, Comcast migration through 2026, Orange's 1,000/day DMARC threshold) and avoids explaining concepts Claude already knows. Not a 5 because of scattered editorial padding ('no history = no trust', 'slower is better — allows you to spot and fix anomalies early', 'they permanently damage reputation') that could be trimmed without losing information.

4 / 5

Actionability

Fully concrete for an instruction-only skill: numeric thresholds (hard bounce <1%/1-2%/>2%, complaint <0.08%), UI paths ('Settings → Sender Authentication'), named diagnostic tools (Google Postmaster Tools, SNDS, JMRP, MXToolbox, Spamhaus), a DMARC policy path (p=none → p=quarantine → p=reject), specific delisting contacts per blocklist, and a copy-paste output-format template. Specific guidance covers the common diagnostic cases.

5 / 5

Workflow Clarity

Clear Step 0-5 sequence with explicit branching (Triage/Audit/Foundation modes), a platform-identification gate with an exact clarifying question, a symptom→cause diagnostic ordering, a foundation checklist, and an enforced output format. Not a 5 because there is no post-recommendation validation loop (e.g., re-check SEQ/bounce metrics after the 2-4 week repair window it cites) — the 'fix behavior before requesting delisting' rule is the only feedback checkpoint.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers and internal cross-signaling ('See Inbox Provider Requirements and Blocklist Quick Reference sections below'), plus outbound skill pointers (twilio-sendgrid-webhooks, twilio-sendgrid-suppressions). Not a 5: the ~240-line body inlines two large lookup tables (Inbox Provider Requirements, Blocklist Quick Reference) that would sit better in a reference file, so the SKILL.md is longer than an overview warrants — though everything inlined is load-bearing for diagnosis.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: explicit what/when, natural trigger phrasing, concrete scope enumeration, and explicit negative boundaries naming the sibling skills to redirect to. The only minor weakness is that the capability verbs are generic ('diagnostic and advisory') while the concrete specifics live in the topic list rather than the action list.

DimensionReasoningScore

Specificity

Names the domain ('email deliverability problems') and a comprehensive, concrete capability surface ('SPF, DKIM, DMARC, BIMI, IP warmup, list hygiene, bounce/spam rate thresholds, and Engagement Quality Score (SEQ)'), but the explicit actions are limited to two generic verbs ('Diagnostic and advisory') — the strength is scope enumeration rather than action listing. Not a 5 because the good-example anchor pattern ('Extract text... fill forms... merge documents...') lists multiple distinct concrete actions, while here only 'diagnose' and 'advise' are stated.

4 / 5

Completeness

Explicitly answers both: what ('Diagnostic and advisory skill for email deliverability problems... Covers SPF, DKIM, DMARC, BIMI, IP warmup, list hygiene...') and when ('Use when a developer asks why emails are going to spam, not reaching the inbox, getting blocked, bouncing, or how to improve sender reputation'). Matches the anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural phrases users would actually say: 'emails are going to spam', 'not reaching the inbox', 'getting blocked', 'bouncing', 'improve sender reputation' — plus the technical vocabulary (SPF, DKIM, DMARC, BIMI, SEQ, IP warmup) with synonyms covered. Fits the anchor 'comprehensive coverage of natural terms including synonyms'.

5 / 5

Distinctiveness Conflict Risk

Two explicit 'Do NOT use' clauses disambiguate the adjacent skills by name ('twilio-email-deliverability-advisor' for Twilio Email, 'twilio-sendgrid-email-send' for general sending), including platform identifiers (comms.twilio.com, Account SID + Auth Token). Clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

openai/plugins

Path

plugins/twilio-developer-kit/skills/twilio-sendgrid-deliverability-advisor/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.