S

sales-automator

Verified

by sickn33 · Updated Apr 16, 2026

opus
166in4.1Kout
$0.251m 35s

Draft cold emails, follow-ups, and proposal templates. Creates

salesoutreachemailtemplatescopywritinglead-nurturing

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. need outreach for yesterday's webinar leads asap — 4-touch emails for ops folks at mid-market SaaS who attended but didn't book, SDRs need it this afternoon

Let me explore the codebase first, then draft the sequence.

Got everything I need. Let me build this out.

Done. The full sequence is at outreach/webinar-followup-sequence.md. Here's the rundown:

4-Touch Cadence:

TouchDateAngleCTA
1Today (Apr 12)Warm webinar callbackBook demo
2Apr 15 (Wed)Meridian case study + ROI frameworkBook demo
3Apr 20 (Mon)BrightPath case study + soft offerDemo or 2-min video
4Apr 30 (Thu)Breakup — "not now" or "show me"Binary reply

What's included:

  • A/B subject lines for every touch (all under 50 chars, lowercase, no spam triggers)
  • Two variants for Touch 1 — one for Segment A leads (asked a question, references their specific Q) and one for Segment B (references poll stats)
  • Personalization variables mapped to CRM/webinar platform fields
  • All three proof points woven in: TechFlow (Touch 1), Meridian (Touch 2), BrightPath (Touch 3)
  • Objection handling scripts for the 4 most common replies
  • Priority lead list — 6 Segment A leads flagged for SDRs to watch closest
  • Rachel Goldstein excluded (she's the co-presenter, not a prospect)
  • KPI targets so SDRs know what good looks like

One flag: Touch 1 lands today (Saturday). The playbook says follow up within 24 hours for 40% higher engagement, but if your team prefers weekday-only sends, shift it to Monday morning and adjust the cadence. That tradeoff is noted in the doc.

Claude Sonnet 4.6

SKILL.md

Use this skill when

  • Working on sales automator tasks or workflows
  • Needing guidance, best practices, or checklists for sales automator

Do not use this skill when

  • The task is unrelated to sales automator
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

You are a sales automation specialist focused on conversions and relationships.

Focus Areas

  • Cold email sequences with personalization
  • Follow-up campaigns and cadences
  • Proposal and quote templates
  • Case studies and social proof
  • Sales scripts and objection handling
  • A/B testing subject lines

Approach

  1. Lead with value, not features
  2. Personalize using research
  3. Keep emails short and scannable
  4. Focus on one clear CTA
  5. Track what converts

Output

  • Email sequence (3-5 touchpoints)
  • Subject lines for A/B testing
  • Personalization variables
  • Follow-up schedule
  • Objection handling scripts
  • Tracking metrics to monitor

Write conversationally. Show empathy for customer problems.

FAQ

What does sales-automator do?

Draft cold emails, follow-ups, and proposal templates. Creates

When should I use sales-automator?

Use it when you need a repeatable workflow that produces text report.

What does sales-automator output?

In the evaluated run it produced text report.

How do I install or invoke sales-automator?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does sales-automator support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does sales-automator need?

It uses no extra tools; channels commonly include text; permissions include no explicit permission scopes.

Is sales-automator safe to install?

Static analysis marked this skill as low risk; review side effects and permissions before enabling it.

How is sales-automator different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does sales-automator outperform not using a skill?

About sales-automator

When to use sales-automator

You need to create a cold email or follow-up sequence for prospects. You want proposal, case study, or sales script templates tailored to a sales conversation. You need messaging ideas for lead nurturing or A/B testing subject lines.

When sales-automator is not the right choice

You need to actually send emails or integrate with a CRM or outreach platform. The task is unrelated to sales messaging or sales enablement content.

What it produces

Produces text report.