Agent skill

Intl Expansion

International market expansion strategy for scaling companies.

Install Intl Expansion

skills CLI

$ npx skills add borghei/Claude-Skills --skill intl-expansion -a claude-code

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

GitHub CLI

$ gh skill install borghei/Claude-Skills intl-expansion --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/c-level-advisor/intl-expansion .claude/skills/intl-expansion && 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/

Paste into Claude Code

Install the "intl-expansion" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/intl-expansion into .claude/skills/intl-expansion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intl-expansion", 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

$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/intl-expansion

Type 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.

skills CLI

$ npx skills add borghei/Claude-Skills --skill intl-expansion -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills intl-expansion --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-advisor/intl-expansion .agents/skills/intl-expansion && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "intl-expansion" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/intl-expansion into .agents/skills/intl-expansion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intl-expansion", 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.

skills CLI

$ npx skills add borghei/Claude-Skills --skill intl-expansion -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills intl-expansion --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-advisor/intl-expansion .cursor/skills/intl-expansion && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "intl-expansion" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/intl-expansion into .cursor/skills/intl-expansion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intl-expansion", 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

$ gemini skills install https://github.com/borghei/Claude-Skills.git --path c-level-advisor/intl-expansion

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add borghei/Claude-Skills --skill intl-expansion -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills intl-expansion --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-advisor/intl-expansion .gemini/skills/intl-expansion && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "intl-expansion" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/intl-expansion into .gemini/skills/intl-expansion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intl-expansion", 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.

GitHub CLI

$ gh skill install borghei/Claude-Skills intl-expansion

Installs 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).

skills CLI

$ npx skills add borghei/Claude-Skills --skill intl-expansion -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-advisor/intl-expansion .github/skills/intl-expansion && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "intl-expansion" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/intl-expansion into .github/skills/intl-expansion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intl-expansion", 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.

skills CLI

$ npx skills add borghei/Claude-Skills --skill intl-expansion -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install borghei/Claude-Skills intl-expansion --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-advisor/intl-expansion .opencode/skills/intl-expansion && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "intl-expansion" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/intl-expansion into .opencode/skills/intl-expansion/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intl-expansion", 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: intl-expansion
GitHub stars: 886
Token cost: ~5.2k tokens
SKILL.md length: 1,954 words
Files: 4 (incl. scripts)
Skills in repo: 354
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

International market expansion strategy for scaling companies.

Expanding to new countries
SKILL.md covers Keywords, Clarify First, Decision Sequence and Market Selection Framework, plus 9 more sections
Runs Python scripts from its folder; calls python
Evaluating international markets

What it does

Intl Expansion is an agent skill from borghei/Claude-Skills. International market expansion strategy for scaling companies. Use when expanding to new countries, evaluating international markets, planning localization, building regional teams, or assessing regulatory requirements by region.

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

It sits in Frontend & Design, covering Internationalization, Regulatory compliance and Go-to-market 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

Expanding to new countries
Evaluating international markets
Planning localization
Building regional teams

Example prompts

“/intl-expansion”

Requirements

Python 3

What it can do on your machine

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

Intl Expansion loads about 5.2k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 1,954 words of instructions outside code blocks.

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

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 4a698e8, republished under its MIT licence (© borghei). 1,954 words, ~5,172 tokens.

Download SKILL.mdSave it as .claude/skills/intl-expansion/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: intl-expansion
description: International market expansion strategy for scaling companies. Use when expanding to new countries, evaluating international markets, planning localization, building regional teams, or assessing regulatory requirements by region.
license: MIT + Commons Clause
metadata.version: 2.0.0
metadata.author: borghei
metadata.category: c-level
metadata.domain: international-strategy
metadata.updated: 2026-03-09
metadata.frameworks: market-selection, entry-mode-evaluation, localization-framework, regional-compliance, gtm-adaptation, launch-planning
metadata.triggers: international expansion, market entry, localization, go-to-market, GTM, regional strategy, international markets, market selection, cross-border, global…

International Expansion

Frameworks for expanding into new markets: selection, entry mode, localization, regulatory compliance, GTM adaptation, and execution. Every expansion is a bet -- this skill structures the bet to maximize signal before committing resources.

Keywords

