CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sendgrid-automation

Automate SendGrid email delivery workflows including marketing campaigns (Single Sends), contact and list management, sender identity setup, and email analytics through Composio's SendGrid toolkit.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/sendgrid-automation/SKILL.md

The canonical home for this skill is sendgrid-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

63%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, high-value reference full of real SendGrid API pitfalls (async behavior, ID formats, double-underscore params, legacy vs Marketing API) with well-sequenced, validated workflows for destructive and batch operations. Its main weaknesses are duplicated pitfall content across sections, no worked example of a complete tool call, and no progressive disclosure — the large API table should be split into a reference file.

Suggestions

Consolidate the duplicated pitfalls: keep each fact in exactly one place (per-workflow Pitfalls or the centralized Known Pitfalls section) and cut the filler 'When to Use' closing line.

Move the 26-row Quick Reference table (and per-tool parameter dictionaries) into a references/ file, leaving SKILL.md as a lean overview with one-level-deep pointers.

Add one complete worked example — the full argument object for SENDGRID_CREATE_SINGLE_SEND — and name the actual Schedule tool slug referenced in the campaign workflow.

DimensionReasoningScore

Conciseness

The body is information-dense with genuinely non-obvious API knowledge and no conceptual padding, but notable redundancy could be tightened: list UUID format, async 202/job_id behavior, the legacy single-recipient tool, the CSV 12-hour limit, and the send_at pitfall each appear twice (per-workflow Pitfalls plus the Known Pitfalls/Common Patterns sections), and the closing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview') is pure filler. Not a 2 because there is no over-explanation of things Claude already knows; not a 4 because the duplication goes beyond minor trimmable instances.

3 / 5

Actionability

Concrete, executable guidance throughout: exact tool slugs, tagged step sequences with [Required]/[Optional]/[Prerequisite], exact parameter names (e.g., 'email__config__suppression__group__id'), real value formats (UUID example, query syntax 'status="delivered"', 'BETWEEN TIMESTAMP'), and limits (30,000 contacts/6MB, limit 1-1000). Not a 5 because there is no worked example of one complete tool call (e.g., a full argument set for SENDGRID_CREATE_SINGLE_SEND) covering the most common case end-to-end.

4 / 5

Workflow Clarity

Sequences are clearly ordered and tagged, and the risky-op validation the rubric demands is present: the irreversible list delete requires explicit user confirmation, async batch contact ops have a wait-then-verify feedback loop ('Wait 10-30 seconds before verifying with GET_CONTACTS_BY_EMAILS', 'Use GET_LIST_CONTACT_COUNT to confirm list growth'), and connection status must be confirmed ACTIVE before workflows. Not a 5 because the flagship campaign workflow references 'the Schedule endpoint separately' without naming the tool and has no post-creation verification step — minor validation gaps matching anchor 4.

4 / 5

Progressive Disclosure

No bundle files exist, so everything lives in one 232-line SKILL.md. Section headers make it navigable, but content that would sit better in a separate file is inlined — most notably the 26-row Quick Reference API table and the per-tool parameter dictionaries — matching anchor 3 ('content that should be separate is inline'). Not a 2 because structure is good, not minimal; not a 4 because there is no file-level disclosure at all for a document of this size.

3 / 5

Total

14

/

20

Passed

Description

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

The description gives a specific, well-branded inventory of what the skill does, but omits any explicit 'when to use' trigger guidance, which both caps completeness and leaves the strong trigger vocabulary without a use-when frame. It is clearly distinct from other skills and avoids vague fluff.

Suggestions

Append a trigger clause such as: 'Use when the user mentions SendGrid, email campaigns, newsletters, mailing lists, sender verification, or email delivery analytics.'

Add a couple of common synonyms (e.g., 'newsletter', 'mailing list', 'unsubscribe/suppression groups') to broaden natural keyword coverage.

Use active verb phrasing (e.g., 'Create and send marketing campaigns', 'Manage contacts and lists') instead of noun phrases to sharpen the action list.

DimensionReasoningScore

Specificity

Lists several specific capability areas — 'marketing campaigns (Single Sends)', 'contact and list management', 'sender identity setup', and 'email analytics' — going beyond naming the domain. Not a 5 because the actions are noun phrases rather than full concrete verbs and coverage has minor gaps (e.g., suppressions, templates, scheduling are absent); not a 3 because more than 1-2 concrete actions are named.

4 / 5

Completeness

Has a clear 'what' (automate SendGrid delivery workflows, campaigns, contacts, senders, analytics) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 2 because the 'what' is explicit and multi-faceted, not vague.

3 / 5

Trigger Term Quality

Contains natural terms users would say: 'SendGrid', 'email', 'marketing campaigns', 'Single Sends', 'contact', 'list', 'sender identity', 'analytics'. Not a 5 because common synonyms like 'newsletter', 'mailing list', 'unsubscribe', or 'email stats' are missing; not a 3 because keyword coverage is good, not partial.

4 / 5

Distinctiveness Conflict Risk

Clear niche: 'SendGrid' plus 'Composio's SendGrid toolkit' is highly specific branding with minimal overlap risk against generic email or other ESP skills. Distinct triggers (Single Sends, sender identity) match anchor 5.

5 / 5

Total

16

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/sendgrid-automation/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.