CtrlK
BlogDocsLog inGet started
Tessl Logo

twilio-sendgrid-engagement-quality

Monitor email program health with SendGrid Engagement Quality (SEQ) scores. Covers the SEQ API endpoints, the 5 scoring metrics (engagement recency, open rate, bounce classification, bounce rate, spam rate), eligibility requirements, and interpreting scores for deliverability improvement. Use when diagnosing SendGrid deliverability issues or monitoring sender reputation. Requires a SendGrid API key (SG.-prefix) — not applicable to the Twilio Email API (comms.twilio.com).

69

Quality

83%

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

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, actionable reference for the SEQ API with clear response handling and edge-case guidance. Minor trimming of the Overview and an added subuser code example would round it out.

Suggestions

Tighten the Overview by merging the 'Key insight' line into the opening sentence to remove redundancy.

Add a short runnable example for the subuser scores endpoint to match the actionability of the primary endpoint.

Make the 202 retry guidance explicit (e.g., 'retry after N minutes') so the asynchronous-calibration workflow has a concrete checkpoint.

DimensionReasoningScore

Conciseness

Mostly efficient with well-organized sections and complete code, though the 'Key insight' line and parts of the Overview restate the correlation that the preceding sentence already implies.

4 / 5

Actionability

Provides an executable Python example with real endpoint, headers, params, and 200/202 handling, plus parameter tables; the subuser endpoint lacks a runnable code example, leaving a minor gap.

4 / 5

Workflow Clarity

Clear interpretive flow from eligibility check through API call to response handling (200/202/omitted), with the CANNOT section covering edge cases; not a destructive workflow, so explicit validation checkpoints are not strictly required.

4 / 5

Progressive Disclosure

Single self-contained SKILL.md with clear section headers and no nested references; the inline API-reference block is somewhat long but appropriately placed given no bundle files exist.

4 / 5

Total

16

/

20

Passed

Description

92%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, specific description that clearly states what the skill does, when to use it, and its scope boundaries. Trigger coverage is good though a few natural synonyms could broaden recall.

Suggestions

Add common synonyms such as 'inbox placement' or 'email sender reputation' to the 'Use when' clause to improve trigger recall.

Consider mentioning the score scale (1-5) in the description so users know what 'health' is being measured against.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — monitoring health, covering API endpoints, the 5 named metrics, eligibility, and interpreting scores — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both 'what' (monitors SEQ scores, endpoints, metrics, eligibility, interpretation) and 'when' ('Use when diagnosing SendGrid deliverability issues or monitoring sender reputation') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('diagnosing SendGrid deliverability issues', 'monitoring sender reputation') plus the SEQ acronym, though a few common synonyms (e.g., 'inbox placement', 'email reputation') are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche — explicitly requires an SG.-prefix API key and states it is 'not applicable to the Twilio Email API (comms.twilio.com)' — minimizing overlap with sibling SendGrid skills.

5 / 5

Total

19

/

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.