international expansion, market entry, localization, go-to-market, GTM, regional strategy, international markets, market selection, cross-border, global expansion, EMEA, APAC, LATAM, data residency, local entity, regional hiring, currency, payment methods, regulatory compliance

Clarify First

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

Which deliverable is needed (market scoring, entry-mode recommendation, localization plan, regulatory map, pricing, or launch plan) — each follows a different framework
The target market(s) under consideration — regional regulatory, cultural-distance, and pricing guidance is country-specific
Existing traction in that market (inbound demand, current ARR from it) — the entry-mode graduation path is gated on revenue thresholds; pull vs. push changes the go/no-go
Product type and home-market model (B2B SaaS vs. other; PLG vs. sales-led) — the frameworks are tuned for B2B SaaS and the GTM adaptation depends on the current model

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.

Decision Sequence

Market Selection --> Entry Mode --> Regulatory Assessment --> Localization Plan
  --> GTM Strategy --> Team Structure --> Launch --> Scale or Exit

Market Selection Framework

Scoring Matrix

Factor	Weight	Assessment Method
Market size (addressable)	25%	TAM in target segment, willingness to pay, growth rate
Competitive intensity	20%	Incumbent strength, number of alternatives, market gaps
Regulatory complexity	20%	Barriers to entry, compliance cost, timeline to launch
Cultural distance	15%	Language, business practices, buying behavior, sales cycle
Existing traction	10%	Inbound demand, existing customers, partnership signals
Operational complexity	10%	Time zones, infrastructure, payment systems, talent pool

Market Selection Decision Tree

START: Considering a new market
  |
  v
[Is there existing pull from this market?]
  |
  +-- YES (inbound demand, existing customers) --> Strong signal. Score and proceed.
  |
  +-- NO  --> [Is there a strategic reason to enter?]
              |
              +-- YES (competitor pressure, investor expectation) --> Score carefully.
              |    Be honest about push vs. pull.
              |
              +-- NO  --> Do not enter. Focus on existing markets.

Regional Quick Reference

Region	Market Size	Regulatory Complexity	Cultural Distance (from US)	Key Considerations
UK/Ireland	Large	Medium	Low	English-speaking, strong tech ecosystem, Brexit considerations
DACH (DE/AT/CH)	Large	High	Medium	Data privacy strict, enterprise-heavy, German language needed
Nordics	Medium	Medium	Low-Medium	Tech-savvy, English common, smaller market size
France	Large	High	Medium	Language required, strong labor laws, cultural nuances
Benelux	Medium	Medium	Low-Medium	Multilingual, hub for European operations
Japan	Very Large	Very High	High	Requires local partner, long sales cycles, relationship-heavy
Singapore/SEA	Medium-Large	Medium	Medium	Regional hub, English common, diverse sub-markets
Australia/NZ	Medium	Low	Low	English-speaking, similar business culture, timezone challenge
Brazil	Large	Very High	High	Portuguese required, complex tax, large opportunity
India	Very Large	High	Medium	Price-sensitive, English common, massive scale potential

Entry Mode Evaluation

Entry Mode Comparison

Mode	Investment	Control	Risk	Speed	Best For
Remote sales (export)	Low ($10-50K)	Low	Low	Fast	Testing demand before committing
Partnership/reseller	Medium ($50-200K)	Medium	Medium	Medium	Markets with strong local requirements
Local hire (no entity)	Medium ($100-300K)	Medium-High	Medium	Medium	First boots on the ground
Full entity (subsidiary)	High ($200K-1M)	Full	High	Slow	Major markets with proven demand
Acquisition	Highest ($500K+)	Full	Highest	Fast (if done well)	Immediate market presence + customer base

Entry Mode Decision Tree

START: Market selected, entry mode needed
  |
  v
[Do you have existing customers in this market?]
  |
  +-- NO  --> Start with Remote Sales
  |            Test demand for 3-6 months
  |            If revenue > $200K ARR from market --> Upgrade
  |
  +-- YES --> [Revenue from this market > $500K ARR?]
              |
              +-- NO  --> Remote Sales or Local Hire (EOR)
              |
              +-- YES --> [Does the market require local entity?]
                          |
                          +-- YES (regulatory requirement) --> Full Entity
                          +-- NO  --> [Revenue trajectory?]
                                      |
                                      +-- Growing fast --> Local Hire, plan Entity
                                      +-- Stable --> Partnership or Local Hire

