CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

57

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/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%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a comprehensive and well-organized SendGrid automation skill that provides genuinely useful, non-obvious information about API quirks, parameter formats, and common pitfalls. Its main weaknesses are significant content repetition (pitfalls repeated in workflow sections and consolidated section) and the lack of bundle files to offload reference material like the quick reference table. Adding concrete example tool invocations with actual parameter values would elevate actionability.

Suggestions

Eliminate duplicated pitfall information — keep pitfalls only in the consolidated 'Known Pitfalls' section and reference it from individual workflows instead of repeating the same warnings.

Move the quick reference table and detailed parameter documentation to a separate REFERENCE.md bundle file to reduce the main SKILL.md token footprint.

Add at least one complete example tool invocation per core workflow showing actual parameter values (e.g., a full SENDGRID_CREATE_SINGLE_SEND call with realistic values).

Add an explicit 'Schedule Single Send' step to the campaign workflow sequence, since the pitfall notes that CREATE does not schedule — the actual scheduling tool/step should be part of the numbered sequence.

DimensionReasoningScore

Conciseness

The skill contains a lot of useful, non-obvious information (pitfalls, parameter quirks, async behavior), but there's significant repetition — the same pitfalls (async contacts, send_at behavior, legacy vs marketing API, UUID formats) are repeated across individual workflow sections AND the consolidated 'Known Pitfalls' section. The quick reference table also duplicates information already covered. Some trimming would improve token efficiency without losing value.

3 / 5

Actionability

The skill provides concrete tool names, specific parameter names with double-underscore notation, exact ID format examples, and clear tool sequences for each workflow. However, there are no executable code examples or copy-paste ready tool invocations showing actual parameter values in context — it stays at the level of parameter documentation rather than showing complete example calls.

4 / 5

Workflow Clarity

Each workflow has a clearly numbered tool sequence with prerequisite/optional/required annotations, and the async operations section includes a verification pattern (wait, then check). However, the campaign creation workflow is missing an explicit validation/scheduling step after creation — the pitfall about send_at not scheduling is noted but no explicit 'Schedule the send' step is included in the sequence. The destructive operation (REMOVE_LIST_AND_OPTIONAL_CONTACTS) mentions requiring user confirmation but doesn't formalize it as a validation checkpoint.

4 / 5

Progressive Disclosure

The content is well-structured with clear sections and headers, but it's quite long (~200+ lines) with no bundle files to offload detailed reference material. The quick reference table, detailed pitfalls, and per-workflow parameter documentation could be split into separate reference files. Everything is inlined in a single monolithic SKILL.md, which is appropriate for a standalone file but not ideal for token efficiency.

3 / 5

Total

14

/

20

Passed

Description

70%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 does a good job listing specific SendGrid capabilities and is highly distinctive due to the named integration. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. Adding trigger guidance and a few more natural user phrases would significantly improve selection accuracy.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about sending emails via SendGrid, managing email contacts/lists, setting up marketing campaigns, or checking email delivery analytics.'

Include additional natural trigger terms like 'send emails', 'bulk email', 'mailing list', 'email templates', or 'transactional email' to capture more user query variations.

DimensionReasoningScore

Specificity

Lists several specific actions: marketing campaigns (Single Sends), contact and list management, sender identity setup, and email analytics. These are concrete capabilities, though it could be more granular about what specific operations are supported within each area.

4 / 5

Completeness

The 'what' is clearly described with multiple concrete capabilities, but there is no explicit 'when' clause (e.g., 'Use when...'). The absence of a 'when' clause caps this at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes strong natural keywords like 'SendGrid', 'email delivery', 'marketing campaigns', 'Single Sends', 'contact and list management', 'sender identity', and 'email analytics'. Missing some natural user phrases like 'send emails', 'email templates', 'bulk email', or 'mailing list'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive due to the specific mention of 'SendGrid' and 'Composio's SendGrid toolkit', which clearly identifies this as a specific integration skill. Minimal risk of conflicting with other email or marketing skills.

5 / 5

Total

16

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.