[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H1RX7RJR2BC1T2DPTWNXAH":3,"skill-same:01M6H1RX7RJR2BC1T2DPTWNXAH":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6H1RX7RJR2BC1T2DPTWNXAH","intl-expansion",null,"International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fclaude-skills-192\u002Fc-level-advisor\u002Fintl-expansion\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"expansion","intl expansion","regulatory","countries","markets","go-to-market","localization","international","selection","Market","go","use","strategy","regulatory compliance","compliance","planning","teams","2026-11-10 10:12:30",false,"---\nname: \"intl-expansion\"\ndescription: \"International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: international-strategy\n  updated: 2026-03-05\n---\n\n# International Expansion\n\nFrameworks for expanding into new markets: selection, entry, localization, and execution.\n\n## Keywords\ninternational expansion, market entry, localization, go-to-market, GTM, regional strategy, international markets, market selection, cross-border, global expansion\n\n## Quick Start\n\n**Decision sequence:** Market selection → Entry mode → Regulatory assessment → Localization plan → GTM strategy → Team structure → Launch.\n\n## Market Selection Framework\n\n### Scoring Matrix\n| Factor | Weight | How to Assess |\n|--------|--------|---------------|\n| Market size (addressable) | 25% | TAM in target segment, willingness to pay |\n| Competitive intensity | 20% | Incumbent strength, market gaps |\n| Regulatory complexity | 20% | Barriers to entry, compliance cost, timeline |\n| Cultural distance | 15% | Language, business practices, buying behavior |\n| Existing traction | 10% | Inbound demand, existing customers, partnerships |\n| Operational complexity | 10% | Time zones, infrastructure, payment systems |\n\n### Entry Modes\n| Mode | Investment | Control | Risk | Best For |\n|------|-----------|---------|------|----------|\n| **Export** (sell remotely) | Low | Low | Low | Testing demand |\n| **Partnership** (reseller\u002Fdistributor) | Medium | Medium | Medium | Markets with strong local requirements |\n| **Local team** (hire in-market) | High | High | High | Strategic markets with proven demand |\n| **Entity** (full subsidiary) | Very high | Full | High | Major markets, regulatory requirement |\n| **Acquisition** | Highest | Full | Highest | Fast market entry with existing base |\n\n**Default path:** Export → Partnership → Local team → Entity (graduate as revenue justifies).\n\n## Localization Checklist\n\n### Product\n- [ ] Language (UI, documentation, support content)\n- [ ] Currency and pricing (local pricing, not just conversion)\n- [ ] Payment methods (varies wildly by market)\n- [ ] Date\u002Ftime\u002Fnumber formats\n- [ ] Legal requirements (data residency, privacy)\n- [ ] Cultural adaptation (not just translation)\n\n### Go-to-Market\n- [ ] Messaging adaptation (what resonates locally)\n- [ ] Channel strategy (channels differ by market)\n- [ ] Local case studies and social proof\n- [ ] Local partnerships and integrations\n- [ ] Event\u002Fconference presence\n- [ ] Local SEO and content\n\n### Operations\n- [ ] Legal entity (if required)\n- [ ] Tax compliance\n- [ ] Employment law (if hiring locally)\n- [ ] Customer support (hours, language)\n- [ ] Banking and payments\n\n## Key Questions\n\n- \"Is there pull from the market, or are we pushing?\"\n- \"What's the cost of entry vs the 3-year revenue opportunity?\"\n- \"Can we serve this market from HQ, or do we need boots on the ground?\"\n- \"What's the regulatory timeline? Can we launch before the paperwork is done?\"\n- \"Who's winning in this market and what would it take to displace them?\"\n\n## Common Mistakes\n\n| Mistake | Why It Happens | Prevention |\n|---------|---------------|------------|\n| Entering too many markets at once | FOMO, board pressure | Max 1-2 new markets per year |\n| Copy-paste GTM from home market | Assuming buyers are the same | Research local buying behavior |\n| Underestimating regulatory cost | \"We'll figure it out\" | Regulatory assessment BEFORE committing |\n| Hiring too early | Optimism | Prove demand before hiring local team |\n| Wrong pricing (just converting) | Laziness | Research willingness to pay locally |\n\n## Integration with C-Suite Roles\n\n| Role | Contribution |\n|------|-------------|\n| CEO | Market selection, strategic commitment |\n| CFO | Investment sizing, ROI modeling, entity structure |\n| CRO | Revenue targets, sales model adaptation |\n| CMO | Positioning, channel strategy, local brand |\n| CPO | Localization roadmap, feature priorities |\n| CTO | Infrastructure, data residency, scaling |\n| CHRO | Local hiring, employment law, comp |\n| COO | Operations setup, process adaptation |\n\n## Resources\n- `references\u002Fmarket-entry-playbook.md` — detailed entry playbook by market type\n- `references\u002Fregional-guide.md` — specific considerations for key regions (EU, US, APAC, LATAM)\n","# International Expansion\n\nFrameworks for expanding into new markets: selection, entry, localization, and execution.\n\n## Keywords\ninternational expansion, market entry, localization, go-to-market, GTM, regional strategy, international markets, market selection, cross-border, global expansion\n\n## Quick Start\n\n**Decision sequence:** Market selection → Entry mode → Regulatory assessment → Localization plan → GTM strategy → Team structure → Launch.\n\n## Market Selection Framework\n\n### Scoring Matrix\n| Factor | Weight | How to Assess |\n|--------|--------|---------------|\n| Market size (addressable) | 25% | TAM in target segment, willingness to pay |\n| Competitive intensity | 20% | Incumbent strength, market gaps |\n| Regulatory complexity | 20% | Barriers to entry, compliance cost, timeline |\n| Cultural distance | 15% | Language, business practices, buying behavior |\n| Existing traction | 10% | Inbound demand, existing customers, partnerships |\n| Operational complexity | 10% | Time zones, infrastructure, payment systems |\n\n### Entry Modes\n| Mode | Investment | Control | Risk | Best For |\n|------|-----------|---------|------|----------|\n| **Export** (sell remotely) | Low | Low | Low | Testing demand |\n| **Partnership** (reseller\u002Fdistributor) | Medium | Medium | Medium | Markets with strong local requirements |\n| **Local team** (hire in-market) | High | High | High | Strategic markets with proven demand |\n| **Entity** (full subsidiary) | Very high | Full | High | Major markets, regulatory requirement |\n| **Acquisition** | Highest | Full | Highest | Fast market entry with existing base |\n\n**Default path:** Export → Partnership → Local team → Entity (graduate as revenue justifies).\n\n## Localization Checklist\n\n### Product\n- [ ] Language (UI, documentation, support content)\n- [ ] Currency and pricing (local pricing, not just conversion)\n- [ ] Payment methods (varies wildly by market)\n- [ ] Date\u002Ftime\u002Fnumber formats\n- [ ] Legal requirements (data residency, privacy)\n- [ ] Cultural adaptation (not just translation)\n\n### Go-to-Market\n- [ ] Messaging adaptation (what resonates locally)\n- [ ] Channel strategy (channels differ by market)\n- [ ] Local case studies and social proof\n- [ ] Local partnerships and integrations\n- [ ] Event\u002Fconference presence\n- [ ] Local SEO and content\n\n### Operations\n- [ ] Legal entity (if required)\n- [ ] Tax compliance\n- [ ] Employment law (if hiring locally)\n- [ ] Customer support (hours, language)\n- [ ] Banking and payments\n\n## Key Questions\n\n- \"Is there pull from the market, or are we pushing?\"\n- \"What's the cost of entry vs the 3-year revenue opportunity?\"\n- \"Can we serve this market from HQ, or do we need boots on the ground?\"\n- \"What's the regulatory timeline? Can we launch before the paperwork is done?\"\n- \"Who's winning in this market and what would it take to displace them?\"\n\n## Common Mistakes\n\n| Mistake | Why It Happens | Prevention |\n|---------|---------------|------------|\n| Entering too many markets at once | FOMO, board pressure | Max 1-2 new markets per year |\n| Copy-paste GTM from home market | Assuming buyers are the same | Research local buying behavior |\n| Underestimating regulatory cost | \"We'll figure it out\" | Regulatory assessment BEFORE committing |\n| Hiring too early | Optimism | Prove demand before hiring local team |\n| Wrong pricing (just converting) | Laziness | Research willingness to pay locally |\n\n## Integration with C-Suite Roles\n\n| Role | Contribution |\n|------|-------------|\n| CEO | Market selection, strategic commitment |\n| CFO | Investment sizing, ROI modeling, entity structure |\n| CRO | Revenue targets, sales model adaptation |\n| CMO | Positioning, channel strategy, local brand |\n| CPO | Localization roadmap, feature priorities |\n| CTO | Infrastructure, data residency, scaling |\n| CHRO | Local hiring, employment law, comp |\n| COO | Operations setup, process adaptation |\n\n## Resources\n- `references\u002Fmarket-entry-playbook.md` — detailed entry playbook by market type\n- `references\u002Fregional-guide.md` — specific considerations for key regions (EU, US, APAC, LATAM)\n",{"name":5,"license":14,"metadata":40,"description":7},{"author":41,"domain":42,"updated":43,"version":44,"category":45},"Alireza Rezvani","international-strategy",1772668800000,"1.0.0","c-level","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fclaude-skills-192\u002Fc-level-advisor\u002Fintl-expansion",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add micsapp\u002Fmicstec-skills --skill intl-expansion",{"tool":59,"command":60},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill intl-expansion",{"tool":62,"command":63},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill intl-expansion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fclaude-skills-192\u002Fc-level-advisor\u002Fintl-expansion\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fmarket-entry-playbook.md","REFERENCE","参考文档",6282,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fclaude-skills-192\u002Fc-level-advisor\u002Fintl-expansion\u002Freferences\u002Fmarket-entry-playbook.md",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fregional-guide.md",6059,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fclaude-skills-192\u002Fc-level-advisor\u002Fintl-expansion\u002Freferences\u002Fregional-guide.md",[78,114,144,164,184,209],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":94,"publishedAt":35},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[84,89],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,26,110,111,112,113],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","strategies","azure api management","mode","for",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":128,"publishedAt":35},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[120,121,124,127],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":122,"categoryName":123,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":125,"categoryName":126,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[129,130,131,132,96,133,134,135,136,137,138,139,104,105,110,140,141,111,142,143],"deployment","apiops deployment","workflows","azure devops","infrastructure","code","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":35},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[150],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},[152,153,154,155,96,99,104,105,156,29,157,158,159,160,161,111,162,163,143,113],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":172,"publishedAt":35},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[170,171],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},{"categoryNo":90,"categoryName":91,"taxonomyType":92,"taxonomyTypeDesc":93},[173,155,174,104,158,175,96,129,176,177,178,179,105,180,111,181,182,183,112,113],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":35},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[191,192,193,131,194,195,196,197,104,198,199,200,201,202,203,204,205,206,207,208],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":35},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[211,216,217,218,219,220,221,29,222,223],"npm","js","calculate","node","math","user","compute","errors"]