Cb Overseas Talent Playbook

SKILL.md

---
name: Overseas Talent and Team Building Playbook
description: Hire, onboard, and manage overseas talent in minutes. Get hiring sequences, role scorecards, interview rubrics, onboarding plans, and compliance checklists for any overseas market — install and build your distributed team in under 30 seconds.
version: 1.0.0
tags: [cross-border, global-talent, international-hiring, hr-compliance]
---

# Overseas Talent and Team Building Playbook

## Overview

A team-design framework for hiring, onboarding, managing, and coordinating overseas local talent and distributed expansion teams.

This is a pure descriptive OpenClaw skill for overseas expansion planning. It provides frameworks, templates, checklists, decision criteria, and risk reminders. It does **not** execute code, call APIs, access the network, scrape websites, submit forms, make purchases, send messages, or perform any external action.

## When to Use

Use this skill when the user needs structured help with overseas talent and team building playbook in a cross-border or international expansion context.

Typical trigger phrases include:
- hire overseas team
- international talent playbook
- local country manager
- distributed global team
- overseas hiring strategy

## Target Users

Founders, HR leads, country managers, and operations leaders expanding internationally.

## Inputs to Collect

Ask for or infer the following context before producing the final framework:

- Target market or list of candidate markets
- Product, service, category, or business model
- Current business stage and domestic traction, if any
- Target customer segment and purchase context
- Expansion goal, timeline, budget range, and constraints
- Existing assets such as brand story, content, team, channels, customer data, or partners
- Known risks, assumptions, compliance concerns, and decision deadlines

If important inputs are missing, state the assumptions clearly and provide a version that can be refined later.

## Workflow

1. Diagnose which overseas capabilities must be local now versus handled from headquarters, based on market stage, customer contact, compliance risk, and speed needs.
2. Design the first hiring sequence and role scorecards for country lead, marketing, sales, support, operations, partnerships, or compliance coordination.
3. Choose hiring channels and evaluation methods that test local judgment, execution ownership, language ability, and cross-cultural collaboration.
4. Create onboarding and operating rhythm for distributed work, including decision rights, reporting, documentation, and conflict escalation.
5. Flag employment, contractor, immigration, payroll, and data-access issues for local professional review before hiring decisions.

## Output Modules

### Role and location design
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.
### Hiring channel and profile map
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.
### Interview and evaluation rubric
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.
### Onboarding and cultural alignment plan
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.
### Operating rhythm for distributed teams
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.
### Risk and compliance checklist
- Purpose: turn the user's market context into a structured planning component.
- Include: assumptions, recommended actions, decision criteria, and questions that require local validation.
- Output style: concise tables, checklists, and bullet-point rationale rather than generic advice.

## Output Format

Return a structured response with these sections:

1. **Input Summary** — what the user provided and what assumptions are being made.
2. **Strategic Diagnosis** — key opportunity, constraint, and uncertainty analysis for the overseas context.
3. **Framework Output** — the main tables, matrices, checklists, templates, or playbooks generated by this skill.
4. **Market Adaptation Notes** — what should change by region, language, channel, customer expectation, or operating model.
5. **Risks and Validation Tasks** — assumptions to test, professional review needs, and red flags.
6. **Next Actions** — 5–10 practical steps the user can take manually.

## Example Prompts

Try these real-world scenarios to see what this skill can produce:

**Prompt 1: First Country Manager Hire**
> "We are a B2B SaaS company entering Japan. We need to hire a country manager. Should we hire a Japanese native or an expat? What should the role scorecard look like?"
> → Output: Role vs location recommendation (Japanese native with EN proficiency preferred for JP), detailed role scorecard with 6 evaluation dimensions (local market judgment, sales network, cross-cultural collaboration, legal/compliance awareness, language ability, execution ownership), recommended hiring channels (LinkedIn JP, Wantedly, BizReach, headhunters), interview rubric with culturally-adapted questions.

