[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MG8DQ9FS0AJWC9DN527XWX":3,"skill-same:01M6MG8DQ9FS0AJWC9DN527XWX":67},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6MG8DQ9FS0AJWC9DN527XWX","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.","JiayiV\u002Fquestion_mixing","JiayiV","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54466889?v=4","01M6JFJYYMRZ3QRGP9339JNQ2K","01M6JFJZ35KB0QVT50NAHPJA7G",0,"MIT","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-intl-expansion-skill-40d46423\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"expansion","intl expansion","Market","modes","countries","markets","go-to-market","localization","international","selection","go","regulatory","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":41,"description":7},{"author":42,"domain":43,"updated":44,"version":45,"category":46},"Alireza Rezvani","international-strategy",1772668800000,"1.0.0","c-level","main","068c2486ccc0f8d200a3db4d21ec137064eda3b4","skills\u002Fpublic-02-claude-skills-main-gemini-skills-intl-expansion-skill-40d46423","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing","https:\u002F\u002Fgithub.com\u002FJiayiV","2026-08-25 16:30:52",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add JiayiV\u002Fquestion_mixing --skill intl-expansion",{"tool":59,"command":60},"bunx","bunx skills add JiayiV\u002Fquestion_mixing --skill intl-expansion",{"tool":62,"command":63},"pnpm","pnpm dlx skills add JiayiV\u002Fquestion_mixing --skill intl-expansion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fpublic-02-claude-skills-main-gemini-skills-intl-expansion-skill-40d46423\u002FSKILL.md",true,[],[68,93,121,154,182,217],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":36},"01M6NN9PJS9NHWPDG4QP93BP8F","webmcpify","Make a web app agent-ready — propose a WebMCP tool manifest, integrate, verify in a real browser, heal; unrelated code stays untouched. Use for \"webmcpify\", \"add WebMCP\", or \"expose app actions to AI agents\".","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fwebmcpify\u002FSKILL.md",[],[70,75,76,77,78,79,80,81,82,83,84,85,86,30,87,88,89,90,91,92],"github","ai agents","web","notes","code","browser","https","actions","manifest","inventory","verify","tool","ready","unrelated","app","scope","for","webmcp",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":36},"01M6NN6KZE5RBN6NGHN2WXV1RE","vardoger-analyze","Use when the user asks to personalize the GitHub Copilot CLI assistant, adapt Copilot to their style, use vardoger, or analyze their Copilot CLI conversation history. Reads the local session directory at `~\u002F.copilot\u002Fsession-state\u002F`, extracts recurring preferences and conventions, and writes a fenced personalization block into `~\u002F.copilot\u002Fcopilot-instructions.md`. Runs entirely on the user's machine via the local `vardoger` CLI (`pipx install vardoger`); no network calls and no uploads. Triggers: 'personalize my copilot', 'analyze my copilot history', 'tailor copilot to me', 'run vardoger', 'update my copilot instructions from history', 'make copilot learn my style'.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fvardoger-analyze\u002FSKILL.md",[],[101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"vardoger analyze","analyze","directory","cli","github copilot","copilot","run","update","learn","network","my style","install","conversation","me","local","github copilot cli","pipx","my","at","copilot instructions",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":135,"publishedAt":36},"01M6NN3CZGQP3XAJ04BM1NNYGT","transloadit-media-processing","Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS\u002FMP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftransloadit-media-processing\u002FSKILL.md",[127,132],{"categoryNo":128,"categoryName":129,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":133,"categoryName":134,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000023","Skill与智能体开发",[136,137,138,139,140,141,142,143,144,145,146,147,148,30,149,150,151,152,91,153],"transloadit media processing","Media","media processing","processing","MCP","mcp server","documents","subtitles","pipeline","ocr","Video","Audio","mp4","images","files","transformation","free","hls",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":163,"publishedAt":36},"01M6NN28E92F9GH4WFYQ2H1Y15","terraform-azurerm-set-diff-analyzer","Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-azurerm-set-diff-analyzer\u002FSKILL.md",[160],{"categoryNo":161,"categoryName":162,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000011","运维与部署",[164,165,166,167,168,169,170,171,172,30,173,174,175,176,177,178,179,180,181,91],"terraform","SET","terraform azurerm set diff analyzer","diff","analyzer","diffs","azure","gateway","firewall","only","resource changes","provider","resources","load balancer","attributes","front","load","balancer",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":199,"publishedAt":36},"01M6NN1QMH2TDYWTH3XY3N5XPV","technical-job-search","Use this skill when a software engineer asks for help with job search tasks: parsing or analyzing a job description, tailoring a CV\u002Fresume, writing a cover letter, evaluating a job offer, or drafting a post-interview follow-up email. Do not activate for general career advice unrelated to an active job search action.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-job-search\u002FSKILL.md",[188,191,196],{"categoryNo":189,"categoryName":190,"taxonomyType":130,"taxonomyTypeDesc":131},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":192,"categoryName":193,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":197,"categoryName":198,"taxonomyType":194,"taxonomyTypeDesc":195},"01JBSEEDCAT000000000000038","人力资源",[200,201,202,203,204,205,206,207,102,208,30,209,210,211,212,213,214,215,91,216],"search","Job Search","technical job search","technical","writing","tasks","email","parsing","interview","up","engineer","general","activate","do","task","cv","letter",{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":223,"publishedAt":36},"01M6NMZFA67XYS1GS09WT42235","steno-mode","Shorthand-first response compression that cuts ~40% of response tokens while preserving technical precision and exact literals. Use when the user says \"steno mode\", \"shorthand mode\", \"compressed responses\", \"token reduction\", \"brief structured output\", or invokes \u002Fsteno. Supports four compression levels: lite, brief, court, machine. Do not trigger for requests needing polished prose such as onboarding\u002Ftutorial content, stakeholder or customer-facing copy, or teaching-focused explanations.","https:\u002F\u002Fgithub.com\u002FJiayiV\u002Fquestion_mixing\u002Fblob\u002Fmain\u002Fskills\u002Fsteno-mode\u002FSKILL.md",[],[224,225,226,227,228,203,229,30,213,230,231,232,233,234,235,236,237,238,91,239],"steno mode","mode","customer","brief","first","tutorial","teaching","tokens","as","trigger","structured output","machine","output","court","requests","response compression"]