Marketing Skills is an open-source library of reusable workflows that helps AI coding agents perform marketing and SEO tasks. It serves people working on search optimization, content, advertising, launches, analytics, and related marketing activities, and its catalogue entries are the individual skills agents can install.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add kostja94/marketing-skills --skill product-launchgit clone --depth 1 https://github.com/kostja94/marketing-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kostja94/marketing-skills/product-launch)<a href="https://agentmods.dev/skills/kostja94/marketing-skills/product-launch"><img src="https://agentmods.dev/badge/skills/kostja94/marketing-skills/product-launch/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kostja94/marketing-skills/product-launch"><img src="https://agentmods.dev/badge/skills/kostja94/marketing-skills/product-launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00088 | $0.00839 |
| Opus 5.5 | $0.00035 | $0.00336 |
| Sonnet 5.5 | $0.00018 | $0.00168 |
| Haiku 4.5 | $0.00009 | $0.00084 |
Grade A, and why
product-launch scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
2 near-identical copies found in the catalogue:
- product-launch — 100% identical, 2 lines differ
- product-launch — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategies: Product Launch
Guides product launch execution—channels, timeline, checklist, and cross-functional coordination. Use this skill when planning the launch of a new product or major feature. For GTM strategy (PLG/SLG/MLG, 90-day framework, ICP, new market entry, repositioning), see gtm-strategy. For cold start (first users, no product yet), see cold-start-strategy.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.
Identify:
- Launch type: New product, major feature, market expansion
- GTM mode: Sales-led, product-led, marketing-led, hybrid (from gtm-strategy)
- Channels: PR, paid, organic, email, events
Launch Checklist
- GTM strategy defined (see gtm-strategy)
- PMF validated (see pmf-strategy)
- Target market and ICP clear
- Messaging consistent across teams
- Channel mix chosen (PR, paid, organic, email)
- Timeline and milestones set
- Cross-functional owners assigned (RACI)
Channel Mix
| Channel | Use | Skills |
|---|---|---|
| PR | Press release, media relations | public-relations |
| Paid ads | Scale acquisition post-PMF | paid-ads-strategy |
| Organic | SEO, content, community | seo-strategy, content-marketing |
| Announcement to existing users | email-marketing | |
| Product Hunt / Directories | Launch-day buzz; early adopters | cold-start-strategy, directory-submission |
Critical Success Factors
| Factor | Guideline |
|---|---|
| PMF first | Validate product-market fit before scaling; see pmf-strategy |
| GTM alignment | One clear story; all teams use same messaging; see gtm-strategy |
| Avoid rush | Most failures = scale before PMF |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed 8d8cf961eef7
- 1mo ago First seen · 67 lines · 88 tokens per session scan A 9cab71274cd0
product-launch is a skill published in the GitHub repository kostja94/marketing-skills (1,067 stars, last pushed 3d ago), licensed MIT. It adds 88 tokens to every session and 839 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
partner-affiliate
When the user wants to build a partner program, launch an affiliate program, design integration partnerships, or create distribution partnerships. Also use when the user mentions 'partnerships,' 'affiliate program,' 'referral program,' 'partner ecosystem,' 'integration partner,' 'reseller,' 'co-marketing,'…
kill-criteria-exit-ramps
Establishes pre-defined, objective conditions for stopping projects and specific decision points for continue/pivot/kill evaluations. Guides through defining kill criteria, setting go/no-go gates, avoiding sunk cost fallacy, and executing disciplined stopping decisions. Use when defining stopping rules for projects…
forecast-discipline
Use to drive consistent forecast methodology, grading, and inspection cadences.
escalation-framework
Use to govern executive involvement, cross-functional response, and risk resolution for at-risk renewals.
renewal-playbooks
Use to design and maintain structured renewal/save motions across segments and risk levels.
stakeholder-ops
Use to coordinate approvals, communications, and accountability across teams for feedback programs.