CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

1.86x
Quality

66%

Does it follow best practices?

Impact

97%

1.86x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

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

Quality

Content

64%

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 highly actionable SendGrid automation skill with excellent domain-specific knowledge including pitfalls, parameter quirks, and legacy vs modern API distinctions. Its main weaknesses are significant content duplication (pitfalls repeated in per-workflow sections and consolidated section) and a monolithic structure that would benefit from splitting detailed references into separate files. Workflow clarity is good but could be improved with explicit validation checkpoints for destructive and async operations.

Suggestions

Eliminate duplicated pitfalls by keeping them only in per-workflow sections OR the consolidated section, not both — this would significantly reduce token count.

Add explicit validation/confirmation steps directly in workflow sequences for destructive operations (e.g., 'Step N: Confirm with user before proceeding' for list deletion) and async operations (e.g., 'Step N: Wait 15s, then verify with GET_CONTACTS_BY_EMAILS').

Consider splitting the quick reference table and detailed parameter lists into a separate REFERENCE.md file, keeping SKILL.md focused on workflows and key pitfalls.

DimensionReasoningScore

Conciseness

The skill is quite long (~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 API, and double-underscore notation. The quick reference table also repeats tool names and params already covered. However, the content is domain-specific knowledge Claude wouldn't inherently know, so it's not explaining basic concepts.

2 / 3

Actionability

Provides specific tool names, exact parameter names with double-underscore notation, concrete ID format examples (UUIDs), specific query syntax for filtering, and clear tool sequences for each workflow. The guidance is directly executable through the MCP tools with copy-paste-ready parameter names and values.

3 / 3

Workflow Clarity

Tool sequences are clearly listed with [Required]/[Optional]/[Prerequisite] annotations, which is good. However, for destructive operations like SENDGRID_REMOVE_LIST_AND_OPTIONAL_CONTACTS, the skill only mentions 'require explicit user confirmation' as a pitfall rather than embedding it as a validation checkpoint in the workflow. The async contact operations mention waiting but lack explicit verify-before-proceeding feedback loops in the workflow steps themselves.

2 / 3

Progressive Disclosure

The content is entirely monolithic with no bundle files or references to separate detailed documents. The quick reference table, all pitfalls, all workflows, and all parameter details are inline. For a skill this comprehensive, the detailed parameter lists and pitfalls per workflow could be split into separate reference files, with the main SKILL.md serving as an overview with links.

2 / 3

Total

9

/

12

Passed

Description

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 SendGrid branding. However, it lacks an explicit 'Use when...' clause, which limits its completeness score, 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 SendGrid, managing email lists, or email campaign analytics.'

Include more natural trigger term variations such as 'email campaign', 'mailing list', 'transactional email', 'email delivery', or 'email API' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: sending emails, managing contacts/lists, sender identities, templates, and analytics. Also specifies the tooling 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 '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 most users.

2 / 3

Distinctiveness Conflict Risk

The explicit mention of 'SendGrid' creates a very clear niche that is unlikely to conflict with other email or communication skills. The combination of SendGrid-specific operations and the Composio tooling makes this highly distinctive.

3 / 3

Total

10

/

12

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
davepoon/buildwithclaude
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.