Agent skill
uni-sendgrid
SendGrid transactional email via uni CLI. Use when user wants to send emails, including HTML emails and dynamic templates. Requires SENDGRID_API_KEY and verified sender email.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/uni-sendgrid
SKILL.md
SendGrid (uni)
Send transactional emails from the terminal.
Authentication
uni sendgrid auth SG.xxx -f [email protected] # Set API key
uni sendgrid auth SG.xxx -f [email protected] -n "App" # With from name
uni sendgrid auth --status # Check configuration
uni sendgrid auth --logout # Remove credentials
# Or use environment variables
export SENDGRID_API_KEY="SG.xxx"
export SENDGRID_FROM="[email protected]"
Get API key from: https://app.sendgrid.com/settings/api_keys
Send Email
# Plain text email
uni sendgrid send [email protected] "Subject" "Message body here"
# HTML email
uni sendgrid send [email protected] "Welcome!" --html "<h1>Welcome!</h1><p>Thanks for joining.</p>"
# Multiple recipients
uni sendgrid send "[email protected],[email protected]" "Newsletter" "Content here"
# With CC/BCC
uni sendgrid send [email protected] "Subject" "Body" --cc [email protected]
uni sendgrid send [email protected] "Subject" "Body" --bcc [email protected]
# With dynamic template
uni sendgrid send [email protected] "Welcome" -t d-xxxxx -d '{"name":"John","company":"Acme"}'
Notes
- From email must be a verified sender in SendGrid
- Dynamic templates use handlebars syntax in SendGrid dashboard
- Template IDs start with
d- - Multiple recipients separated by commas
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?