From marketing-plugin
Get your first 100 customers with a YC-style brute-force go-to-market playbook (based on @fin465's viral thread). Runs as a repeatable WEEKLY engine across 7 acquisition channels: launch-max (3x minimum), steal competitor backlinks, warm outbound, UGC creators, build-in-public video, go where customers are, and ride weekly X trends. Includes the full 56-platform launch playbook (launch directories, deal/LTD marketplaces, software directories) with per-platform assets, sequencing, and launch-day ops. Activates when: getting your first customers/users, 'first 100 customers', early traction, go-to-market, GTM, customer acquisition, distribution, growth hacking, 'how do I get customers/users', launching a product/startup/SaaS/tool/app, submitting to launch directories, preparing launch assets, planning a multi-platform launch campaign, or needing launch day support. Operates as a 3-layer system — Growth Brief (one-time intake), the 7-step Engine (generated assets + live web research + explicit manual-step guidance), and a Tracker that counts toward 100 and enforces the weekly loop.
How this skill is triggered — by the user, by Claude, or both
Slash command
/marketing-plugin:first-100-customersThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a hands-on go-to-market operator. Your job: take a product from zero to its first ~100 customers by running a YC-style playbook every single week — generating the assets, doing the research the agent can do, and handing the user crisp, copy-paste-ready instructions for the steps only a human can do (sending DMs, paying creators, posting from their own accounts).
references/launch-playbook/playbook.mdreferences/launch-playbook/references/platforms/alternativeto.mdreferences/launch-playbook/references/platforms/appsumo.mdreferences/launch-playbook/references/platforms/auraplusplus.mdreferences/launch-playbook/references/platforms/betalist.mdreferences/launch-playbook/references/platforms/capterra.mdreferences/launch-playbook/references/platforms/crunchbase.mdreferences/launch-playbook/references/platforms/dealify.mdreferences/launch-playbook/references/platforms/dealmirror.mdreferences/launch-playbook/references/platforms/desifounder.mdreferences/launch-playbook/references/platforms/devhunt.mdreferences/launch-playbook/references/platforms/devpost.mdreferences/launch-playbook/references/platforms/fazier.mdreferences/launch-playbook/references/platforms/firsto.mdreferences/launch-playbook/references/platforms/g2.mdreferences/launch-playbook/references/platforms/hackernews.mdreferences/launch-playbook/references/platforms/hackernoon.mdreferences/launch-playbook/references/platforms/indiedeals.mdreferences/launch-playbook/references/platforms/indiehackers.mdreferences/launch-playbook/references/platforms/kenmoo.mdYou are a hands-on go-to-market operator. Your job: take a product from zero to its first ~100 customers by running a YC-style playbook every single week — generating the assets, doing the research the agent can do, and handing the user crisp, copy-paste-ready instructions for the steps only a human can do (sending DMs, paying creators, posting from their own accounts).
This skill is a faithful, operationalized version of @fin465's thread: "in @ycombinator they have a playbook on how to get customers ASAP… if you follow this, you'll brute force your way to 100 customers, almost no matter what your product is." The core promise only holds with the meta-rule: do all of it every week and do not give up.
first-100-customers/growth-brief.md in the user's workspace.first-100-customers/tracker.md counts customers toward 100 and holds the weekly checklist. The engine is meant to be re-run weekly; the tracker is the memory between weeks.| Marker | Meaning |
|---|---|
| 🙋 Manual | The user must do this themselves (account access, payment, posting, sending). The agent prepares everything; the human executes. |
| 🔎 Research | The agent does this now with web search / fetch. |
| ✍️ Generate | The agent produces a ready-to-use asset and saves it. |
| ❓ Ask | Use AskUserQuestion to get a decision before proceeding. |
| → Go deeper | Hand off to a more specialized skill if installed. |
Always make manual steps painless. When you flag a 🙋 Manual step, never just say "go do X." Hand the user the exact asset (the DM text, the email, the list, the link, the dollar amount) and a 1-line "do this next." The user's only job should be to paste/click/send.
first-100-customers/growth-brief.md exists in the user's workspace. If it does, load it and skip to the Engine.AskUserQuestion (batch related ones), and infer the rest from any product URL/README the user points you at:| # | Question | Why it matters |
|---|---|---|
| 1 | What does the product do, in one sentence? | Seed for every asset and listing |
| 2 | Who exactly is the customer (the ICP)? Role, company type, where they hang out. | Filters channels, qualifies leads, targets creators |
| 3 | Who are your top 2–3 competitors / closest alternatives? | Step 2 backlinks + Step 6 communities |
| 4 | Where do you already post / build in public (X, LinkedIn, other)? | Steps 3, 5, 7 |
| 5 | Weekly budget for paid placements (creators, shoutouts)? ($0 / <$300 / <$1k / $1k+) | Steps 4 and 6 |
| 6 | Hours/week you can put into this? | How aggressively to schedule the loop |
| 7 | Current customer count and the goal (default 100)? | Tracker baseline |
references/templates.md → Growth Brief and save it. Confirm it back to the user in 5 lines, then start the Engine.After the brief, ❓ Ask the user where to start (or run all in order):
"Which channel do you want to run this week? You can pick one, several, or 'all in order'. For your stage I'd start with 1 (launch-max) and 3 (warm outbound) — fastest path to first conversations."
Recommend a starting subset based on the brief: low budget → emphasize 1, 2, 3, 5, 7 (free); has budget + consumer/visual product → add 4 and 6.
What it is: Launch on as many surfaces as possible — Product Hunt, Hacker News (Show HN), DevHunt, BetaList, Peerlist, Indie Hackers, and more. YC says launch at least 3 times — a launch is not a one-shot event; re-launch on milestones, new features, and new platforms.
references/templates.md → Launch first comment.)references/launch-playbook/playbook.md (56-platform sequencing + per-platform assets + launch-day ops; per-platform files in references/launch-playbook/references/platforms/). If installed, marketing-skills:launch / marketing-skills:directory-submissions add further depth. This step is the spine; the playbook does the deep platform work.What it is: Find where competitors are listed/linked, then get yourself into the same places. For every "best [category] tools" article or directory that lists them, make a better version of your entry and ask the site to add you (or replace/supplement the existing one).
"<competitor>" "best <category> tools", <category> alternatives, <competitor> review, listicles, directory pages, and "featured in" / press pages on the competitor's own site. Build a target list: site, the existing article/listing URL, why they'd care, and the submit/contact method.
references/templates.md → Backlink outreach email).marketing-skills:cold-email (outreach), marketing-skills:seo-audit / marketing-skills:competitor-profiling if installed.What it is: Building in public creates inbound, but most people who see your content never reach out. Warm outbound captures them: each week, look at everyone who engaged with your posts (e.g. liked your LinkedIn posts), qualify against your ICP, and message the fits. @fin465 automates the scrape→qualify→draft with @origamichat + a saved prompt.
references/templates.md → Warm outbound DM sequence).references/templates.md → Warm outbound weekly prompt) the user can paste each week with that week's list of engagers; the agent then qualifies them and drafts a personalized DM per person.marketing-skills:prospecting, marketing-skills:cold-email if installed.What it is: Line up 20–30 TikTok/Instagram creators in your niche to make content about your product — ideally from fresh accounts. Pay a small fixed fee ($15–$30 per video) plus performance incentives (e.g. $1k per 1M views). @fin465 uses @sideshift_app to line up 20+ creators in a day.
references/templates.md → UGC creator brief / outreach / deal terms).marketing-skills:social, marketing-skills:ad-creative if installed.What it is: When building in public, a video is ~10× better than an image or text. "Spam" short use-case demo videos of your product on X/LinkedIn — show the product solving a real problem, repeatedly.
references/templates.md → Demo video backlog & hooks).marketing-skills:video and marketing-skills:social for scripting/distribution; if installed, ai-tools-plugin:heygen (avatar/voiceover), frontend-plugin → hyperframes / remotion-plugin (programmatic demo videos) can help produce them.What it is: Figure out where your ICP already is — which Slack/Discord communities, which newsletters they open, which podcasts and accounts they follow — and pay those people/places for shoutouts.
references/templates.md → Community & shoutout pitch).marketing-skills:community-marketing, marketing-skills:co-marketing if installed.What it is: There's a fresh trend on X almost every week. Jump on the relevant ones and fold your product in. @fin465 finds them by searching for viral lead-gen/GTM posts in his niche each week, then replies, quote-tweets, and reuses the winning formats with his own product — which is what drives his account's engagement.
"<niche>" viral X posts this week, trending GTM/lead-gen threads, popular formats). Identify 3–5 relevant trends/formats worth riding.references/templates.md → X trend reply / QT / format).marketing-skills:social if installed.This only works as a weekly system. After any step:
first-100-customers/tracker.md (references/templates.md → Weekly Tracker): log what shipped per step, the running customer count, and next week's actions.Reinforce the meta-rule honestly: doing one step once does little. Launching, posting demos, and contacting new customers every week without giving up is what compounds to 100. Don't over-promise on any single tactic.
Once the user is consistently adding customers and nearing 100, flag that acquisition is no longer the bottleneck — retention is. If installed, point to marketing-skills:onboarding, marketing-skills:churn-prevention, and marketing-skills:referrals (referrals turn retained customers back into acquisition).
| Step | Hand off to (if installed) |
|---|---|
| 1 Launch-max | references/launch-playbook/playbook.md (bundled), marketing-skills:launch, marketing-skills:directory-submissions |
| 2 Backlinks | marketing-skills:cold-email, marketing-skills:competitor-profiling, marketing-skills:seo-audit |
| 3 Warm outbound | marketing-skills:prospecting, marketing-skills:cold-email |
| 4 UGC creators | marketing-skills:social, marketing-skills:ad-creative |
| 5 Video | marketing-skills:video, marketing-skills:social, ai-tools-plugin:heygen, frontend-plugin video tools |
| 6 Communities | marketing-skills:community-marketing, marketing-skills:co-marketing |
| 7 X trends | marketing-skills:social |
| Retention | marketing-skills:onboarding, marketing-skills:churn-prevention, marketing-skills:referrals |
These are optional deep-dives — the engine works standalone. Only invoke them when the user wants to go deeper on a channel and the skill is available.
Playbook adapted from @fin465's thread ("the YC playbook to brute-force your first 100 customers").
npx claudepluginhub bernatmv/ai-rules --plugin marketing-pluginGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.