campaign-builder
Skill3 starsChanged 4 months agoMITView on GitHub
Builds an end-to-end plan for a launch, series, or challenge across three phases — pre-launch (teaser/waitlist), launch (daily beats + CTA ladder), and post (nurture/repurpose) — with a day-by-day beat sheet and per-phase metrics. Use when the user is launching a product, running a series or challenge, asks for a "launch plan" or "30-day challenge", or is promoting an offer. Trigger on launch/campaign/series/challenge/promotion requests. Works with any capable model.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Buzzlead-dev-org/campaign-buildertheir own version, first seen May 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Buzzlead-dev-org/campaign-builder★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- analytics-interpreterSkill
- audience-bullseyeSkill
- brand-voice-keeperSkill
- breakout-detectorSkill
- channel-competitor-analysisSkill
- content-strategy-engineSkill
- cross-platform-adapterSkill
- engagement-boosterSkill
- growth-orchestratorSkill
- hook-machineSkill
- offer-cta-architectSkill
- onboarding-brand-briefSkill
- performance-optimizerSkill
- profile-optimizerSkill
- repurpose-masterSkill
- trend-jackerSkill
- viral-script-generatorSkill
- visual-idea-generatorSkill
- youtube-title-labSkill
The file
Files
Campaign Builder
A campaign is a story with a deadline, not a pile of promo posts. Audiences buy at the peak of desire, and desire is manufactured through sequenced beats — anticipation before availability, urgency at the close. First-principles: warm the audience before you ask, escalate the CTA from soft to hard so no one feels ambushed, and stack scarcity at the end where it converts. The plan below turns any launch into a three-act arc with defined beats and a metric per phase so you know if it's working before the cart opens.
1. Pre-launch — manufacture anticipation (7-14 days)
- Tease the problem, not the product. Post the pain your offer solves; agitate it. No selling yet.
- Open a waitlist / early-access list. Trade a lead magnet or "first + cheapest" promise for the email/DM. This is your launch-day fuel.
- Seed proof and story. Share the origin, the beta results, behind-the-scenes of building it.
- Run a countdown mechanic in the final 3 days: "3 days until X" posts + Stories with a reminder sticker.
- Metric: waitlist size + reply/DM rate. A cold audience won't warm on launch day — grow the list here or the launch stalls.
2. Launch — daily beats + CTA ladder (3-7 days, cart open)
Escalate the CTA from soft to hard across the window:
- Open (soft): "It's live. Here's what it is and who it's for." Link/CTA once.
- Value + demo: show it working; a mini-win or free sample. CTA: "See how it works."
- Proof day: testimonials, case study, results screenshots. CTA: "Join them."
- Objection crush: FAQ, guarantee, "is this for me?" CTA: direct.
- Urgency (hard): "Price rises / bonus disappears in 48h." Real deadline only.
- Final call: "Closes tonight." Multiple posts + Stories + an email. Expect 30-50% of sales here.
- Metric: CTR, add-to-cart, conversion rate, revenue per beat. Watch which beat sells — double it next launch.
3. Post-launch — nurture + repurpose (7-14 days)
- Onboard + deliver a fast win so new buyers succeed and refer.
- Sell the non-buyers softly: a downsell, waitlist for next round, or "doors reopen" list.
- Repurpose the campaign: best-performing beats become evergreen content; testimonials feed the next pre-launch.
- Debrief: log open/close numbers, best beat, biggest objection.
- Metric: fulfillment/refund rate, referral rate, list growth for next launch.
Output template
CAMPAIGN: ___ OFFER: ___ CART: [open date] → [close date]
PRE-LAUNCH (D-14 → D-1)
D-14 Tease problem | grow waitlist
D-7 Lead magnet + waitlist | capture emails
D-3 Story + proof | warm list
D-1 Countdown / final tease | prime buyers
LAUNCH (D0 → D5)
D0 OPEN (soft CTA) D1 Demo/value D2 Proof
D3 Objection crush D4 Urgency (hard) D5 FINAL CALL (close)
POST (D6 → D14)
Onboard + fast win → downsell non-buyers → repurpose + debrief
METRICS: Pre = waitlist size | Launch = conv% + rev/beat | Post = refunds + referralsPlatform variants
- Email: the conversion engine — open, proof, urgency, final call as separate sends; final-day = 2 emails.
- Instagram/TikTok: Stories carry countdowns and reminders; feed carries proof and demos.
- X/Threads: launch-day thread + reply-with-link; pin the offer.
- YouTube/Long: one deep demo or case study during the value beat.
- Live: a launch-day or close-day live is the single highest-converting beat — use it for objection crush.
Rules
- Warm before you sell. Cold launches to cold audiences fail — the waitlist is the launch.
- Escalate soft → hard. Never open on max urgency; never close on soft.
- Scarcity must be real. Fake countdowns that reset kill trust and future launches.
- One offer, one deadline per campaign. Competing CTAs split conversions.
- The close beat outsells the open — plan your heaviest push for the final 48 hours.
- Debrief every launch and feed the winners into the next pre-launch. Campaigns compound.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

