outreach-batch

Outreach Batch

You are managing a maker outreach campaign for Your Project. Your goal is to get tool makers to claim their listings, increasing engagement and moving toward revenue.

Before Starting

Check for context first:

• How many emails have already been sent this session? (Check playbook)
• Did previous batches get any claims? (Check magic_claim_tokens on prod)
• Has S&QA approved more outreach, or said to wait for signal?

Context Needed

1. How many targets? (Default: 15-20 per batch)
2. Star threshold? (Default: 1000+ GitHub stars)
3. Any tools to exclude? (Already emailed list)

How This Skill Works

Mode 1: Full Campaign (first time)

Run all 6 steps below in order. Takes ~30 minutes with departments.

Mode 2: Next Batch (adding more)

Skip to Step 1 with exclusions from previous batches. Reuse existing templates.

Mode 3: Follow-Up

Check claim analytics, resend to non-responders with adjusted angle after 7 days.

The 6-Step Process

Step 1: Find Targets (Backend)

SELECT slug, name, github_stars, url FROM tools
WHERE status='approved' AND maker_id IS NULL
AND github_stars > {threshold}
AND slug NOT IN ({already_emailed})
ORDER BY github_stars DESC LIMIT {count}

Step 2: Find Emails (Backend)

For each target, try in order:

1. gh api users/{owner} --jq '.email'
2. gh api repos/{owner}/{repo} --jq '.owner.email'
3. Check CONTRIBUTING.md, README security contacts
4. Check package.json/composer.json author fields

Expected hit rate: ~70%. Skip tools with no public email.

Step 3: Audit Target Pages (MCP Dept)

BEFORE sending, verify each tool page has:

• Correct install_command (NOT wrong tool — Cal.com had mailhog!)
• Non-truncated tagline
• Description that's more than just the tagline
• Correct category

Fix issues via Backend before proceeding.

Step 4: Write Emails (Content)

Two template types:

• Has MCP views (>0): "agents recommended your tool X times"
• Zero views: "AI agents couldn't find your tool — we fixed that"