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.

78

1.86x
Quality

69%

Does it follow best practices?

Impact

97%

1.86x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/sendgrid-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

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

A dense, actionable reference that sequences workflows clearly with appropriate validation for destructive/batch operations. Its main weaknesses are repetition across sections and a monolithic single-file structure that would benefit from splitting into reference files.

Suggestions

De-duplicate repeated facts (async contact 202/job_id, UUID list IDs, double-underscore params) into a single Known Pitfalls section and reference it from workflows.

Move the Quick Reference table and/or per-workflow detail into one-level-deep reference files (e.g. references/quick-reference.md) with clear links from SKILL.md to improve progressive disclosure.

Add at least one fully assembled example tool call (e.g. a complete SENDGRID_CREATE_SINGLE_SEND parameter set) to close the small actionability gap.

DimensionReasoningScore

Conciseness

Mostly efficient and dense, but several facts are repeated across sections (async 202 contact behavior, list-IDs-are-UUIDs, nested double-underscore params appear in workflow pitfalls, Common Patterns, and Known Pitfalls), which could be tightened.

3 / 5

Actionability

Provides concrete tool slugs, required/optional tagging, key parameters with types and constraints, and a copy-paste Quick Reference table; minor gaps include no fully assembled example tool call.

4 / 5

Workflow Clarity

Five workflows each give an explicit numbered tool sequence, prerequisites, 'When to use' triggers, and pitfalls, with validation for risky operations (confirm ACTIVE connection before workflows, verify-after-delay for async contacts, explicit confirmation for irreversible list deletion).

4 / 5

Progressive Disclosure

Well-organized sections, but at ~225 lines of dense reference with no bundle files, substantial material (the Quick Reference table, Known Pitfalls, per-workflow detail) is inlined that would read better as one-level-deep reference files.

3 / 5

Total

14

/

20

Passed

Description

75%Weight 40%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.

A specific, distinctive description with comprehensive capability coverage, weakened only by the absence of an explicit 'Use when...' trigger clause and a few missing synonyms. Adding a use-when clause would lift the completeness score.

Suggestions

Add an explicit 'Use when...' clause naming the natural triggers (e.g. 'Use when sending SendGrid marketing campaigns or managing contacts, lists, sender identities, or email analytics').

Include common synonyms users say, such as 'campaigns', 'Single Sends', and 'suppressions/unsubscribes', alongside the current capability list.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'sending emails, managing contacts/lists, sender identities, templates, and analytics' — giving comprehensive coverage of the SendGrid domain.

5 / 5

Completeness

Has a clear, enumerated 'what' but no explicit 'when'/'Use when...' trigger clause; the closing 'Always search tools first' is procedural guidance, not a use-when trigger, so completeness is capped at 3 per the rubric.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('send emails', 'contacts/lists', 'templates', 'analytics') but omits common synonyms like 'campaigns' or 'Single Sends' that this skill actually handles.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (SendGrid email operations via Rube MCP/Composio) with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.