agentleFS
hailneedhailneed/painradar/skills/launch/SKILL.md

launch

Skill0 starsChanged 3 months agoMITView on GitHub

Build an evidence-based launch and marketing flow for a product, repo or chosen opportunity — channel selection with stated reasons, posting rules for Reddit / Hacker News / Product Hunt, an SEO comparison-page plan, a TrustMRR listing step, a 30-day calendar and 3 content briefs grounded in the radar evidence. Use when the user asks how to market or launch, where the first customers come from, "pazarlama akışı", "lansman planı", "nasıl duyururum", "go-to-market", "launch plan", or runs /painradar:launch [repo | idea]. Uses the latest radar/fit reports when present; asks one question when the product is unclear. Not for finding pain points — that is painradar:scan.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-policy, tool-rename-deprecation and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • OpenCortexIDESkill

    add-policy

    Use when adding, modifying, or reviewing VS Code configuration policies. Covers the full policy lifecycle from registration to export to platform-specific artifacts. Run on ANY change that adds a `policy:` field to a configuration property.

    Also in 4 projects that use this

  • gitpod-ioSkill

    tool-rename-deprecation

    Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

    Also in 4 projects that use this

  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 9 projects that use this

  • CesarjoquinSkill

    co-marketing

    When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

    Also in 9 projects that use this

  • martinbattaglia-commitsSkill

    marketing-loops

    When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

    Also in 6 projects that use this

  • aiunlocked1412Skill

    influencer-marketing

    Influencer marketing AI — brief, pitch, rate evaluation, performance review แบบ data-driven

    Also in 5 projects that use this

  • +4 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 63 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write the concrete rules for the chosen channels (from the reference): reply-first period, ratio of help to promotion, what gets banned, …

    line 38
  2. Distinctive:

    Keep it doable for the persona's capacity.

    line 46

“Common” is measured: kept by at least 6 in 10 of the 63 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch flow

A launch plan is a set of decisions with reasons, not a list of channels. Every channel you recommend must cite either the radar evidence (where the complaints live) or the channel notes in ${CLAUDE_PLUGIN_ROOT}/skills/launch/references/channels.md.

Language rule: write every user-facing output in the language the user is speaking with you.

Step 0 — Inputs

  • Product: the argument (repo → read README/package manifests in the current directory to describe it; idea → take it from the latest ~/.claude/radar/*-fit-*.md). If still unclear, ask one question: what it does and for whom.
  • Latest radar report for that topic (run scan if missing): the threads, communities and phrasing in it are the audience map.
  • Persona card if present (~/.claude/persona/persona.md) to match tone and capacity (e.g. someone who never writes long-form should not be given a 4-posts-a-week blog plan).

Step 1 — Positioning (short)

One sentence in the complainers' own words (lift phrasing from the evidence), one sentence on the job it does, three reasons to believe. Name the incumbent it replaces.

Step 2 — Channel selection with reasons

Pick one primary channel and at most two supporting channels for the first 90 days, following references/channels.md. Justify each with evidence ("the radar found 9 of 14 threads in r/X" or "revenue correlates with Domain Rating, so comparison pages"). Say explicitly which popular channels you are not using and why.

Step 3 — Rules before posting

Write the concrete rules for the chosen channels (from the reference): reply-first period, ratio of help to promotion, what gets banned, Show HN title/body constraints, when Product Hunt is worth it, how to list on TrustMRR and use the verified-revenue proof.

Step 4 — 30-day calendar

Week by week: what is published where, which threads to answer (link them from the radar), which comparison/alternative pages to write, when to launch, what to measure. Keep it doable for the persona's capacity; fewer items done well beat a full calendar.

Step 5 — Three content briefs

For the top 3 radar themes, one brief each (format · working title · hook · angle · 3–6 beats · linked proof points · CTA · why now). Stop at outline level — the user writes in their own voice.

Step 6 — Measure

Define 5 numbers to track weekly (e.g. qualified conversations started, signups from primary channel, comparison-page impressions, trial→paid, replies per post) and the kill/continue rule for the primary channel at day 30 and day 90.

Save ~/.claude/radar/<slug>-launch-<date>.md; reply with the primary channel + reason, the first three actions this week, and the first measurement rule.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.