Gingiris Go Global
Gingiris-1031/Competitor-analysis-tool
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization.
Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a…
Install Launch Plan
$ npx skills add indranilbanerjee/digital-marketing-pro --skill launch-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro launch-plan --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/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/launch-plan .claude/skills/launch-plan && 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-plan" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/launch-plan into .claude/skills/launch-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-plan", 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/indranilbanerjee/digital-marketing-pro/tree/main/skills/launch-planType 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 indranilbanerjee/digital-marketing-pro --skill launch-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro launch-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/launch-plan .agents/skills/launch-plan && 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-plan" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/launch-plan into .agents/skills/launch-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-plan", 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 indranilbanerjee/digital-marketing-pro --skill launch-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro launch-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/launch-plan .cursor/skills/launch-plan && 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-plan" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/launch-plan into .cursor/skills/launch-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-plan", 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/indranilbanerjee/digital-marketing-pro.git --path skills/launch-plan--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 indranilbanerjee/digital-marketing-pro --skill launch-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro launch-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/launch-plan .gemini/skills/launch-plan && 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-plan" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/launch-plan into .gemini/skills/launch-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-plan", 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 indranilbanerjee/digital-marketing-pro launch-planInstalls 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 indranilbanerjee/digital-marketing-pro --skill launch-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/launch-plan .github/skills/launch-plan && 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-plan" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/launch-plan into .github/skills/launch-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-plan", 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 indranilbanerjee/digital-marketing-pro --skill launch-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install indranilbanerjee/digital-marketing-pro launch-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/launch-plan .opencode/skills/launch-plan && 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-plan" agent skill from https://github.com/indranilbanerjee/digital-marketing-pro/tree/main/skills/launch-plan into .opencode/skills/launch-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "launch-plan", 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
launch-plan- GitHub stars
- 859
- Used in
- 1 other repo
- Token cost
- ~1.1k tokens
- SKILL.md length
- 423 words
- Files
- 1
- Skills in repo
- 162
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a…
- Works in 8 steps: Load brand context: Read… → Define launch tier (Tier 1 major, Tier 2… → Pre-launch phase (T-30 to T-1): Teaser… → …
- /digital-marketing-pro:launch-plan
- SKILL.md covers Purpose, Execution gate (MANDATORY —…, Input Required and Process, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Launch Plan is an agent skill from indranilbanerjee/digital-marketing-pro. Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a risk register, and KPIs per phase. Triggers on "/digital-marketing-pro:launch-plan", "plan our product launch", "launch playbook for the new feature", "what should launch week look like", "coordinate the rebrand rollout". Planning only: it performs no external action itself; any playbook step handed to an execution skill…
Its SKILL.md is about 1.1k 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 Product launch strategy and Operations and SOPs. The repository describes itself as: An open-source AI marketing operating system for strategy, SEO, AEO/GEO, paid media, content, CRM, and analytics - grounded in brand context, human approval, and verifiable… The licence is MIT.
When your agent uses it
- /digital-marketing-pro:launch-plan
- Plan our product launch
- Launch playbook for the new feature
- What should launch week look like
Example prompts
- “/digital-marketing-pro:launch-plan”
- “plan our product launch”
- “launch playbook for the new feature”
- “/launch-plan”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load…
- Define launch tier (Tier 1 major, Tier 2 moderate, Tier 3 minor) to calibrate effort
- Pre-launch phase (T-30 to T-1): Teaser content, audience building, press seeding, influencer outreach, email list warming, landing page…
- Launch phase (T-0 to T+3): Coordinated announcement across all channels, press release, email blast, social blitz, paid media activation…
- Post-launch phase (T+4 to T+30): Performance monitoring, user feedback collection, content follow-up, retargeting, optimization, case…
- Build detailed timeline with owners, deliverables, and deadlines per task
- Define success metrics per phase and overall launch KPIs
- Identify risks and build contingency plans
What it can do on your machine
Read from SKILL.md and the folder at commit 3343924. 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
Launch Plan loads about 1.1k tokens when it runs. Until then it costs about 186 tokens; SKILL.md has 423 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 indranilbanerjee/digital-marketing-pro at commit 3343924, republished under its MIT licence (© indranilbanerjee). 423 words, ~1,101 tokens.
Download SKILL.mdSave it as
.claude/skills/launch-plan/SKILL.md (or your agent's skills folder).- name
- launch-plan
- description
- Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a risk register, and KPIs per phase. Triggers on "/digital-marketing-pro:launch-plan", "plan our product launch", "launch playbook for the new feature", "what should launch week look like", "coordinate the rebrand rollout". Planning only: it performs no external action itself; any playbook step handed to an execution skill such as /digital-marketing-pro:launch-campaign or /digital-marketing-pro:send-email-campaign must pass that skill's own typed-yes approval gate first. Reads the brand profile, guidelines, templates, and agency SOPs.
- argument-hint
- [product-name]
- disable-model-invocation
- false
/digital-marketing-pro:launch-plan
Purpose
Build a comprehensive launch playbook that coordinates all marketing activities across three phases — pre-launch, launch, and post-launch — to maximize impact and sustain momentum.
Execution gate (MANDATORY — cannot be skipped)
This skill produces a launch playbook — it performs no external action itself, so it runs freely. The gate governs the handoff: before ANY step of this playbook is executed by a downstream execution skill (/digital-marketing-pro:launch-campaign, /digital-marketing-pro:launch-ad-campaign, /digital-marketing-pro:send-email-campaign, etc.), that skill presents its own Execution Summary and the user must type yes. Never proceed on ambiguous input, never auto-execute a playbook step, and never auto-retry a failed one.
Input Required
The user must provide (or will be prompted for):
- What is launching: Product, feature, service, rebrand, or event
- Launch date: Target date or date range
- Launch goals: Signups, revenue, coverage, awareness targets
- Target audience: Primary and secondary audiences for the launch
- Available channels: Which channels are active and resourced
- Budget: Dedicated launch budget (if any)
- Assets available: What already exists (product pages, demos, press materials, creative)
- Team: Who is involved and their roles
Process
- Load brand context: Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at~/.claude-marketing/brands/{slug}/guidelines/_manifest.json— if present, load restrictions and relevant category files. Check for custom templates at~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. - Define launch tier (Tier 1 major, Tier 2 moderate, Tier 3 minor) to calibrate effort
- Pre-launch phase (T-30 to T-1): Teaser content, audience building, press seeding, influencer outreach, email list warming, landing page, waitlist
- Launch phase (T-0 to T+3): Coordinated announcement across all channels, press release, email blast, social blitz, paid media activation, community engagement
- Post-launch phase (T+4 to T+30): Performance monitoring, user feedback collection, content follow-up, retargeting, optimization, case studies
- Build detailed timeline with owners, deliverables, and deadlines per task
- Define success metrics per phase and overall launch KPIs
- Identify risks and build contingency plans
Show full SKILL.md (80 more words)Show less
Output
A structured launch playbook containing:
- Launch overview with tier classification and success criteria
- Pre-launch checklist with timeline, deliverables, and owners
- Launch day runbook with hour-by-hour coordination plan
- Post-launch optimization plan with feedback loops
- Channel-by-channel activation plan with specific tactics
- Content and asset requirements list
- Risk register with contingency actions
- KPI dashboard with targets per phase
Agents Used
- marketing-strategist — Launch architecture, phasing, goal setting, channel coordination
- content-creator — Launch messaging, content assets, announcement copy
- pr-outreach — Media strategy, press materials, influencer seeding
© indranilbanerjee, 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/launch-plan of indranilbanerjee/digital-marketing-pro.
Open the folder on GitHubat commit 3343924
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in indranilbanerjee/digital-marketing-pro, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Launch Plan 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 Plan this skillindranilbanerjee/digital-marketing-pro | 859 | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Gingiris Go GlobalGingiris-1031/Competitor-analysis-tool | 110 | — | ~868 | Automated safety check: Pass | None | |
| 60 Launch Playbook Globalminhnv0807/ai-business-skills | 610 | — | ~3k | Automated safety check: Pass | MIT | |
| 60 Launch Playbookminhnv0807/ai-business-skills | 610 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Apqphashgraph-online/awesome-codex-plugins | 1.3k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Technical Launch Plannerjamesrochabrun/skills | 216 | 1 repos | ~3.8k | Automated safety check: Pass | MIT |
Similar skills
60 Launch Playbook Global
minhnv0807/ai-business-skills
A skill your agent uses when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room…
60 Launch Playbook
minhnv0807/ai-business-skills
Dung khi da co huong launch va can QUY TRINH chay cho khong vo tran — timeline T-30 den D+7, checklist tung bo phan content, design, ads, sales, CSKH; war-room ngay launch, escalation matrix va tieu…
Apqp
hashgraph-online/awesome-codex-plugins
Advanced Product Quality Planning (APQP) — plan and track a new product launch through all 5 phases, identify deliverables per phase, run gate reviews, and ensure quality outputs are complete before…
Technical Launch Planner
jamesrochabrun/skills
Plan and execute technical product launches for developer tools, APIs, and technical products.
Getxapi Connect
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
More from indranilbanerjee/digital-marketing-pro
All 162 skills in this repoAb Test Plan
indranilbanerjee/digital-marketing-pro
Design a statistically rigorous A/B or multivariate test plan — If/Then/Because hypothesis, control and variant specs, required sample size per variant (absolute vs relative MDE via…
Aeo Audit
indranilbanerjee/digital-marketing-pro
Audit how a brand appears across the 6 canonical AI answer surfaces — ChatGPT, Perplexity, Google AI Mode, AI Overviews, Gemini, Copilot — probing 10-25 queries into a numbered output bundle with…
Agent Readiness Audit
indranilbanerjee/digital-marketing-pro
Audit whether AI agents and AI crawlers can actually use a site — robots.txt rules per AI crawler token (OpenAI, Anthropic and Perplexity bots, Google-Extended, Applebot-Extended)…
Backlink Gap
indranilbanerjee/digital-marketing-pro
Find referring domains that link to your competitors but not to you, ranked by an outreach-priority score (0.40 DR + 0.25 link-overlap + 0.20 traffic + 0.15 topical relevance) — outputs a four-gate…
C2pa Metadata
indranilbanerjee/digital-marketing-pro
Embed a C2PA provenance manifest into an AI-generated marketing asset (PNG, JPG, WebP, GIF, TIFF, MP4, MOV, WebM, MP3, WAV, PDF) via scripts/embed-c2pa.py — produces a signed copy of the file…
Campaign Audit
indranilbanerjee/digital-marketing-pro
Inventory and score everything currently running for a brand across paid search, paid social, email, organic, SEO, AEO/GEO, CRM, and analytics — produces a dated audit document with a 4-tier triage…
Related
Categories
Questions about Launch Plan
What does Launch Plan do?
Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a…. Launch Plan is an agent skill from indranilbanerjee/digital-marketing-pro. Build a three-phase launch playbook — pre-launch (T-30), an hour-by-hour launch-day runbook, and post-launch optimization (T+30) — with per-task owners and deadlines, channel activation plans, a risk register, and KPIs per phase.
When should I use Launch Plan?
Launch Plan fits situations like: /digital-marketing-pro:launch-plan; plan our product launch; launch playbook for the new feature; what should launch week look like.
How do I install Launch Plan in Claude Code?
Run `npx skills add indranilbanerjee/digital-marketing-pro --skill launch-plan -a claude-code`. Or copy the skill folder (skills/launch-plan in indranilbanerjee/digital-marketing-pro) into .claude/skills/launch-plan in your project. Claude Code loads it when a task matches its description.
How do I install Launch Plan in Codex?
Run `npx skills add indranilbanerjee/digital-marketing-pro --skill launch-plan -a codex`. Or copy the skill folder (skills/launch-plan in indranilbanerjee/digital-marketing-pro) into .agents/skills/launch-plan in your project. Codex loads it when a task matches its description.
Can I use Launch Plan 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 indranilbanerjee/digital-marketing-pro --skill launch-plan -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-plan, .gemini/skills/launch-plan, .github/skills/launch-plan and .opencode/skills/launch-plan in your project.
What does Launch Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Launch Plan is instructions for the agent only.
Does Launch Plan 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 Plan 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 Launch Plan use?
Launch Plan 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 Launch Plan use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Plan?
Skills that share tags, products or a category with Launch Plan: Gingiris Go Global (Gingiris-1031/Competitor-analysis-tool, 110 stars), 60 Launch Playbook Global (minhnv0807/ai-business-skills, 610 stars), 60 Launch Playbook (minhnv0807/ai-business-skills, 610 stars) and Apqp (hashgraph-online/awesome-codex-plugins, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Launch Plan?
indranilbanerjee (a GitHub user) maintains it in indranilbanerjee/digital-marketing-pro, which has 859 GitHub stars. The repository holds 162 skills in this directory. The repository was last updated on October 4, 2026.
Source: indranilbanerjee/digital-marketing-pro on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.