Default Graduation Path

Stage 1: Remote Sales ($0-200K ARR from market)
  - Sell remotely from HQ
  - No local presence
  - Test messaging, pricing, ICP fit

Stage 2: Local Hire ($200K-500K ARR)
  - 1-2 people via EOR (Employer of Record)
  - Sales + CS representative
  - No legal entity yet

Stage 3: Local Entity ($500K-2M ARR)
  - Establish legal entity
  - Hire local team (3-8 people)
  - Local banking, contracts, compliance

Stage 4: Regional Hub ($2M+ ARR)
  - Full local team (10+ people)
  - Regional leadership
  - Market-specific product features

Localization Framework

Product Localization

Layer	Must Have	Nice to Have	Cost Impact
Language (UI)	Full translation of core product	Marketing site in local language	$20-50K initial
Currency	Display and charge in local currency	Multi-currency invoicing	$10-30K engineering
Payment methods	Credit card + local preferred method	All local payment methods	$5-20K per method
Data formats	Date, time, number, address	Local units (km, kg, etc.)	$5-15K engineering
Data residency	If legally required	If customer-required	$50-200K infrastructure
Cultural adaptation	Avoid cultural missteps	Full cultural optimization	Variable

GTM Localization

Element	Approach	Common Mistake
Messaging	Adapt value proposition for local pain points	Copy-paste from home market
Channel strategy	Research local channels (may differ significantly)	Assume same channels work everywhere
Case studies	Local customer references essential	Only showing US/UK case studies
Partnerships	Local integrations and ecosystem	Ignoring local tech ecosystem
Events	Regional conferences and meetups	Only attending global events
Content/SEO	Local language content, local domain	English-only content for non-English market

Operations Localization

Area	Key Considerations
Legal entity	Type, timeline, cost, ongoing compliance
Tax compliance	VAT/GST registration, transfer pricing, withholding
Employment law	At-will vs. strong protections, notice periods, benefits
Customer support	Hours, language, channels
Banking	Local bank account, payment processing
Insurance	Local requirements for entity and employees

Regulatory Compliance by Region

Data Privacy Requirements

Regulation	Region	Key Requirements	Penalty
GDPR	EU/EEA	Consent, data minimization, DPO, breach notification	Up to 4% annual revenue
UK GDPR	UK	Similar to GDPR, separate registration	Up to 4% annual revenue
LGPD	Brazil	Similar to GDPR, DPO required	Up to 2% revenue (capped R$50M)
PIPL	China	Data localization, consent, cross-border assessment	Up to 5% annual revenue
PIPA	South Korea	Consent, purpose limitation, data localization for some	Up to 3% of related revenue
APPI	Japan	Consent, purpose specification, cross-border transfer rules	Criminal penalties possible
Privacy Act	Australia	APPs, breach notification, cross-border transfer rules	Increasing penalties

Data Residency Decision Tree

START: Expanding to new region
  |
  v
[Does local law require data residency?]
  |
  +-- YES (e.g., certain China, Russia, some industry regs)
  |     --> Local hosting mandatory. Budget for local infrastructure.
  |
  +-- NO  --> [Do target customers require local data hosting?]
              |
              +-- YES (common in enterprise, government, healthcare)
              |     --> Offer regional hosting as option. Major sales enabler.
              |
              +-- NO  --> Global hosting acceptable. Document your data practices.

International GTM Strategy

Pricing Strategy by Market

Approach	When	Example
Global uniform pricing	Simple product, global ICP	Same price everywhere
PPP-adjusted	Consumer product, price-sensitive markets	Lower prices in developing markets
Market-specific	Different value perception by market	Higher in markets with less competition
Local currency, global rate	B2B SaaS, enterprise	Price in local currency, USD-equivalent

Sales Model Adaptation

Market Characteristic	Sales Model Adjustment
High-trust culture (Nordics, Japan)	Longer relationship building, more proof points
Price-sensitive market (India, LATAM)	Flexible pricing, usage-based options
Channel-dominant (Japan, Middle East)	Partner-led sales, local reseller required
Enterprise-heavy (DACH, France)	On-premises option, compliance documentation
PLG-friendly (US, UK, Nordics)	Self-serve with local payment methods

