agentsclimarketplace

Viral launch

Skill oleg-koval/agent-skills/packages/marketing/viral-launch

Opinionated agent skill catalog for Codex, Claude, Cursor, Copilot, and launch workflows.

Install
npx -y skills add oleg-koval/agent-skills --skill viral-launch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Set up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops without pretending virality is guaranteed.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.2 KB, as published. Nobody here has run it

viral-launch

Use this skill when a user wants to launch a project, make a repo marketable, improve discoverability, or build shareable launch assets.

This skill is opinionated: virality is not a promise. The goal is to make the project easy to understand, easy to share, and easy to act on.

Trigger phrases

  • make this repo launch-ready
  • set this up to go viral
  • prepare a product launch
  • create marketing assets for this project
  • improve the README for launch
  • prepare Product Hunt / Hacker News / X / LinkedIn launch copy
  • set up an open-source repo for growth

Workflow

  1. Inspect the project first:
  • product purpose
  • target user
  • core use case
  • current README and docs
  • install or demo path
  • screenshots, videos, or visual proof
  • analytics or waitlist capture if present
  1. Define the launch angle in one sentence:
  • who it is for
  • what painful job it solves
  • why now
  • what makes it different
  1. Make the repo launch-ready:
  • clear README headline and first paragraph
  • demo or quickstart within the first screen
  • installation steps that work from a clean checkout
  • screenshots, GIF, or demo link where possible
  • feature list based on outcomes, not implementation trivia
  • examples for the highest-intent use cases
  • badges only when they add trust
  • license, contributing notes, and issue templates when useful
  1. Create launch assets:
  • short tagline
  • 1-paragraph announcement
  • 5 social post variants
  • Product Hunt tagline and description when relevant
  • Hacker News title candidates when relevant
  • launch email or DM when relevant
  • creator/influencer outreach list criteria, not spam copy
  1. Design share loops:
  • a reason users would show the output to someone else
  • a public artifact worth linking
  • a before/after demo
  • a template, benchmark, checklist, or gallery that can travel
  • referral or waitlist loop only if it fits the product
  1. Define proof and metrics:
  • activation event
  • share event
  • conversion event
  • retention proxy
  • launch-day dashboard or simple tracking checklist
  1. Keep claims grounded:
  • do not invent traction, logos, benchmarks, testimonials, or user counts
  • mark assumptions explicitly
  • prefer specific proof over hype
  • avoid dark patterns and spam

Output format

When planning, produce:

  • Launch angle
  • Repo changes
  • Launch assets
  • Share loops
  • Metrics
  • Risks and assumptions
  • Next actions

When editing a repository, make the smallest useful set of changes first, then validate by reading the README from a new user's perspective.

References

  • references/launch-checklist.md
  • references/external-skills.md

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.