Getxapi Connect
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
Plan and execute product launches and feature announcements: phased plans (alpha, beta, GA), channel strategy, Product Hunt playbooks, and post-launch momentum.
$ npx skills add borghei/Claude-Skills --skill launch-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills launch-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "launch-strategy" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/launch-strategy into .claude/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/marketing/launch-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill launch-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills launch-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/launch-strategy .agents/skills/launch-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "launch-strategy" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/launch-strategy into .agents/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill launch-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills launch-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/launch-strategy .cursor/skills/launch-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "launch-strategy" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/launch-strategy into .cursor/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path marketing/launch-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill launch-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills launch-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/launch-strategy .gemini/skills/launch-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "launch-strategy" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/launch-strategy into .gemini/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills launch-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill launch-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/launch-strategy .github/skills/launch-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "launch-strategy" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/launch-strategy into .github/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill launch-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills launch-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/launch-strategy .opencode/skills/launch-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "launch-strategy" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/launch-strategy into .opencode/skills/launch-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
launch-strategyPlan 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. 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.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit c9a1487. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from borghei/Claude-Skills at commit c9a1487, republished under its MIT licence (© borghei). 1,839 words, ~3,893 tokens.
.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.Category: Marketing Tags: product launch, feature release, Product Hunt, go-to-market, launch playbook, announcement strategy
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.
Before planning the launch, confirm these inputs. If any is unknown or vague, ASK — do not assume:
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.
Not every release deserves the same effort. Classify first.
| Tier | What It Is | Marketing Effort | Examples |
|---|---|---|---|
| Tier 1: Major Launch | New product, major pivot, rebrand | 4-8 weeks prep, all channels | New product launch, platform launch |
| Tier 2: Feature Launch | Significant new capability | 2-4 weeks prep, owned + select channels | Major feature, integration, new plan |
| Tier 3: Update | Improvement to existing feature | 1 week prep, owned channels only | Performance improvement, UI refresh |
| Tier 4: Changelog | Bug fix, minor improvement | Same day, changelog only | Bug 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.
Positioning & Messaging
Positioning Template:
For [target audience] who [need/pain point],
[product/feature] is the [category]
that [key benefit].
Unlike [alternatives],
we [key differentiator].Asset Checklist:
Audience Warming
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"The ORB Channel Framework
Categorize every launch channel as Owned, Rented, or Borrowed:
| Channel Type | Definition | Examples | Control |
|---|---|---|---|
| Owned | You control the audience | Email list, blog, product (in-app), changelog | Full |
| Rented | You pay for access | Paid ads, sponsorships, promoted posts | High (while paying) |
| Borrowed | You earn access through others | Press, influencer mentions, community shares, Product Hunt | Low |
Channel Strategy by Tier:
| Channel | Tier 1 | Tier 2 | Tier 3 |
|---|---|---|---|
| Email (full list) | Yes | Yes | Segment only |
| Blog post | Long-form | Short-form | Changelog |
| Social media | Multi-post campaign | Single announcement | Brief mention |
| In-app notification | Yes | Yes | Optional |
| Product Hunt | If applicable | No | No |
| Press / media | Targeted pitches | No | No |
| Paid amplification | Budget allocated | Small budget | No |
| Partner co-marketing | If applicable | No | No |
| Community posts | HN, Reddit, Discord | HN maybe | No |
T-2 hours:
T-0 (Launch):
T+2 hours:
T+6 hours:
End of Day:
Product Hunt is a launch channel, not a launch strategy. It works best when combined with the full ORB approach.
Week -4: Preparation
Week -1: Pre-Launch
Launch Day (12:01 AM PT)
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!| Outcome | What It Means |
|---|---|
| Top 5 of the day | Strong launch, badge, homepage visibility |
| Top 10 of the day | Good launch, still gets homepage traffic for 24h |
| Below top 10 | Minimal PH-specific value, but launch content still works elsewhere |
| Product of the week/month | Significant ongoing PH traffic |
The launch is not over on day one. Most of the value comes from sustained post-launch activity.
| Metric | Target | Source |
|---|---|---|
| Waitlist signups | 500+ for Tier 1 | Landing page |
| Email list growth | 10%+ increase | Email platform |
| Social engagement on teaser content | 2x normal | Platform analytics |
| Metric | Target | Source |
|---|---|---|
| Landing page visitors | 5x normal daily | GA4 |
| Signup/conversion rate | 5-15% of visitors | Product analytics |
| Social shares/mentions | 50+ | Social monitoring |
| Product Hunt rank | Top 5 | Product Hunt |
| Metric | Target | Source |
|---|---|---|
| Total signups attributed to launch | 2-5x monthly average | Attribution |
| Activation rate of launch signups | Match or exceed normal cohort | Product analytics |
| Press/blog mentions | 3+ organic mentions | Google Alerts |
| SEO keyword rankings | Ranking for launch keywords | Search console |
| Skill | Use When |
|---|---|
| email-sequence | Building launch announcement and post-launch onboarding sequences |
| social-media-manager | Coordinating social strategy around the launch |
| content-creator | Writing blog posts and landing page copy for the launch |
| analytics-tracking | Setting up tracking for launch conversion metrics |
| ab-test-setup | Testing launch page variants |
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Launch day traffic spike but near-zero signups | Landing page value proposition unclear or CTA buried | Audit landing page: headline must answer "what is this and why should I care" in 5 seconds |
| Product Hunt submission gets below 50 upvotes | No community warm-up, poor listing assets, or launched on wrong day | Follow 4-week PH playbook; launch Tue-Thu; ensure gallery images show product, not marketing graphics |
| Post-launch momentum dies by day 3 | No post-launch content plan; team assumes launch day is the end | Execute 30-day post-launch plan with follow-up content, testimonials, and retargeting |
| Email open rate below 15% on launch announcement | Subject line not compelling or list not segmented by engagement | A/B test subject lines; segment by engagement (send to most engaged first, then broader list) |
| Support team overwhelmed on launch day | Not briefed on new feature or FAQ not prepared | Include support briefing and FAQ creation in pre-launch checklist, minimum 1 week before launch |
| Metrics dashboard shows no data on launch day | Tracking not configured or UTMs not applied to launch URLs | Include tracking verification in final QA checklist, test all conversion events in staging first |
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.
| Script | Purpose | Usage |
|---|---|---|
scripts/launch_readiness_checker.py | Assess go/no-go readiness across positioning, assets, channels, team, tracking | python scripts/launch_readiness_checker.py checklist.json --tier 1 |
scripts/launch_timeline_generator.py | Generate week-by-week launch timeline with tasks and owners | python scripts/launch_timeline_generator.py --date 2026-04-15 --tier 1 |
scripts/launch_metrics_tracker.py | Track actual vs target metrics across pre-launch, launch day, and post-launch | python 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
SKILL.md and 3 other files (scripts) in marketing/launch-strategy of borghei/Claude-Skills.
Open the folder on GitHubat commit c9a1487
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Launch Strategy this skillborghei/Claude-Skills | 874 | — | ~3.9k | Automated safety check: Pass | MIT | |
| Getxapi ConnectLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~715 | Automated safety check: Pass | Custom licence | |
| Technical Launch Plannerjamesrochabrun/skills | 215 | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| ProducthuntReScienceLab/opc-skills | 1.8k | — | ~467 | Automated safety check: Pass | Apache-2.0 | |
| Micro SaaS Launchernicepkg/auto-company | 192 | 7 repos | ~1.3k | Automated safety check: Pass | None | |
| Amazon Competitor Monitoringnexscope-ai/Amazon-Skills | 735 | 1 repos | ~1.6k | Automated safety check: Pass | MIT |
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
jamesrochabrun/skills
Plan and execute technical product launches for developer tools, APIs, and technical products.
ReScienceLab/opc-skills
Search and retrieve content from Product Hunt. An agent skill from ReScienceLab/opc-skills.
nicepkg/auto-company
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software.
nexscope-ai/Amazon-Skills
Amazon competitor monitoring and competitive intelligence for sellers.
FoundDream/miniclawd
Discover trending tech products, apps, and tools from Product Hunt.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
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.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Categories
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.
Launch Strategy fits situations like: launching a new product; planning a Product Hunt launch.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.