New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Product Launch

by cbrock84 in cbrock84/headcount

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to…

MITAuto-check passedMarketing & SEO

Install Product Launch

skills CLI
$ npx skills add cbrock84/headcount --skill product-launch -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cbrock84/headcount product-launch --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/marketing/skills/product-launch .claude/skills/product-launch && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-launch
GitHub stars
2k
Token cost
~1.1k tokens
SKILL.md length
639 words
Files
2 (incl. references)
Skills in repo
178
Repo updated
First seen
Licence
MIT

At a glance

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to…

  • Tasks that involve Product launch strategy
  • SKILL.md covers Tier the launch before…, Sequence internal readiness…, Decide who it is for, and say… and Pick a date for a reason, and…, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Launch is an agent skill from cbrock84/headcount. Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).

It sits in Marketing & SEO, covering Product launch strategy. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.

When your agent uses it

  • Tasks that involve Product launch strategy

Example prompts

  • “Use the product-launch skill to take something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing…”
  • “/product-launch”

What it can do on your machine

Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Launch loads about 1.1k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 129 tokens; SKILL.md has 639 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~129
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 639 words, ~1,115 tokens.

Download SKILL.mdSave it as .claude/skills/product-launch/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
product-launch
description
Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach. Use this to plan a launch, right-size one that is consuming more than it deserves, work out why a released feature nobody uses was launched loudly, or run the weeks after launch day.

Product launch

A launch is not an announcement. The announcement is the cheapest part and the part most likely to be mistaken for the whole thing, which is how features get press coverage and no adoption.

Tier the launch before planning it

Not everything deserves the same treatment, and treating everything as major is how a team burns its own attention and its audience's.

  • Tier one — changes the story you tell about the product, or opens a new segment. Full motion: positioning work, press, sales enablement, customer communication, campaign.
  • Tier two — meaningful to existing customers, not a new story. In-product announcement, documentation, a note to affected accounts, sales briefing.
  • Tier three — improvement. Release notes and nothing else.

Agree the tier before work starts, and expect the pull toward tier one from whoever built it. Effort spent above the tier is taken from somewhere else, usually from the next launch.

Sequence internal readiness ahead of the announcement

The order matters and gets reversed constantly. Support and sales find out from the announcement, then spend launch week answering questions they were never briefed on, badly.

Before anything external: documentation exists, support can answer the top questions, sales knows who it is for and who it is not for, pricing and packaging are decided and configured, and the thing works for the accounts that will try it first.

Have someone outside the team use it from scratch. The team cannot see the first-run experience any more, and the first-run experience is what everyone else gets.

Decide who it is for, and say who it is not for

A launch aimed at everyone lands on no one. Name the segment, the problem it solves, and what changes for them — and say explicitly who should not use it yet. Sales will otherwise sell it to whoever asks, and the earliest customers will be the worst-fit ones.

Pick a date for a reason, and defend the criteria over the date

Launch dates get set by an event, a quarter, or a promise. Whatever fixes it, write down the criteria that must hold to launch on it — quality bar, documentation, support readiness — and treat those as the real gate.

Launching before support readiness is the most expensive way to save a week. The cost lands as a bad first impression on exactly the customers most interested in the thing.

Show full SKILL.md (247 more words)Show less

Plan the days after, not just the day

Most launch plans end on launch day, which is where the work starts. Schedule the follow-through: a second wave for people who missed the first, in-product prompts for users who have not tried it, outreach to accounts that fit, and a check on the questions arriving in support.

Watch the first support tickets closely. They are the fastest signal about what the launch got wrong, and they arrive before any dashboard moves.

Measure adoption, not announcement

Reach, impressions and press mentions measure the announcement. What matters is whether the intended people are using the thing and whether it did what the roadmap claimed.

Decide the number before launch — how many of which accounts, doing what, by when. A launch evaluated on engagement metrics chosen afterward is always a success and teaches you nothing.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Announce externally before support and sales can answer the obvious questions.
  • Run a tier-one motion for a tier-three change because the team is proud of it.
  • Launch to everyone because narrowing the audience feels like reducing the impact.
  • Report launch success in reach when the goal was adoption.

© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in plugins/marketing/skills/product-launch of cbrock84/headcount.

  • SKILL.md
  • references/sources.md

Open the folder on GitHubat commit 98d1c17

Compare with similar skills

