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 it could benefit from more natural user-facing trigger terms beyond the technical service name.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about SendGrid, email campaigns, transactional emails, or managing email contacts and mailing lists.'

Include more natural trigger term variations such as 'email campaign', 'bulk email', 'email marketing', 'transactional email', or 'mailing list' that users might naturally say.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: sending emails, managing contacts/lists, sender identities, templates, and analytics. Also specifies the mechanism (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 'email campaign', 'mailing list', 'email marketing', 'transactional email', or 'bulk email'. 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' as the platform and 'Rube MCP (Composio)' as the integration mechanism. Unlikely to conflict with generic email skills or other service-specific 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 skill provides comprehensive coverage of SendGrid operations via Rube MCP with good domain-specific knowledge about pitfalls, parameter quirks, and API distinctions. However, it suffers from significant content duplication (pitfalls repeated in workflow sections and consolidated section), lacks executable example invocations, and is overly long for a single SKILL.md file without progressive disclosure to separate reference materials.

Suggestions

Deduplicate pitfalls — keep them only in the per-workflow sections OR the consolidated section, not both, to reduce the document by ~30%

Add at least one complete, copy-paste ready tool invocation example (e.g., a full SENDGRID_CREATE_SINGLE_SEND call with all required params filled in) to improve actionability

Move the Quick Reference table and Known Pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with links

Add explicit validation/retry loops for async operations: e.g., 'Wait 15s → call GET_CONTACTS_BY_EMAILS → if not found, wait and retry up to 3 times'

Dimension	Reasoning	Score
Conciseness	The skill is quite lengthy (~250+ lines) with significant repetition — pitfalls are listed per workflow AND again in a consolidated 'Known Pitfalls' section, duplicating information about async operations, ID formats, legacy APIs, and parameter quirks. The quick reference table also repeats information already covered. However, the content is mostly domain-specific knowledge Claude wouldn't inherently know.	2 / 3
Actionability	Tool sequences are clearly named with specific parameter lists and concrete tool slugs, which is good. However, there are no executable code examples or copy-paste ready tool invocations showing exact JSON payloads. The guidance stays at the level of 'call this tool with these params' without showing a complete example call, making it less immediately actionable.	2 / 3
Workflow Clarity	Multi-step workflows are clearly sequenced with numbered steps and labeled as Required/Optional/Prerequisite, which is helpful. However, validation checkpoints are weak — async operations mention waiting 10-30 seconds but don't provide explicit verify-then-retry loops. The destructive operation (REMOVE_LIST_AND_OPTIONAL_CONTACTS) mentions requiring user confirmation but lacks a structured validation/confirmation step in the workflow.	2 / 3
Progressive Disclosure	The content is organized into logical sections with a table of contents-like structure, but it's essentially a monolithic document with no references to separate files for detailed content. The quick reference table, detailed pitfalls, and all workflow details are inline, making this a very long single file that could benefit from splitting advanced topics (e.g., pitfalls, parameter details) into separate reference files.	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: 7cc63f3

Reviewed: about 4 hours 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.