sendgrid-automation

Automate SendGrid email operations including sending emails, managing contacts/lists, sender identities, templates, and analytics via Rube MCP (Composio). Always search tools first for current schemas.

1.86x

Quality

58%

Does it follow best practices?

Impact

97%

1.86x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/all-skills/skills/sendgrid-automation/SKILL.md

Quality

Discovery

67%

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 platform. However, it lacks an explicit 'Use when...' clause which would help Claude know exactly when to select this skill, and could benefit from more natural user-facing trigger terms beyond the technical product names.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about SendGrid, sending emails via API, managing email contacts or mailing lists, or email campaign analytics.'

Include more natural trigger term variations such as 'email campaign', 'transactional email', 'mailing list', 'email delivery', or 'email API' to improve matching with user requests.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: sending emails, managing contacts/lists, sender identities, templates, and analytics. Also specifies the tooling (Rube MCP/Composio) and includes a procedural note about searching tools first.	3 / 3
Completeness	Clearly answers 'what does this do' with specific SendGrid operations, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain (SendGrid email operations).	2 / 3
Trigger Term Quality	Includes good keywords like 'SendGrid', 'email', 'contacts', 'lists', 'templates', 'analytics', but misses common user variations like 'send an email', 'email campaign', 'mailing list', 'transactional email', or 'email API'. The term 'Rube MCP (Composio)' is technical jargon unlikely to be used by users.	2 / 3
Distinctiveness Conflict Risk	Very distinct due to the specific mention of 'SendGrid' and 'Rube MCP (Composio)', which clearly carves out a niche. Unlikely to conflict with generic email skills or other API integration skills.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

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

This is a thorough SendGrid automation reference that covers the major workflows comprehensively with specific tool names, parameters, and pitfalls. Its main weaknesses are significant content repetition (pitfalls duplicated across sections), lack of executable examples showing actual tool call payloads, and a monolithic structure that would benefit from splitting into overview + reference files. The workflow sequences are well-organized but lack explicit validation checkpoints for destructive and async operations.

Suggestions

Consolidate pitfalls into a single section and reference it from workflows instead of duplicating (e.g., async behavior, UUID formats, send_at quirk are each stated 2-3 times)

Add at least one concrete tool call example with actual JSON input/output for a core workflow like creating a Single Send campaign

Add explicit validation checkpoints in workflows: e.g., after async contact add, show a verify step before proceeding to campaign creation; before list deletion, show a confirmation gate

Consider splitting the quick reference table and detailed pitfalls into separate bundle files, keeping SKILL.md as a concise overview with workflow sequences

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but quite verbose at ~250+ lines. There's significant repetition—pitfalls are listed both within each workflow section AND again in a consolidated 'Known Pitfalls' section (e.g., async contact operations, UUID formats, send_at behavior are each mentioned 2-3 times). The quick reference table duplicates information already covered in workflow sections. However, it doesn't explain basic concepts Claude already knows, and the content is domain-specific enough to justify its existence.	2 / 3
Actionability	The skill provides specific tool names, parameter names with double-underscore notation, and clear tool sequences. However, there are no executable code examples or copy-paste ready tool invocations showing exact JSON payloads. The guidance is concrete in naming tools and parameters but stops short of showing actual MCP tool call examples with sample inputs/outputs, which would make it fully actionable.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with numbered steps and labeled as [Required], [Optional], [Prerequisite]. However, validation checkpoints are weak—the async contact operations mention waiting 10-30 seconds but don't provide explicit verify-then-proceed feedback loops within the workflow steps themselves. The destructive operation (REMOVE_LIST_AND_OPTIONAL_CONTACTS) mentions requiring user confirmation in pitfalls but doesn't embed it as a workflow checkpoint. The campaign creation workflow doesn't include a validation step before sending.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and headers, but it's monolithic—everything is in a single file with no references to supporting documents. The quick reference table, detailed pitfalls, and common patterns sections could be split into separate files. For a skill this long (~250+ lines), having everything inline reduces scannability. The single external link to Composio docs is helpful but insufficient for progressive disclosure.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: davepoon/buildwithclaude
Commit: d065ead

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.