Creator Outreach Kit
Cold-outreach pipeline for open-source creators: find public emails, verify them, send personalized batches.
- What
- Cold-outreach pipeline for open-source creators: find public emails, verify them, send personalized batches.
- Cost
- Free
- Needs
- Set up the Creator Outreach Kit for your own campaign. You need: a Gmail account connected for sending, a GitHub token (public profiles only), and dig on your PATH.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
The Creator Outreach Kit is the complete cold-email pipeline Skill Harbor used to contact 255 open-source creators about their listings, with a bounce rate under 4% after verification. It covers the whole chain, not just the sending: collect public GitHub emails for a list of creators, verify every address with a syntax check plus an MX/A DNS lookup (free, via dig), build a deduped send queue with one personalized message per creator, and send in daily batches with per-recipient claim links and an opt-out line in every message. The kit ships with two working Python scripts. verify_emails.py takes your collected profiles and marks each address valid or not. send_batch.py sends the next N unsent queue entries through Gmail, marks them sent with a timestamp, and appends everything to send-log.txt. Both scripts share the same anti-placeholder guard that rejects scraper artifacts ([email protected], [email protected], u003e unicode escapes, fake domains) at queue-build time and again at send time, so a bad address can never slip through twice. The operating rules are baked in: public emails only (never guess private addresses), one email per creator even for multiple projects, an opt-out in every message, no tracking pixels (developers notice), about 30 sends per day from a warmed-up mailbox, and a next-day bounce triage because a 200 OK on send is not proof of delivery. If your product has per-creator pages, the kit also documents the HMAC-signed, expiring claim-link pattern so a creator can take over their listing with zero account friction.
Version:
Install
Copy the install package below, then paste it into MuseCommunity-built. Skill Harbor doesn't audit code — review the source before installing.
Set up the Creator Outreach Kit for your own campaign. You need: a Gmail account connected for sending, a GitHub token (public profiles only), and dig on your PATH. 1. Build targets.json: one row per creator with your internal id, their github_login, and their display name. 2. Collect: for each login, call the GitHub users API (authenticated, 5,000 req/hour) and keep the email ONLY if the profile lists it publicly. Save as profiles.json. Never guess private addresses. 3. Verify: run verify_emails.py profiles.json --out emails-verified.json. It checks syntax and MX/A records per domain (cached). Keep only valid addresses. 4. Queue: build queue.json with one entry per email (dedupe!), hottest first. Each entry needs email, creator_name, projects text, and claim_url. Placeholder-looking addresses are rejected automatically. 5. Send: run send_batch.py --queue queue.json --account YOUR_GMAIL_ACCOUNT_ID --subject "Your subject" --template template.txt --batch 30. It sends sequentially about 2 seconds apart, marks sent with timestamps, and logs everything. Show the exact subject and body to a human and get an explicit go before the first batch. 6. Next day: check Mail Delivery Subsystem bounces, classify them (nonexistent, blocked, delayed), and prune dead addresses from future queues. Rules that keep you out of trouble: public emails only, one email per creator, opt-out line in every message, no tracking pixels, ~30/day max.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.