Product Launch next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Launch compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Launch this skillcbrock84/headcount2k—~1.1kAutomated safety check: PassMIT
Technical Launch Plannerjamesrochabrun/skills2161 repos~3.8kAutomated safety check: PassMIT
Getxapi ConnectLeoYeAI/openclaw-marketing-skills1k1 repos~715Automated safety check: PassCustom licence
ProducthuntReScienceLab/opc-skills1.8k—~467Automated safety check: PassApache-2.0
Micro SaaS Launchernicepkg/auto-company1948 repos~1.3kAutomated safety check: PassNone
Directory Submissionscoreyhaines31/marketingskills54k2 repos~6.7kAutomated safety check: PassMIT

Similar skills

  • Technical Launch Planner

    jamesrochabrun/skills

    Plan and execute technical product launches for developer tools, APIs, and technical products.

    216 GitHub starsUsed in 1 repo~3.8k tokens
    Marketing & SEOAuto-check passed

  • Getxapi Connect

    LeoYeAI/openclaw-marketing-skills

    Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.

    1k GitHub starsUsed in 1 repo~715 tokens
    Marketing & SEOAuto-check passed

  • Producthunt

    ReScienceLab/opc-skills

    Search and retrieve content from Product Hunt. An agent skill from ReScienceLab/opc-skills.

    1.8k GitHub stars~467 tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Micro SaaS Launcher

    nicepkg/auto-company

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software.

    194 GitHub starsUsed in 8 repos~1.3k tokens
    Marketing & SEOAuto-check passed

  • Directory Submissions

    coreyhaines31/marketingskills

    When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.

    54k GitHub starsUsed in 2 repos~6.7k tokens
    Marketing & SEOAuto-check passed

  • Producthunt

    FoundDream/miniclawd

    Discover trending tech products, apps, and tools from Product Hunt.

    138 GitHub stars~722 tokensUpdated 8 mo ago
    Marketing & SEOAuto-check passed

More from cbrock84/headcount

All 178 skills in this repo

  • Agent Hierarchy

    cbrock84/headcount

    Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…

    2k GitHub stars~1.2k tokensUpdated 22 days ago
    Auto-check passed

  • Access And Identity

    cbrock84/headcount

    Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.

    2k GitHub stars~1.1k tokensUpdated 22 days ago
    Auto-check passed

  • Account Based Marketing

    cbrock84/headcount

    Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…

    2k GitHub stars~1.2k tokensUpdated 22 days ago
    Auto-check passed

  • Activation

    cbrock84/headcount

    Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.

    2k GitHub stars~865 tokensUpdated 22 days ago
    Auto-check passed

  • AI ML Governance

    cbrock84/headcount

    Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.

    2k GitHub stars~1k tokensUpdated 22 days ago
    Auto-check passed

  • AI Research Analyst

    cbrock84/headcount

    Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.

    2k GitHub stars~916 tokensUpdated 22 days ago
    Auto-check passed

Categories

Questions about Product Launch

What does Product Launch do?

Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to…. Product Launch is an agent skill from cbrock84/headcount. Takes something built and gets it into the market — tiering the launch to match what it actually warrants, sequencing internal readiness before external announcement, preparing sales and support to answer the questions it creates, choosing the date for a reason, and measuring adoption rather than announcement reach.

When should I use Product Launch?

Product Launch fits situations like: tasks that involve Product launch strategy.

How do I install Product Launch in Claude Code?

Run `npx skills add cbrock84/headcount --skill product-launch -a claude-code`. Or copy the skill folder (plugins/marketing/skills/product-launch in cbrock84/headcount) into .claude/skills/product-launch in your project. Claude Code loads it when a task matches its description.

How do I install Product Launch in Codex?

Run `npx skills add cbrock84/headcount --skill product-launch -a codex`. Or copy the skill folder (plugins/marketing/skills/product-launch in cbrock84/headcount) into .agents/skills/product-launch in your project. Codex loads it when a task matches its description.

Can I use Product Launch in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill product-launch -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-launch, .gemini/skills/product-launch, .github/skills/product-launch and .opencode/skills/product-launch in your project.

What does Product Launch need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Launch is instructions for the agent only.

Does Product Launch access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Launch safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Launch use?

Product Launch is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Launch use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 447 tokens, read only when the agent opens those files.

What are the alternatives to Product Launch?

Skills that share tags, products or a category with Product Launch: Technical Launch Planner (jamesrochabrun/skills, 216 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars), Producthunt (ReScienceLab/opc-skills, 1.8k stars) and Micro SaaS Launcher (nicepkg/auto-company, 194 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Launch?

cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,016 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.

Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.