**Prompt 2: Germany Distributed Team Setup**
> "We are opening a 5-person team in Berlin for our DTC brand. We need marketing, customer support, logistics, and a country lead. What's the right hiring sequence and onboarding plan?"
> → Output: Hiring sequence recommendation (country lead first → logistics specialist → marketing lead → customer support → operations coordinator), timeline estimate (3 months), role scorecards per position, onboarding plan with 30-60-90 day milestones, German employment law flags (probation period, severance rules, works council considerations), operating rhythm for distributed collaboration with HQ.

**Prompt 3: Southeast Asia Contractor vs Employee**
> "We need a marketing person in Vietnam and a sales person in Thailand. Should we hire them as employees or contractors? What are the compliance risks?"
> → Output: Market-specific analysis (VN: employee preferred for substantive roles, contractor risk flags under VN Labor Code; TH: contractor options viable with proper agreement structure), compliance checklist per jurisdiction, payroll and social contribution comparison, recommended EOR provider evaluation criteria, escalation path for compliance issues.

## Getting Started

👋 **cb-overseas-talent-playbook installed!**

I help you hire and manage overseas teams that actually work — not just job descriptions, but a full system for finding, evaluating, onboarding, and retaining local talent.

Try this to get started:
> "I need help hiring [role] in [market]. We're [company type] and this is our first hire in that country."

Or just describe your overseas team-building challenge.

## Safety and Limitations

Employment, contractor, tax, and immigration rules vary by jurisdiction and require local professional advice.

Additional limitations:

- No professional legal, tax, financial, medical, employment, investment, or compliance advice.
- No guarantee of market success, conversion improvement, legal compliance, or platform acceptance.
- Verify local laws, platform policies, consumer expectations, and current market facts with qualified professionals and reliable sources.
- Avoid stereotyping cultures or users; treat all cultural observations as hypotheses requiring local validation.


## Usage Scenarios

### Scenario 1

**User Input:** "I want to hire 3 software engineers in Poland. Should I use an EOR or set up a local entity?"

**Expected Output:** Decision matrix comparing Deel/Remote/Oyster EOR costs vs. Polish entity setup costs, timeline (EOR: 2 weeks vs. entity: 3-6 months), and ongoing compliance burden. Recommends EOR for this scale.

### Scenario 2

**User Input:** "Benchmark compensation for a senior product manager in Singapore, including mandatory benefits and CPF contributions."

**Expected Output:** Total compensation table: base salary range (SGD), bonus norms, CPF employer contribution schedule, mandatory insurance, and typical perks. Sourced from recent market data.

### Scenario 3

**User Input:** "Design a 90-day onboarding plan for our first remote hire in Brazil, addressing timezone overlap (BRT ↔ CET) and cultural integration."

**Expected Output:** Week-by-week onboarding calendar with timezone-friendly meeting slots, Portuguese-language resource links, cultural-norm guide (communication style, holiday calendar), and a buddy-system recommendation.


### Scenario 4: 帮国内公司找海外技术人才
**User input:** "我们公司要在东南亚（越南/印尼/泰国）招工程师，但不知道怎么在当地发招聘广告、面试、发Offer。有系统的方法吗？"
**Expected output:** 东南亚技术人才招聘路线图——渠道：越南用TopDev/ITViec、印尼用Glints/Kalibrr、泰国用JobsDB；JD发布：本地化翻译+注明薪资范围（当地币种，普遍要求月薪公开）+福利签证优势；面试：用腾讯会议国际版Voov Meeting/Zoom安排，注意时差（东七区/东八区）；Offer：明确注明是本地雇佣还是跨境（C2C/B2B），薪资结构必须加医疗保险+签证支持；文化要点：东南亚候选人喜欢信息透明（JD里写清成长路径）、加班要明确说明规则、签约奖金比高底薪更有吸引力。关键工具：Deel/Remote.com处理跨境雇佣合规。

## Acceptance Criteria

- Defines priority roles and hiring sequence
- Includes role scorecards and interview questions
- Provides onboarding and communication rhythm
- Addresses local management autonomy
- Flags employment-law and contractor risks
- Provides structured, market-aware outputs rather than generic overseas expansion advice.
- Includes explicit assumptions, evidence gaps, and validation steps.
- Stays pure descriptive with no code execution, API calls, browsing, network access, or external side effects.