Common Mistakes

Mistake	Why It Happens	Prevention
Entering too many markets at once	FOMO, board pressure	Maximum 1-2 new markets per year
Copy-paste GTM from home market	Assuming buyers are the same	Research local buying behavior first
Underestimating regulatory cost	"We'll figure it out"	Regulatory assessment BEFORE committing
Hiring local team too early	Optimism about demand	Prove $200K+ ARR from market first
Wrong pricing (just converting)	Laziness or assumption	Research local willingness to pay
Ignoring local competition	Focused on global competitors	Local players often dominate segments
Underestimating cultural distance	"Business is business everywhere"	Invest in local market expertise
No exit criteria	Sunk cost fallacy	Define revenue milestone to hit within 12 months

Launch Checklist

Pre-Launch (T-90 days to T-30 days)

Category	Item	Status
Legal	Entity established (if needed)	[ ]
Legal	Local contracts reviewed by local counsel	[ ]
Compliance	Data privacy requirements met	[ ]
Compliance	Tax registration completed	[ ]
Product	Core product localized (language, currency)	[ ]
Product	Local payment methods integrated	[ ]
Sales	ICP defined for local market	[ ]
Sales	Pricing set for local market	[ ]
Marketing	Local messaging and positioning	[ ]
Marketing	Local case studies (or adjacent)	[ ]
People	First local hire identified	[ ]
Support	Support coverage plan for timezone	[ ]

Launch (T-0 to T+90 days)

Week	Focus	Success Metric
1-4	Activate local presence, first outreach	20+ qualified conversations
5-8	First pipeline built, first deals	5+ opportunities in pipeline
9-12	First customers closed, iterate	2+ closed deals, product feedback

Exit Criteria

If these are not met within 12 months, evaluate exit:

Metric	Minimum Threshold
Pipeline generated	$500K+
Revenue closed	$200K+ ARR
Customer satisfaction	NPS > 20 in market
Cost of entry	< 3x first-year revenue

Show full SKILL.md (800 more words)Show less

Red Flags

Entering a market because a board member suggested it (without data)
No local market research before committing resources
Pricing set by currency conversion, not local value research
Hiring a country manager before proving demand
Legal entity established before $200K ARR from market
Ignoring local data privacy requirements
Same marketing messaging as home market
No exit criteria defined before entry

Integration with C-Suite

Role	Contribution to Expansion
CEO (`ceo-advisor`)	Market selection decision, strategic commitment
CFO (`cfo-advisor`)	Investment sizing, ROI modeling, entity structure, tax
CRO (`cro-advisor`)	Revenue targets, sales model adaptation, pricing
CMO (`cmo-advisor`)	Positioning, channel strategy, local brand
CPO (`cpo-advisor`)	Localization roadmap, feature priorities
CTO (`cto-advisor`)	Infrastructure, data residency, scaling
CHRO (`chro-advisor`)	Local hiring, employment law, compensation
CISO (`ciso-advisor`)	Data privacy, regulatory compliance
COO (`coo-advisor`)	Operations setup, process adaptation

Output Artifacts

Request	Deliverable
"Should we expand to [market]?"	Market scoring analysis with recommendation
"How should we enter [market]?"	Entry mode recommendation with graduation path
"Localization plan for [market]"	Product + GTM + operations localization checklist
"Regulatory requirements for [region]"	Compliance checklist with timeline and cost
"International pricing strategy"	Market-specific pricing recommendation
"Launch plan for [market]"	90-day launch plan with milestones and exit criteria

Troubleshooting

