Cb Market Entry Strategist

Systematic market selection and entry strategy for cross-border e-commerce expansion

Security Scan

The skill's code, instructions, and requirements are coherent with a descriptive market-entry advisor and do not request unrelated credentials or network access; a few minor documentation mismatches are noted but nothing appears malicious.

Purpose & Capability

Name and description match the code and outputs: the skill evaluates markets, builds phased strategies, and produces checklists. It does not request credentials, binaries, or config paths. Minor inconsistency: the package metadata and SKILL.md describe this as a "pure descriptive" or "instruction-only" skill, yet a handler.py implementation file is present (the code runs locally). This is not dangerous here, but it's an inconsistency between 'instruction-only' wording and the actual code file.

Instruction Scope

SKILL.md explicitly states no network calls, exec, or file I/O beyond producing JSON; the included handler.py follows that: it parses input, uses internal constants, and returns JSON. The handler does not read external files, environment variables, or make network/subprocess calls. The only small scope note: SKILL.md wording 'No code execution' is slightly misleading because handler.py is executable code that runs locally when invoked, but it does not perform unexpected I/O or external communications.

Install Mechanism

There is no install spec and nothing is downloaded or installed. All functionality is provided by the bundled handler.py and SKILL.md, so installation risk is low.

Credentials

The skill requires no environment variables, no credentials, and no config paths. All data used are internal static market entries and user-provided input; the requested access is proportional to the described purpose.

Persistence & Privilege

always:false and default invocation settings are used. The skill does not request persistent system-wide changes or access to other skills' configurations.

Assessment

This skill appears to honestly implement a descriptive market-entry advisor and does not try to access network, secrets, or system files. Two minor documentation inconsistencies to note before installing: (1) SKILL.md/registry text describes the skill as "instruction-only" or "no code execution" while a runnable handler.py is included — the code runs locally but does not perform network I/O; (2) ACCEPTANCE.md references a .claw/identity.json requirement that is not present in the file manifest. Neither issue is evidence of malicious behavior, but if you need strict guarantees, ask the publisher to clarify (a) whether the skill is truly instruction-only or intentionally includes executable handler code, and (b) provide the referenced identity file or remove that acceptance requirement. If you are happy with local-only processing and no external access, this skill is coherent and low-risk.

Cross-border Market Entry Strategist

Overview

Systematic market selection and entry strategy for cross-border e-commerce expansion. Evaluates multiple international markets using a multi-factor scoring model, generates phased entry roadmaps based on timeline and budget, and produces implementation checklists with market-specific requirements. This is a pure descriptive skill providing frameworks, templates, and analysis. No code execution, API calls, network requests, or real-time data.

Trigger Keywords

Use this skill when the user mentions or asks about:

• market entry and expansion strategy
• which country or which market to enter for international e-commerce
• expand to Germany, Japan, Australia, France, UK, or other international markets
• market selection for cross-border expansion
• international growth planning

Primary Triggers

• "market entry strategy for Germany and Japan"
• "which markets should I expand to for my electronics brand"
• "help me evaluate Australia and Canada for cross-border expansion"

Workflow

1. Receive input — Parse current markets, product categories, budget, and timeline
2. Analyze markets — Score and rank target markets using multi-factor assessment (purchasing power, logistics, regulatory, competition)
3. Build strategy — Generate phased entry framework based on timeline (short/medium/long)
4. Create checklist — Produce implementation checklist with market-specific items (VAT, compliance, logistics, payments)
5. Identify risks — Outline risk mitigation across regulatory, operational, and market dimensions

Input Format

Accepts natural language or structured JSON describing the business context, target markets, budget, and timeline.

Output Structure

Returns JSON with:

• input_analysis: parsed input parameters
• market_analysis: scored and ranked markets with strengths, risks, and complexity
• entry_strategy_framework: phased approach appropriate to timeline
• implementation_checklist: 10+ actionable items
• risk_mitigation_framework: regulatory, operational, and market risks with mitigations
• disclaimer: safety disclaimer

Safety and Disclaimer

Descriptive guidance only. Not professional legal, tax, financial, or business advice. Verify with qualified professionals. Does not guarantee market success or compliance.

Examples

Example 1: Electronics Expansion

Input: "I sell electronics and want to expand to Germany and Japan within 6 months budget $100k" Output: Scored market analysis for Germany and Japan, phased 6-month entry strategy, implementation checklist with VAT/regulatory tasks, risk framework.

Example 2: Multi-Market Evaluation

Input: "help me evaluate Australia Canada Netherlands for cross-border expansion budget $200k" Output: Comparative analysis across three markets with scores, phased strategy, comprehensive checklist.

Acceptance Criteria

• Evaluates at least 3-5 target markets with numerical scoring
• Provides phased entry strategy framework appropriate to timeline
• Includes implementation checklist with 10+ items
• Outlines risk mitigation framework covering regulatory, operational, and market risks
• Returns valid JSON with all documented fields present
• Contains complete safety disclaimer in every output
• Includes input_analysis summarizing parsed input
• Pure descriptive — no code execution, API calls, network requests, or bookings

Last updated: 2026-04-22

Last updated: 2026-04-22