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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill sendgrid-automation70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
50%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 excels at listing specific SendGrid capabilities and is highly distinctive due to platform-specific naming. However, it critically lacks explicit trigger guidance ('Use when...'), which would help Claude know when to select this skill over others. The operational instruction about searching tools first doesn't compensate for missing usage triggers.
Suggestions
Add a 'Use when...' clause with trigger terms like 'SendGrid', 'email automation', 'email marketing', 'mailing list management', or 'transactional emails'.
Include common user phrases that would indicate need for this skill, such as 'send bulk emails', 'manage email subscribers', or 'email campaign analytics'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'sending emails, managing contacts/lists, sender identities, templates, and analytics.' These are clear, actionable capabilities within the SendGrid domain. | 3 / 3 |
Completeness | Describes what the skill does well, but completely lacks a 'Use when...' clause or any explicit trigger guidance. The instruction 'Always search tools first' is operational guidance, not usage triggers. | 1 / 3 |
Trigger Term Quality | Includes good keywords like 'SendGrid', 'email', 'contacts', 'templates', and 'analytics', but missing common variations users might say like 'email marketing', 'mailing lists', 'email campaigns', or 'bulk email'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct due to explicit 'SendGrid' branding and 'Rube MCP (Composio)' reference. Unlikely to conflict with generic email skills or other integrations. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable and well-structured skill for SendGrid automation with excellent workflow clarity, explicit validation checkpoints, and comprehensive tool coverage. The main weaknesses are moderate verbosity from repeated pitfall documentation and a monolithic structure that could benefit from progressive disclosure across multiple files. The content successfully teaches Claude exactly how to execute SendGrid operations with specific tool names, parameters, and common gotchas.
Suggestions
Consolidate pitfalls into a single section or inline only the most critical ones per workflow, removing the separate 'Known Pitfalls' section to reduce redundancy
Split detailed workflow sections (Campaigns, Contacts, Senders, Statistics) into separate reference files, keeping SKILL.md as a concise overview with links
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy - pitfalls are repeated across sections and in a dedicated 'Known Pitfalls' section. The quick reference table duplicates information already covered in workflows. Could be tightened by consolidating pitfalls and removing duplicate parameter documentation. | 2 / 3 |
Actionability | Excellent actionability with specific tool names, exact parameter names with double-underscore notation, concrete examples of ID formats, and clear tool sequences for each workflow. The quick reference table provides copy-paste ready tool slugs and key parameters. | 3 / 3 |
Workflow Clarity | Clear numbered sequences with [Required], [Optional], and [Prerequisite] annotations. Includes explicit validation steps (verify connection ACTIVE, wait 10-30 seconds for async operations, use GET_LIST_CONTACT_COUNT to confirm). Async operations have clear feedback loops with job_id handling. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single monolithic file. The 300+ line document could benefit from splitting detailed workflow sections into separate files, with SKILL.md serving as an overview pointing to CAMPAIGNS.md, CONTACTS.md, etc. | 2 / 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.
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 | |
- 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.