Problem	Likely Cause	Resolution
Market scores high but pipeline generation is near zero	Market sizing based on TAM not SAM; ICP not validated locally	Re-score using serviceable addressable market; run 20 discovery calls before committing further resources
Local hire producing no results after 3 months	Wrong profile (too senior or too junior), insufficient HQ support, or wrong ICP	Assess whether hire has local market expertise AND startup mindset; ensure HQ provides enablement materials and responsive support
Regulatory compliance taking 2x longer than planned	Underestimated complexity; no local legal counsel engaged early	Engage local legal counsel in pre-launch phase (T-90); add 50% buffer to all regulatory timelines
Localization costs spiraling beyond budget	Scope creep from "nice to have" to "must have"; no phased approach	Apply localization framework layers strictly: Must Have first, Nice to Have only after revenue proves market
Pricing not competitive in new market	Direct currency conversion without local willingness-to-pay research	Conduct 10+ pricing conversations with local prospects; consider PPP adjustment or market-specific pricing tier
Partnership/reseller underperforming	Partner not incentivized properly or wrong partner profile	Review partner selection criteria; ensure economic alignment (margins); set 90-day performance review with exit clause
Cultural missteps damaging brand in new market	No local market expertise on team; copy-paste approach from home market	Hire local advisor or consultant for cultural review; adapt messaging, not just translate it

Success Criteria

Market selection scoring produces a clear rank-ordered list with at least 3 candidate markets scored across all 6 factors
Entry mode selected matches the graduation path: no legal entity before $200K ARR from market
Pre-launch checklist 100% complete by T-30 days before launch
First 90 days produce 20+ qualified conversations, 5+ pipeline opportunities, and 2+ closed deals
Exit criteria defined before market entry with specific revenue and cost thresholds
Localization phased: Must Have items complete at launch; Nice to Have items gated behind revenue milestone
Regulatory compliance achieved before first customer contract signed in new market

Scope & Limitations

In scope: Market selection scoring, entry mode evaluation, localization planning (product, GTM, operations), regulatory compliance mapping by region, pricing strategy adaptation, launch planning with exit criteria, team structure decisions
Out of scope: Detailed tax advisory (engage local tax counsel); immigration and visa processing (use specialized provider); transfer pricing implementation (use CFO Advisor with tax expertise); detailed legal entity formation (use local legal counsel)
Limitation: Regional quick reference data is indicative and changes with regulations; always validate with local experts before committing
Limitation: Framework optimized for B2B SaaS companies; B2C, hardware, and marketplace businesses have different expansion dynamics
Limitation: Market scoring is a structured estimate, not a guarantee; validate with real market signals (inbound demand, pilot customers) before major investment

Integration Points

Skill	Integration	Data Flow
`ceo-advisor`	Market entry is a strategic CEO decision	CEO strategy → Market selection priority
`cfo-advisor`	Investment sizing, ROI modeling, entity structure	Expansion budget → CFO financial model
`cro-advisor`	Revenue targets and sales model adaptation	Market ICP → CRO sales playbook adaptation
`cmo-advisor`	Local positioning and channel strategy	Market research → CMO local GTM plan
`cpo-advisor`	Localization roadmap and feature priorities	Localization requirements → CPO product roadmap
`ciso-advisor`	Data privacy and regulatory compliance	Regulatory map → CISO compliance checklist
`chro-advisor`	Local hiring, employment law, compensation	Market team plan → CHRO local hiring strategy

Python Tools

Tool	Purpose	Usage
`scripts/market_readiness_scorer.py`	Score and rank target markets using the 6-factor weighted framework	`python scripts/market_readiness_scorer.py --market "Germany" --market-size 4 --competition 3 --regulatory 2 --cultural-distance 3 --traction 4 --operational 3 --json`
`scripts/localization_checklist.py`	Generate a phased localization checklist for a target market	`python scripts/localization_checklist.py --market "Japan" --product-type saas --current-languages en --json`
`scripts/regulatory_mapper.py`	Map regulatory requirements by region including data privacy, tax, and employment law	`python scripts/regulatory_mapper.py --region eu --industry saas --data-processing yes --json`

Files

SKILL.md and 3 other files (scripts) in c-level-advisor/intl-expansion of borghei/Claude-Skills.

SKILL.md
scripts/localization_checklist.py
scripts/market_readiness_scorer.py
scripts/regulatory_mapper.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Intl Expansion 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.

Intl Expansion compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Intl Expansion this skillborghei/Claude-Skills	886	—	~5.2k	Automated safety check: Pass	MIT	2 days ago
Intl Expansionalirezarezvani/claude-skills	28k	1 repos	~1.1k	Automated safety check: Pass	MIT	1 mo ago
Grad Born Globalasgard-ai-platform/skills	242	—	~1.5k	Automated safety check: Pass	MIT	4 mo ago
Grad Uppsalaasgard-ai-platform/skills	242	—	~1.4k	Automated safety check: Pass	MIT	4 mo ago
Chuhai Market Entrymohitagw15856/pm-claude-skills	1.4k	—	~1.2k	Automated safety check: Pass	MIT	yesterday
Arabic Copy Localizergrowthack88/growth-marketing-os	116	—	~1k	Automated safety check: Pass	MIT	7 days ago

