Agent skill

Launch Strategy

by borghei in borghei/Claude-Skills

Plan and execute product launches and feature announcements: phased plans (alpha, beta, GA), channel strategy, Product Hunt playbooks, and post-launch momentum.

MITAuto-check passedMarketing & SEO

Install Launch Strategy

skills CLI
$ npx skills add borghei/Claude-Skills --skill launch-strategy -a claude-code

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

GitHub CLI
$ gh skill install borghei/Claude-Skills launch-strategy --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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/launch-strategy .claude/skills/launch-strategy && 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
launch-strategy
GitHub stars
874
Token cost
~3.9k tokens
SKILL.md length
1,839 words
Files
4 (incl. scripts)
Skills in repo
364
Repo updated
First seen
Licence
MIT

At a glance

Plan and execute product launches and feature announcements: phased plans (alpha, beta, GA), channel strategy, Product Hunt playbooks, and post-launch momentum.

  • Works in 4 steps: Pre-Launch (4-8 Weeks Before) → Launch Day Execution → Product Hunt Playbook → …
  • Launching a new product
  • SKILL.md covers Overview, Clarify First, Launch Tiers and Phase 1: Pre-Launch (4-8 Weeks…, plus 10 more sections
  • Runs Python scripts from its folder; calls python

What it does

Launch Strategy is an agent skill from borghei/Claude-Skills. Plan and execute product launches and feature announcements: phased plans (alpha, beta, GA), channel strategy, Product Hunt playbooks, and post-launch momentum. Use when launching a new product or feature, or planning a Product Hunt launch.

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/launch_metrics_tracker.py`, `scripts/launch_readiness_checker.py` and `scripts/launch_timeline_generator.py`).

It sits in Marketing & SEO, covering Product launch strategy. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Launching a new product
  • Planning a Product Hunt launch

Example prompts

  • “/launch-strategy”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Pre-Launch (4-8 Weeks Before)
  2. Launch Day Execution
  3. Product Hunt Playbook
  4. Post-Launch Momentum (30 Days)

What it can do on your machine

Read from SKILL.md and the folder at commit c9a1487. 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

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    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

Launch Strategy loads about 3.9k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 1,839 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 1,839 words, ~3,893 tokens.

Download SKILL.mdSave it as .claude/skills/launch-strategy/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
launch-strategy
description
Plan and execute product launches and feature announcements: phased plans (alpha, beta, GA), channel strategy, Product Hunt playbooks, and post-launch momentum. Use when launching a new product or feature, or planning a Product Hunt launch.
license
MIT + Commons Clause
metadata.version
1.0.0
metadata.author
borghei
metadata.category
marketing
metadata.domain
product-launch
metadata.updated
2026-03-09
metadata.frameworks
phased-launch, orb-channels, product-hunt, launch-momentum

Launch Strategy

Category: Marketing Tags: product launch, feature release, Product Hunt, go-to-market, launch playbook, announcement strategy

Overview

Launch Strategy provides the complete playbook for launching products and features that build momentum, capture attention, and convert interest into users. A product launch is not an event -- it is a campaign with pre-launch, launch day, and post-launch phases. Shipping without a launch plan is leaving growth on the table.


Clarify First

Before planning the launch, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Launch tier — Tier 1 major / 2 feature / 3 update / 4 changelog (sets effort level, channel mix, and timeline length)
  • Launch date — the target go-live (anchors the week-by-week pre-launch timeline and Product Hunt window)
  • Primary audience segment — who cares most about this release (drives positioning and ORB channel selection)
  • One-sentence value prop — what is launching and why anyone should care (drives the positioning template and announcement copy)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.


Launch Tiers

Not every release deserves the same effort. Classify first.

TierWhat It IsMarketing EffortExamples
Tier 1: Major LaunchNew product, major pivot, rebrand4-8 weeks prep, all channelsNew product launch, platform launch
Tier 2: Feature LaunchSignificant new capability2-4 weeks prep, owned + select channelsMajor feature, integration, new plan
Tier 3: UpdateImprovement to existing feature1 week prep, owned channels onlyPerformance improvement, UI refresh
Tier 4: ChangelogBug fix, minor improvementSame day, changelog onlyBug fixes, minor UX tweaks

The rest of this skill focuses on Tier 1-2 launches. Tier 3-4 follow a simplified version of the same process.


Phase 1: Pre-Launch (4-8 Weeks Before)

Week 8-6: Foundation

Positioning & Messaging

  1. Define the one-sentence value prop for this launch
  2. Identify primary audience segment (who cares most about this?)
  3. Draft the headline you want to see in coverage
  4. Answer the "so what?" question -- why should anyone care?

Positioning Template:

For [target audience] who [need/pain point],
[product/feature] is the [category]
that [key benefit].
Unlike [alternatives],
we [key differentiator].

Asset Checklist:

  • Landing page copy and design
  • Product screenshots / demo video
  • Blog post (announcement)
  • Email announcement draft
  • Social media posts (per platform)
  • Press release / media pitch (Tier 1 only)
  • Internal FAQ for team
  • Customer FAQ
Week 6-4: Build Momentum

Audience Warming

  • Tease the launch in social posts (building in public)
  • Share behind-the-scenes development content
  • Engage with potential users about the problem you are solving
  • Collect early feedback from beta users

Waitlist / Early Access For Tier 1 launches, consider a waitlist to build anticipation:

Waitlist Landing Page Elements:
1. Clear headline: what is coming
2. One-sentence description: why it matters
3. Email capture form
4. Social proof: "Join [X] others waiting"
5. Expected launch date
6. Share incentive: "Move up the list by sharing"
Week 4-2: Prepare Channels

The ORB Channel Framework

Categorize every launch channel as Owned, Rented, or Borrowed:

Channel TypeDefinitionExamplesControl
OwnedYou control the audienceEmail list, blog, product (in-app), changelogFull
RentedYou pay for accessPaid ads, sponsorships, promoted postsHigh (while paying)
BorrowedYou earn access through othersPress, influencer mentions, community shares, Product HuntLow

Channel Strategy by Tier:

ChannelTier 1Tier 2Tier 3
Email (full list)YesYesSegment only
Blog postLong-formShort-formChangelog
Social mediaMulti-post campaignSingle announcementBrief mention
In-app notificationYesYesOptional
Product HuntIf applicableNoNo
Press / mediaTargeted pitchesNoNo
Paid amplificationBudget allocatedSmall budgetNo
Partner co-marketingIf applicableNoNo
Community postsHN, Reddit, DiscordHN maybeNo
Week 2-1: Final Prep
  • All assets created and reviewed
  • Landing page live (or ready to flip)
  • Email sequences loaded and tested
  • Social posts scheduled
  • Team briefed on launch plan and talking points
  • Analytics tracking configured for launch metrics
  • Support team briefed on new feature / expected questions
  • Rollback plan documented (if something goes wrong)

Phase 2: Launch Day Execution

Launch Day Checklist (Time-Boxed)

T-2 hours:

  • Final check: landing page, links, tracking all working
  • Team Slack channel open for coordination
  • Support team ready

T-0 (Launch):

  • Flip landing page / feature gate live
  • Send email announcement (Segment 1: most engaged users)
  • Publish blog post
  • Post on social media (all platforms, staggered by 30 min)
  • Submit to Product Hunt (if planned -- see PH section)
  • Post in relevant communities (HN, Reddit, Discord)
  • Notify partners for co-promotion

T+2 hours:

  • Check analytics: traffic, signups, errors
  • Respond to all social media comments/questions
  • Send email announcement (Segment 2: broader list)
  • Monitor Product Hunt ranking (if applicable)

T+6 hours:

  • Share early results with team
  • Address any support issues
  • Engage with community discussion threads
  • Schedule next-day follow-up content

End of Day:

  • Document day-one metrics
  • Thank early adopters publicly
  • Note any issues for immediate fix
  • Confirm next-day plan
Launch Day Communication Rules
  1. Respond to everything -- launch day is not the day to ignore comments
  2. Founder engagement -- CEO/founders should personally reply on HN, Reddit, PH
  3. Celebrate wins publicly -- share milestones as they happen ("500 signups in first 3 hours!")
  4. Address issues immediately -- if something breaks, communicate before people complain
  5. Never argue -- if someone criticizes, thank them and learn

Phase 3: Product Hunt Playbook

Product Hunt is a launch channel, not a launch strategy. It works best when combined with the full ORB approach.

PH Timeline

Week -4: Preparation

  • Create / update Maker profile
  • Engage genuinely in PH community (comment on other products)
  • Build relationships with active PH hunters
  • Draft listing: tagline, description, first comment, media

Week -1: Pre-Launch

  • Confirm launch date (Tuesday, Wednesday, or Thursday -- avoid Monday/Friday)
  • Prepare all PH assets:
    • Thumbnail (240x240, clean, recognizable)
    • Gallery images (1270x760, show the product, not marketing fluff)
    • Demo video or GIF (under 60s)
    • First comment (personal, story-driven, not corporate)
  • Notify your network: "We are launching on PH on [date]"
  • Do NOT ask for upvotes (against PH guidelines and counterproductive)

Launch Day (12:01 AM PT)

  • Submit immediately after midnight PT (products are ranked by votes within a 24h window starting at midnight PT)
  • Post first comment within 5 minutes (this is your pitch)
  • Share across channels: "We launched on Product Hunt today" with direct link
  • Respond to EVERY comment on PH within 30 minutes
  • Engage authentically -- answer questions, thank feedback, acknowledge criticism

First Comment Template:

Hey PH! [Name] here, [role] at [Company].

We built [product] because [personal story about the problem].

[1-2 sentences about what it does and why it's different]

Here's what you get:
- [Key feature 1]
- [Key feature 2]
- [Key feature 3]

Special for PH: [offer -- extended trial, discount, early access to feature]

Would love your honest feedback. Happy to answer any questions!
PH Success Metrics
OutcomeWhat It Means
Top 5 of the dayStrong launch, badge, homepage visibility
Top 10 of the dayGood launch, still gets homepage traffic for 24h
Below top 10Minimal PH-specific value, but launch content still works elsewhere
Product of the week/monthSignificant ongoing PH traffic

Phase 4: Post-Launch Momentum (30 Days)

The launch is not over on day one. Most of the value comes from sustained post-launch activity.

Week 1 (Days 2-7)
  • Publish follow-up content: "What we learned from launching"
  • Share metrics publicly if impressive: "1,000 signups in 48 hours"
  • Create comparison pages: [Product] vs [Competitor A], vs [Competitor B]
  • Reach out to people who engaged on launch day for testimonials
  • Fix any issues reported on launch day
Show full SKILL.md (721 more words)Show less
Week 2 (Days 8-14)
  • Publish case study or early user story
  • Create interactive demo or product tour
  • Submit to relevant directories and lists (G2, Capterra, AlternativeTo)
  • Pitch guest posts to relevant blogs / newsletters
  • Run retargeting ads to launch day visitors who did not convert
Week 3-4 (Days 15-30)
  • Publish "roundup" email to full list with launch highlights + social proof
  • Create SEO-optimized content around launch keywords
  • Analyze full launch funnel: what worked, what did not, what to repeat
  • Document launch playbook for next time (what you would do differently)
  • Plan next feature launch using learnings

Launch Metrics

Pre-Launch Metrics
MetricTargetSource
Waitlist signups500+ for Tier 1Landing page
Email list growth10%+ increaseEmail platform
Social engagement on teaser content2x normalPlatform analytics
Launch Day Metrics
MetricTargetSource
Landing page visitors5x normal dailyGA4
Signup/conversion rate5-15% of visitorsProduct analytics
Social shares/mentions50+Social monitoring
Product Hunt rankTop 5Product Hunt
Post-Launch Metrics (30 day)
MetricTargetSource
Total signups attributed to launch2-5x monthly averageAttribution
Activation rate of launch signupsMatch or exceed normal cohortProduct analytics
Press/blog mentions3+ organic mentionsGoogle Alerts
SEO keyword rankingsRanking for launch keywordsSearch console

Proactive Triggers

  • Feature ship date mentioned with no marketing plan: immediately ask about launch strategy
  • Waitlist or early access mentioned: design the full phased funnel, not just a landing page
  • Product Hunt considered: trigger the full PH playbook with the 4-week timeline
  • Post-launch silence: suggest momentum content if nothing published after day 3
  • Pricing change planned: treat it as a Tier 2 launch opportunity

SkillUse When
email-sequenceBuilding launch announcement and post-launch onboarding sequences
social-media-managerCoordinating social strategy around the launch
content-creatorWriting blog posts and landing page copy for the launch
analytics-trackingSetting up tracking for launch conversion metrics
ab-test-setupTesting launch page variants

Troubleshooting

SymptomLikely CauseResolution
Launch day traffic spike but near-zero signupsLanding page value proposition unclear or CTA buriedAudit landing page: headline must answer "what is this and why should I care" in 5 seconds
Product Hunt submission gets below 50 upvotesNo community warm-up, poor listing assets, or launched on wrong dayFollow 4-week PH playbook; launch Tue-Thu; ensure gallery images show product, not marketing graphics
Post-launch momentum dies by day 3No post-launch content plan; team assumes launch day is the endExecute 30-day post-launch plan with follow-up content, testimonials, and retargeting
Email open rate below 15% on launch announcementSubject line not compelling or list not segmented by engagementA/B test subject lines; segment by engagement (send to most engaged first, then broader list)
Support team overwhelmed on launch dayNot briefed on new feature or FAQ not preparedInclude support briefing and FAQ creation in pre-launch checklist, minimum 1 week before launch
Metrics dashboard shows no data on launch dayTracking not configured or UTMs not applied to launch URLsInclude tracking verification in final QA checklist, test all conversion events in staging first

Success Criteria

  • Launch readiness score above 80% on readiness checker before go-live decision
  • Launch day traffic at least 5x normal daily traffic
  • Signup/conversion rate between 5-15% of launch day visitors
  • 50+ social shares/mentions on launch day
  • Product Hunt top 5 finish (for Tier 1 launches using PH channel)
  • Post-launch 30-day signups at 2-5x monthly average
  • Activation rate of launch cohort matches or exceeds normal cohort within 10%

Scope & Limitations

In Scope: Phased launch planning (Tier 1-4), ORB channel strategy, Product Hunt playbook, launch day execution checklists, post-launch momentum campaigns, waitlist management, launch metrics tracking, launch readiness assessment.

Out of Scope: Product development and feature readiness (engineering responsibility), pricing strategy (see marketing-strategy-pmm skill), ongoing marketing operations (see marketing-ops skill), press and media relationship building (PR function).

Limitations: Launch success depends on product-market fit — no launch strategy compensates for a product that does not solve a real problem. Product Hunt effectiveness varies by product category; B2C and developer tools typically perform better than enterprise B2B. Post-launch metrics require 30 days minimum for meaningful assessment.


Scripts

ScriptPurposeUsage
scripts/launch_readiness_checker.pyAssess go/no-go readiness across positioning, assets, channels, team, trackingpython scripts/launch_readiness_checker.py checklist.json --tier 1
scripts/launch_timeline_generator.pyGenerate week-by-week launch timeline with tasks and ownerspython scripts/launch_timeline_generator.py --date 2026-04-15 --tier 1
scripts/launch_metrics_tracker.pyTrack actual vs target metrics across pre-launch, launch day, and post-launchpython scripts/launch_metrics_tracker.py metrics.json --demo

© borghei, 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 3 other files (scripts) in marketing/launch-strategy of borghei/Claude-Skills.

  • SKILL.md
  • scripts/launch_metrics_tracker.py
  • scripts/launch_readiness_checker.py
  • scripts/launch_timeline_generator.py

Open the folder on GitHubat commit c9a1487

Compare with similar skills

Launch Strategy 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.

Launch Strategy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Launch Strategy this skillborghei/Claude-Skills874—~3.9kAutomated safety check: PassMIT
Getxapi ConnectLeoYeAI/openclaw-marketing-skills1k1 repos~715Automated safety check: PassCustom licence
Technical Launch Plannerjamesrochabrun/skills2151 repos~3.8kAutomated safety check: PassMIT
ProducthuntReScienceLab/opc-skills1.8k—~467Automated safety check: PassApache-2.0
Micro SaaS Launchernicepkg/auto-company1927 repos~1.3kAutomated safety check: PassNone
Amazon Competitor Monitoringnexscope-ai/Amazon-Skills7351 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • 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
  • Technical Launch Planner

    jamesrochabrun/skills

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

    215 GitHub starsUsed in 1 repo~3.8k 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.

    192 GitHub starsUsed in 7 repos~1.3k tokens
    Marketing & SEOAuto-check passed
  • Amazon Competitor Monitoring

    nexscope-ai/Amazon-Skills

    Amazon competitor monitoring and competitive intelligence for sellers.

    735 GitHub starsUsed in 1 repo~1.6k tokens
    Marketing & SEOAuto-check passed
  • Producthunt

    FoundDream/miniclawd

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

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

More from borghei/Claude-Skills

All 364 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    874 GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    874 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    874 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    874 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    874 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    874 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Launch Strategy

What does Launch Strategy do?

Plan and execute product launches and feature announcements: phased plans (alpha, beta, GA), channel strategy, Product Hunt playbooks, and post-launch momentum. Launch Strategy is an agent skill from borghei/Claude-Skills. Plan and execute product launches and feature announcements: phased plans (alpha, beta, GA), channel strategy, Product Hunt playbooks, and post-launch momentum.

When should I use Launch Strategy?

Launch Strategy fits situations like: launching a new product; planning a Product Hunt launch.

How do I install Launch Strategy in Claude Code?

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

How do I install Launch Strategy in Codex?

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

Can I use Launch Strategy 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 borghei/Claude-Skills --skill launch-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/launch-strategy, .gemini/skills/launch-strategy, .github/skills/launch-strategy and .opencode/skills/launch-strategy in your project.

What does Launch Strategy need to run?

Going by SKILL.md and its folder, Launch Strategy needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Launch Strategy 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 Launch Strategy 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Launch Strategy use?

Launch Strategy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Launch Strategy use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Launch Strategy?

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

Who maintains Launch Strategy?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 874 GitHub stars. The repository holds 364 skills in this directory. The repository was last updated on October 7, 2026.

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