Develop e-commerce strategy for Southeast Asian markets including platform selection, payment infrastructure, logistics challenges, and localization requirements. Use this skill when the user is expanding e-commerce to SEA, evaluating Shopee vs Lazada vs Tokopedia, or needs to understand SEA market differences — even if they say 'sell to Southeast Asia', 'which platform in Vietnam', 'SEA payment methods', or 'cross-border e-commerce in ASEAN'.
npx skills add https://github.com/asgard-ai-platform/skills --skill ecom-sea-strategy
IRON LAW: SEA Is Not One Market — It's 10+ Different Markets
Indonesia, Vietnam, Thailand, Philippines, Malaysia, and Singapore have
different languages, payment preferences, logistics infrastructure, and
consumer behaviors. A strategy that works in Singapore (high digital
maturity, English-speaking) will fail in Indonesia (cash-heavy, Bahasa,
island logistics). Analyze each country individually.
| Country | Pop. | E-com Penetration | Top Platform | Dominant Payment | Key Challenge |
|---------|------|------------------|-------------|-----------------|---------------|
| Indonesia | 278M | ~35% | Tokopedia/Shopee | Bank transfer, e-wallets (GoPay, OVO) | Island logistics, last-mile cost |
| Vietnam | 100M | ~30% | Shopee | COD (~60%), e-wallets (MoMo) | COD returns high (~15-20%) |
| Thailand | 72M | ~40% | Shopee/Lazada | Bank transfer (PromptPay), COD | Fragmented social commerce |
| Philippines | 115M | ~25% | Shopee/Lazada | GCash, COD | Island logistics, low trust in online |
| Malaysia | 33M | ~45% | Shopee | FPX bank transfer, e-wallets | Small market, competitive |
| Singapore | 6M | ~55% | Shopee/Lazada/Amazon | Credit cards, PayNow | Tiny market, high CAC |
| Factor | Marketplace (Shopee/Lazada) | Own D2C Site | Social Commerce (IG/LINE/TikTok) |
|--------|---------------------------|-------------|--------------------------------|
| Traffic | Built-in | Must generate yourself | Organic but unpredictable |
| Commission | 3-15% + ads | 0% + payment/hosting costs | 0% + fulfillment |
| Data ownership | Platform owns | You own | Partial |
| Brand control | Limited | Full | Medium |
| Best for | Market entry, volume | Brand building, repeat customers | Viral products, low-trust markets |
Phase 1: Market Selection (pick ONE country first)
Phase 2: Platform Setup
Phase 3: Localization
Phase 4: Scale
# SEA E-Commerce Strategy: {Brand/Product}
## Market Selection
| Country | Opportunity | Competition | Barriers | Score |
|---------|-----------|-------------|---------|-------|
| {country} | H/M/L | H/M/L | H/M/L | {total} |
## Recommended Entry: {Country}
- Platform: {which marketplace}
- Payment: {accepted methods}
- Logistics: {fulfillment approach}
- Timeline: {phases with milestones}
## Localization Requirements
{Language, pricing, cultural adaptations needed}
## Budget Estimate
| Item | Cost | Notes |
|------|------|-------|
| Platform setup | ${X} | ... |
| Inventory | ${X} | ... |
| Marketing (first 3 months) | ${X} | ... |
references/sea-regulations.mdreferences/platform-fees.mdBuild robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.
Cloudflare Workers Runtime APIs including Fetch, Streams, Crypto, Cache, WebSockets, and Encoding. Use for HTTP requests, streaming, encryption, caching, real-time connections, or encountering API compatibility, response handling, stream processing errors.
Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.
Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.
Track and analyze portfolio company performance against plan. Ingests monthly/quarterly financial packages (Excel, PDF), extracts KPIs, flags variances to budget, and produces summary dashboards. Use when reviewing portfolio company financials, preparing board materials, or monitoring covenant compliance. Triggers on "review portfolio company", "monthly financials", "how is [company] performing", "covenant check", or "portfolio update".
Expert knowledge for Azure Payment Hsm development including troubleshooting, best practices, decision making, architecture & design patterns, security, and configuration. Use when configuring Payment HSM VNets/peering, FastPath, payShield Manager access, SKUs, HA/DR topologies, or traffic routing, and other Azure Payment Hsm related development tasks. Not for Azure Cloud Hsm (use azure-cloud-hsm), Azure Dedicated HSM (use azure-dedicated-hsm), Azure Key Vault (use azure-key-vault), Azure Security (use azure-security).
Matter budgeting and ongoing WIP/variance monitoring. Build phase-based fee estimates at matter setup, run bottom-up budgets by jurisdiction or workstream, calculate contingency, and structure AFA arrangements (fixed fee, capped fee, phased fixed fees). Ongoing monitoring: WIP tracking against budget, proportionality assessment (spend vs progress), variance commentary with root cause analysis, forecast-to-complete, realisation monitoring, write-off analysis. Trigger on: 'build a budget', 'fee estimate', 'what will this cost', 'WIP review', 'budget vs actual', 'how are we tracking against budget', 'we're over budget', 'realisation is poor', 'what's our ETC', 'budget for the German workstream', 'model the financial impact of this scope change', 'draft a fee adjustment', 'write-off analysis', 'how much contingency', 'AFA structure', 'fixed fee estimate', 'budget update', 'forecast to complete'.
Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.
Take asgard-ai-platform/ecom-sea-strategy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.