Marketing Plan
Nexus-JPF/note-companion
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
A skill your agent uses when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch…
Install 59 Go To Market Global
$ npx skills add minhnv0807/ai-business-skills --skill 59-go-to-market-global -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install minhnv0807/ai-business-skills 59-go-to-market-global --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/minhnv0807/ai-business-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/en/59-go-to-market-global .claude/skills/59-go-to-market-global && 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 "59-go-to-market-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/59-go-to-market-global into .claude/skills/59-go-to-market-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "59-go-to-market-global", 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/minhnv0807/ai-business-skills/tree/master/skills/en/59-go-to-market-globalType 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 minhnv0807/ai-business-skills --skill 59-go-to-market-global -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install minhnv0807/ai-business-skills 59-go-to-market-global --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/en/59-go-to-market-global .agents/skills/59-go-to-market-global && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "59-go-to-market-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/59-go-to-market-global into .agents/skills/59-go-to-market-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "59-go-to-market-global", 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 minhnv0807/ai-business-skills --skill 59-go-to-market-global -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install minhnv0807/ai-business-skills 59-go-to-market-global --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/en/59-go-to-market-global .cursor/skills/59-go-to-market-global && 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 "59-go-to-market-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/59-go-to-market-global into .cursor/skills/59-go-to-market-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "59-go-to-market-global", 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/minhnv0807/ai-business-skills.git --path skills/en/59-go-to-market-global--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 minhnv0807/ai-business-skills --skill 59-go-to-market-global -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install minhnv0807/ai-business-skills 59-go-to-market-global --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/en/59-go-to-market-global .gemini/skills/59-go-to-market-global && 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 "59-go-to-market-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/59-go-to-market-global into .gemini/skills/59-go-to-market-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "59-go-to-market-global", 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 minhnv0807/ai-business-skills 59-go-to-market-globalInstalls 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 minhnv0807/ai-business-skills --skill 59-go-to-market-global -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/en/59-go-to-market-global .github/skills/59-go-to-market-global && 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 "59-go-to-market-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/59-go-to-market-global into .github/skills/59-go-to-market-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "59-go-to-market-global", 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 minhnv0807/ai-business-skills --skill 59-go-to-market-global -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install minhnv0807/ai-business-skills 59-go-to-market-global --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/minhnv0807/ai-business-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/en/59-go-to-market-global .opencode/skills/59-go-to-market-global && 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 "59-go-to-market-global" agent skill from https://github.com/minhnv0807/ai-business-skills/tree/master/skills/en/59-go-to-market-global into .opencode/skills/59-go-to-market-global/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "59-go-to-market-global", 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.
Facts
- Skill name
59-go-to-market-global- GitHub stars
- 609
- Token cost
- ~2.8k tokens
- SKILL.md length
- 1,194 words
- Files
- 1
- Skills in repo
- 142
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch…
- Works in 6 steps: Choose the beachhead segment → Lock the offer and the launch message → Set channels by phase → …
- Course is going to market — beachhead segment selection
- SKILL.md covers Information gathering, Principles, Workflow and Output structure, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
59 Go To Market Global is an agent skill from minhnv0807/ai-business-skills. Use when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch, milestones, success metrics, and go or no-go criteria. Trigger on 'go-to-market', 'GTM plan', 'product launch plan', 'we are launching a new product', 'beachhead segment', 'how do we launch this course'. Also use when the user has a finished product and no route to the first customers. Not for — the day-by-day execution checklist, see…
Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Go-to-market strategy. The repository describes itself as: 138 bilingual AI marketing skills (69 VN + 69 Global) for Claude Code, OpenCode, Codex, VS Code. Four role SOP packs — content, design, performance, leader ops — plus strategy… The licence is MIT.
When your agent uses it
- Course is going to market — beachhead segment selection
- Launch messaging
- Channels by phase across pre-launch
- Success metrics
Example prompts
- “go-to-market”
- “GTM plan”
- “product launch plan”
- “/59-go-to-market-global”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 0360adc. 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 (its code samples are markdown).
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
59 Go To Market Global loads about 2.8k tokens when it runs. Until then it costs about 182 tokens; SKILL.md has 1,194 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.
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 minhnv0807/ai-business-skills at commit 0360adc, republished under its MIT licence (© minhnv0807). 1,194 words, ~2,808 tokens.
Download SKILL.mdSave it as
.claude/skills/59-go-to-market-global/SKILL.md (or your agent's skills folder).- name
- 59-go-to-market-global
- description
- Use when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch, milestones, success metrics, and go or no-go criteria. Trigger on 'go-to-market', 'GTM plan', 'product launch plan', 'we are launching a new product', 'beachhead segment', 'how do we launch this course'. Also use when the user has a finished product and no route to the first customers. Not for — the day-by-day execution checklist, see `60-launch-playbook-global`; the ongoing period plan, see `00-marketing-plan-global`; one campaign inside the launch, see `02-campaign-brief-global`; positioning first, see `58-positioning-global`.
- metadata.version
- 1.0.1
- metadata.category
- strategy
- license
- MIT
- triggers
- go-to-market, GTM plan, GTM strategy, product launch plan, launch plan, launching a new product, beachhead segment, new offer launch
- output
- File .md — full GTM plan: beachhead segment, launch message, channels by phase, pre-launch to post-launch timeline, milestones, go/no-go criteria
- related
- product-marketing-context-global, 58-positioning-global, 31-offer-design-global, 60-launch-playbook-global, 10-reverse-kpi-global, 61-budget-planning-global…
Go-To-Market Plan (Global)
A launch is not a one-day event. It is a three-phase process: prepare, launch, sustain. Failed launches usually are not caused by a weak product — they are caused by nobody knowing, nobody believing, and nobody buying at the right moment. Run
58-positioning-globaland31-offer-design-globalfirst to lock the message and the offer; run60-launch-playbook-globalafterwards for the detailed execution checklist.
Information gathering
Read .agents/product-marketing-context-global.md, the positioning doc, and the offer doc if available. If missing, ask up to 4 questions:
- What is being launched? Price, early-bird or bundle pricing, and any capacity limit.
- Who is the primary audience: who are they, where are they, what are they thinking? Do you already have a warm base (followers, email list, past customers)?
- Timeline and budget: exact launch date? Budget allocated to the launch?
- Team and competitors: who do you have (writer, designer, media buyer, agency)? Does a competitor already sell something similar, and how are they positioned?
Principles
- Never launch cold. Start warming the audience at least 2 weeks before launch — teasers, community seeding, email warm-up.
- Beachhead first, expand later. Pick one segment small enough to win and large enough to sustain you. Win there, then move to the next. Always plan from SOM (what you can actually reach in 3-6 months), never from TAM.
- One core message throughout. Every launch asset reflects the same message, taken from the positioning statement.
- Have a plan B. Launch day brings technical failures (page down, ad rejection, payment errors). Have the fallback ready in advance.
- No-go is a valid decision. Launching at the wrong time is worse than launching late. Only the leader decides go/no-go — never delegate it.
Workflow
1. Choose the beachhead segment
Score 2-3 candidate segments (1-5 per question, 45 max):
| Criteria group | Scoring questions |
|---|---|
| Market need | Is the pain clear and growing? Is search or discussion volume high? Is the market durable rather than a passing trend? |
| Competition | Are there large incumbents? Have they saturated the channels? Is there a niche nobody addresses clearly? |
| Reachability | Do you already have a fitting channel or list? Can you test it on a small budget? Can the buyer decide quickly? |
Decision: 30+ points means launch on this beachhead. 25-30 means reconsider or narrow further. Below 25 means revisit the product or the segment.
Signals of a high-value beachhead customer: high LTV, low churn, active referrals. Filter question: "If this product disappeared tomorrow, what would you do?" The more painful the answer, the better the segment.
2. Lock the offer and the launch message
Offer summary (from 31-offer-design-global):
| Item | Detail |
|---|---|
| Product name | |
| List price / early bird / bundle | |
| Sales window and capacity limit | |
| Guarantee | |
| USP — one sentence of difference |
Launch message hierarchy — 5 layers, used in this order inside every asset:
- Hook (pain or desire) > 2. Solution (why this product) > 3. Proof (evidence) > 4. Offer (exactly what they get) > 5. Urgency (why buy now).
Required audience insight: persona, pain point, desire, primary objection, buying trigger. In US/EU markets the dominant objection is usually credibility and reviews rather than price — plan proof accordingly.
3. Set channels by phase
| Channel | Phase | Content | KPI |
|---|---|---|---|
| Meta (Facebook + Instagram) | Pre + Launch | Teaser > announce > urgency | Reach, leads |
| TikTok | Pre + Launch | Hook video, testimonial, creator content | Views, CTR |
| Email + SMS (Klaviyo, Mailchimp, Attentive) | Pre + Launch | Warm-up sequence > offer > last call | Open rate, CVR |
| Community seeding (Reddit, Discord, Slack, niche forums) | Pre-launch | Problem-aware content, no offer reveal | Engagement, saved posts |
| Google Search / Shopping | Launch | High-intent and brand keywords | CVR, ROAS |
| Affiliates / partners / creators | Launch | Co-promotion with tracked links | Attributed revenue |
Selection rule: you need both a REACH channel (drives traffic) and a CONVERT channel (closes). One channel rarely does both. Prioritize where the beachhead already spends time and where you have a real advantage.
Show full SKILL.md (562 more words)Show less
4. Build the three-phase timeline
PRE-LAUNCH (T-4 to T-1 weeks):
| Week | Activity | Owner | Output |
|---|---|---|---|
| T-4 | Offer finalized, landing page live | Leader + dev | Page live, tracking verified |
| T-3 | Produce teaser content (3-5 pieces) | Content | Posts ready |
| T-2 | Start seeding and warm-audience ads | Content + performance | Engagement, custom audiences |
| T-1 | Email/SMS pre-launch sequence | Leader | Warm list |
| T-3 days | Ads built and verified, tracking checked | Media buyer | Campaigns in Paused state |
| T-1 day | Full funnel final check > go/no-go | Leader | GO decision |
LAUNCH WEEK:
| Day | Activity | Channel | Owner |
|---|---|---|---|
| D-day morning | Official announcement | All | Leader |
| D-day | Turn on BOFU ads | Meta, TikTok, Google | Media buyer |
| D+1 | Follow-up email to non-buying leads | Email/SMS | Leader |
| D+2 | Social proof — first customer reviews | Social | Writer |
| D+3 | Media buyer report > scale, hold, or cut | — | Leader |
| D+5 | Urgency push — remaining capacity or bonus deadline | All | Leader |
| D+7 | Close cart — final email and post | Email + social | Leader |
POST-LAUNCH (D+8 to D+14): compile results (revenue, leads, ROAS, CPA), collect customer feedback to improve the product and capture testimonials, run the team retrospective, and decide whether to convert the campaign to evergreen.
5. Milestones and go/no-go
| Milestone | Timing | Pass criteria |
|---|---|---|
| M1 — Offer + page ready | T-4 | Page live, tracking verified, offer locked (price, bonuses, deadline) |
| M2 — Audience warm | T-1 | Warm base large enough: [X] engagers / [Y] email subscribers / custom audience >= [Z] |
| M3 — Go/no-go | T-1 day | Passes the checklist below |
| M4 — Mid-launch check | D+3 | CPA within threshold, first orders landed |
| M5 — Close + retro | D+7 to D+14 | >= [X]% of target hit, retrospective complete |
Go/no-go checklist (T-1 day, leader signs off):
- Tracking fully working (pixel fires, server-side events, UTMs complete)
- Payment tested end to end (card, PayPal, and any wallet you accept)
- All links resolve, no 404s
- Offer copy correct (price, bonuses, deadline), and every claim substantiated
- Consent and privacy in place: cookie/consent banner, GDPR/CCPA notices, CAN-SPAM unsubscribe in every email
- Team confirmed ready, inbox coverage staffed across the relevant timezones
- Plan B documented for technical failure
Any missing item means NO-GO. Do not launch "roughly ready" and fix later.
6. Success metrics
| Metric | Target | How measured |
|---|---|---|
| Launch-week revenue | ||
| Orders / seats sold | ||
| CPL / CPA | ||
| ROAS | ||
| Email open rate | ||
| Landing page CVR |
Derive targets backwards from the revenue goal using 10-reverse-kpi-global — never set targets by feel. Benchmark against references/benchmarks-global.md for the relevant region and industry; a US launch and an SEA launch are not comparable at face value.
Output structure
File name: gtm-plan-[product-name]-[YYYYMMDD].md
# GTM Plan — [Product] — Launch [date]
## 1. Product and offer summary
| Name / price / early bird / capacity / guarantee / USP |
## 2. Beachhead segment
- SOM score: [X]/45 — decision:
- Persona + pain + desire + objection + trigger:
## 3. Positioning and messaging
- Core message (one sentence):
- Message hierarchy: Hook > Solution > Proof > Offer > Urgency
## 4. Channel plan by phase
| Channel | Phase | Content | KPI |
## 5. Timeline
[Pre-launch T-4 to T-1 | Launch week D-day to D+7 | Post-launch D+8 to D+14]
| Checkpoint | Activity | Owner | Output | Deadline |
## 6. Milestones and go/no-go
| Milestone | Timing | Criteria |
- Go/no-go checklist T-1:
## 7. Success metrics
| Metric | Target | How measured |
## 8. Plan B
| Failure scenario | Fallback |Related skills
58-positioning-global: run first — the launch core message comes from the positioning statement.31-offer-design-global: run first — the offer must be locked before GTM planning.10-reverse-kpi-global: derive lead and budget targets from the revenue goal.61-budget-planning-global: allocate the launch budget across phases.60-launch-playbook-global: run after — day-by-day execution, war room, escalation.02-campaign-brief-global: turn the GTM plan into briefs for content and performance.
Quality checklist
- Beachhead selected by SOM scoring, not by intuition
- Offer summary complete: price, early bird, capacity, guarantee, USP
- Message hierarchy has all 5 layers: Hook > Solution > Proof > Offer > Urgency
- Channels cover both REACH and CONVERT, each with a role per phase
- Audience warming starts at least 2 weeks before launch
- Timeline covers all three phases with one owner per task
- Milestones have concrete, measurable pass criteria
- Go/no-go checklist complete, including payment, consent, and claim substantiation — leader signs off
- Success metrics derived backwards from the revenue target
- Plan B covers at least 3 failure scenarios (page down, ad rejection, payment failure)
- A retrospective is scheduled after launch (
63-campaign-retrospective-global)
© minhnv0807, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/en/59-go-to-market-global of minhnv0807/ai-business-skills.
Open the folder on GitHubat commit 0360adc
Compare with similar skills
59 Go To Market Global 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 |
|---|---|---|---|---|---|---|
| 59 Go To Market Global this skillminhnv0807/ai-business-skills | 609 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Marketing PlanNexus-JPF/note-companion | 870 | 5 repos | ~5.2k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Designferdinandobons/startup-skill | 1.2k | — | ~8.1k | Automated safety check: Pass | MIT | |
| Jaredrhod Marketingjaredrhod/ai-marketing-skills | 282 | — | ~584 | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Traffic Acquisitionvivy-yi/xiaohongshu-skills | 481 | 1 repos | ~4k | Automated safety check: Pass | None |
Similar skills
Revenue Centric Design
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
Startup Design
ferdinandobons/startup-skill
Design, validate, and plan a startup from scratch. An agent skill from ferdinandobons/startup-skill.
Jaredrhod Marketing
jaredrhod/ai-marketing-skills
Run any marketing task the way jaredrhod actually runs it. An agent skill from jaredrhod/ai-marketing-skills.
Traffic Acquisition
vivy-yi/xiaohongshu-skills
A skill your agent uses when driving traffic to Xiaohongshu account from external sources, acquiring new followers beyond organic discovery, implementing multi-platform growth strategy, or scaling…
Amazon Product Research
nexscope-ai/Amazon-Skills
Comprehensive product research and opportunity analysis for Amazon sellers.
More from minhnv0807/ai-business-skills
All 142 skills in this repoDesign Master
minhnv0807/ai-business-skills
Handles eight kinds of marketing visual requests, from logos and campaign key visuals to infographics and quote graphics, by generating images or writing paste-ready prompts.
Offer Design
minhnv0807/ai-business-skills
Designs or repairs what a business sells, covering the promise, value stack, bonuses, guarantee, honest scarcity and a tiered ladder, rather than price or copy.
Global SEO Growth
minhnv0807/ai-business-skills
Covers six SEO layers for a website: crawl and index audit, local SEO, search-intent content, AI search visibility, schema markup and backlink or directory distribution.
B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
Community Seeding Plan
minhnv0807/ai-business-skills
Plans honest participation in outside communities such as Reddit, Discord and Facebook Groups, with a rules-based community list, roster, posts, replies and calendar.
Ad Conversion Tracking Setup
minhnv0807/ai-business-skills
Sets up and verifies conversion tracking before ad spend: Meta Pixel and CAPI, Google Ads, GA4, TikTok, server-side GTM, consent mode, UTMs and a pre-launch checklist.
Related
Categories
Questions about 59 Go To Market Global
What does 59 Go To Market Global do?
A skill your agent uses when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch…. 59 Go To Market Global is an agent skill from minhnv0807/ai-business-skills. Use when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch, milestones, success metrics, and go or no-go criteria.
When should I use 59 Go To Market Global?
59 Go To Market Global fits situations like: course is going to market — beachhead segment selection; launch messaging; channels by phase across pre-launch; success metrics.
How do I install 59 Go To Market Global in Claude Code?
Run `npx skills add minhnv0807/ai-business-skills --skill 59-go-to-market-global -a claude-code`. Or copy the skill folder (skills/en/59-go-to-market-global in minhnv0807/ai-business-skills) into .claude/skills/59-go-to-market-global in your project. Claude Code loads it when a task matches its description.
How do I install 59 Go To Market Global in Codex?
Run `npx skills add minhnv0807/ai-business-skills --skill 59-go-to-market-global -a codex`. Or copy the skill folder (skills/en/59-go-to-market-global in minhnv0807/ai-business-skills) into .agents/skills/59-go-to-market-global in your project. Codex loads it when a task matches its description.
Can I use 59 Go To Market Global 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 minhnv0807/ai-business-skills --skill 59-go-to-market-global -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/59-go-to-market-global, .gemini/skills/59-go-to-market-global, .github/skills/59-go-to-market-global and .opencode/skills/59-go-to-market-global in your project.
What does 59 Go To Market Global need to run?
SKILL.md names no scripts, command-line tools or credentials: 59 Go To Market Global is instructions for the agent only.
Does 59 Go To Market Global 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 59 Go To Market Global 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 59 Go To Market Global use?
59 Go To Market Global 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 59 Go To Market Global use?
About 2.8k tokens (SKILL.md is roughly 11k 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 59 Go To Market Global?
Skills that share tags, products or a category with 59 Go To Market Global: Marketing Plan (Nexus-JPF/note-companion, 870 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Design (ferdinandobons/startup-skill, 1.2k stars) and Jaredrhod Marketing (jaredrhod/ai-marketing-skills, 282 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains 59 Go To Market Global?
minhnv0807 (a GitHub user) maintains it in minhnv0807/ai-business-skills, which has 609 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on September 12, 2026.
Source: minhnv0807/ai-business-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.