oss-launch skill (samber): plan an open-source launch, gate to day 30

• Asks one question at a time until it can name the audience, anchor channel and goal.

  Eleven questions. Questions 8 to 10 (deadline, spike or compounding goal, effort ceiling) set the channel ranking, so they come before any proposal. SKILL.md also tells the agent to keep a few project notes in memory.

  Interview

• Treats a trademark or license conflict as a rename before launch, not a risk to carry.

  Runs a trademark clearance check across similar names, secures the domain, organization and handles, and settles license and CLA-versus-DCO in the same pass.

  Step 1 - Clear the name and the license

• Scores the repo against blockers and boosters; every blocker must pass first.

  The pass test is a cold run: someone who has never used the project follows only the README. If the agent can execute commands it does that run itself in a fresh directory and logs every guess.

  Runs code · Step 2 - Run the readiness gate

• Writes the one-liner and an explicit "why not X" answer, then checks credibility.

  The one-liner format is "<name> is a <category> for <audience> that <capability the alternatives lack>". It names real alternatives and publishes limitations up front.

  Step 3 - Sharpen the positioning

• Picks a single spike or a multi-day launch caravan.

  The default is a single spike. A caravan needs at least three announceable items, a conference or fixed date on the calendar and staff to name an owner per day.

  Step 4 - Choose the launch shape

• Picks one anchor channel and ranks six rows of work by outcome per maintainer hour.

  Registry publish, anchor post, secondary communities, your own accounts, newsletters and lists, and a long-form write-up. Rows 1 to 3 are the default launch.

  Step 5 - Sequence the channels

• Builds an hour-by-hour run of show with one named owner per channel.

  Includes the first top-level comment, a response rotation and a separate path for security reports that bypasses the rotation.

  Step 6 - Stand up the war room

• Bans soliciting votes or stars and sets day 1, day 7 and day 30 readings.

  It tells you to capture a baseline the evening before launch and to read stars against cloners and downloads.

  Step 7 and 8 - Velocity and measurement

• Produces a launch plan with nine sections, agreed one section at a time.

  Verdict, Clearance, Positioning, Audience, Shape, Channels, Run of show, Measurement and Risks.

  Try: “We're open-sourcing our internal feature-flag service next month. Can you plan the launch?”

  Launch plan output

Watch out for

• The cold run executes your README commands

  Step 2 has the agent follow your README in a fresh directory when it can execute commands. Our advice: use an empty directory or container and read each command before it runs. github.com

• It may keep notes in devrel-context.md

  SKILL.md tells the agent to store a few details about the current task or project, and to use a file called devrel-context.md when its memory lives in a file. Our advice: open that file before you commit or share the folder. github.com

• The plugin route installs the whole collection

  The README's plugin and extension routes add every skill in the repo; its git tree holds 93. The repo has no hooks, agents, commands or MCP server files, and 14 of its skills bundle a script. Our advice: use the skills CLI command for this skill if you want only it. github.com

Security advisories