Similar skills

Intl Expansion
alirezarezvani/claude-skills
International market expansion strategy. An agent skill from alirezarezvani/claude-skills.
28k GitHub starsUsed in 1 repo~1.1k tokens
Marketing & SEOAuto-check passed
Grad Born Global
asgard-ai-platform/skills
Apply the Born Global framework to analyze firms that internationalize rapidly from inception under resource constraints.
242 GitHub stars~1.5k tokensUpdated 4 mo ago
Frontend & DesignAuto-check passed
Grad Uppsala
asgard-ai-platform/skills
Apply the Uppsala Internationalization Model to analyze gradual foreign market entry based on psychic distance and experiential learning.
242 GitHub stars~1.4k tokensUpdated 4 mo ago
Frontend & DesignAuto-check passed
Chuhai Market Entry
mohitagw15856/pm-claude-skills
Plan a Chinese company's entry into an overseas market (出海): choose the market with evidence, then plan entity, payments, localisation, compliance, channels and team for the first twelve months.
1.4k GitHub stars~1.2k tokensUpdated yesterday
Marketing & SEOAuto-check passed
Arabic Copy Localizer
growthack88/growth-marketing-os
Marketing copy localization skill that converts English marketing copy (ads, landing pages, emails, CTAs) into native Egyptian Arabic عامية — or GCC dialect on request — with natural English…
116 GitHub stars~1k tokensUpdated 7 days ago
Frontend & DesignAuto-check passed
Ds Lint Component
baloise/design-system
Lint and fix Helvetia Design System components for style guide compliance.
114 GitHub stars~1.4k tokensUpdated today
Frontend & DesignAuto-check passed

Questions about Intl Expansion

What does Intl Expansion do?

International market expansion strategy for scaling companies. Intl Expansion is an agent skill from borghei/Claude-Skills. International market expansion strategy for scaling companies.

When should I use Intl Expansion?

Intl Expansion fits situations like: expanding to new countries; evaluating international markets; planning localization; building regional teams.

How do I install Intl Expansion in Claude Code?

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

How do I install Intl Expansion in Codex?

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

Can I use Intl Expansion 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 intl-expansion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/intl-expansion, .gemini/skills/intl-expansion, .github/skills/intl-expansion and .opencode/skills/intl-expansion in your project.

What does Intl Expansion need to run?

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

Does Intl Expansion 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 Intl Expansion 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 Intl Expansion use?

Intl Expansion 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 Intl Expansion use?

About 5.2k tokens (SKILL.md is roughly 21k 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 Intl Expansion?

Skills that share tags, products or a category with Intl Expansion: Intl Expansion (alirezarezvani/claude-skills, 28k stars), Grad Born Global (asgard-ai-platform/skills, 242 stars), Grad Uppsala (asgard-ai-platform/skills, 242 stars) and Chuhai Market Entry (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Intl Expansion?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 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.

Install Intl Expansion

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

International Expansion

Keywords

Clarify First

Decision Sequence

Market Selection Framework

Scoring Matrix

Market Selection Decision Tree

Regional Quick Reference

Entry Mode Evaluation

Entry Mode Comparison

Entry Mode Decision Tree

Default Graduation Path

Localization Framework

Product Localization

GTM Localization

Operations Localization

Regulatory Compliance by Region

Data Privacy Requirements

Data Residency Decision Tree

International GTM Strategy

Pricing Strategy by Market

Sales Model Adaptation

Common Mistakes

Launch Checklist

Pre-Launch (T-90 days to T-30 days)

Launch (T-0 to T+90 days)

Exit Criteria

Red Flags

Integration with C-Suite

Output Artifacts

Troubleshooting

Success Criteria

Scope & Limitations

Integration Points

Python Tools

Files

Compare with similar skills

Similar skills

More from borghei/Claude-Skills

Related

Questions about Intl Expansion