Official agent skill

International Expansion

by anthropics in anthropics/claude-for-legal

Reference: implementation-planning framework for international hiring — EOR vs.

OfficialApache-2.0Auto-check passed

Install International Expansion

skills CLI
$ npx skills add anthropics/claude-for-legal --skill international-expansion -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install anthropics/claude-for-legal international-expansion --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/anthropics/claude-for-legal.git skills-src && mkdir -p .claude/skills && cp -r skills-src/employment-legal/skills/international-expansion .claude/skills/international-expansion && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
international-expansion
GitHub stars
9.6k
Used in
3 other repos
Token cost
~3.9k tokens
SKILL.md length
1,858 words
Files
1
Skills in repo
147
Repo updated
First seen
Licence
Apache-2.0

At a glance

Reference: implementation-planning framework for international hiring — EOR vs.

  • Works in 6 steps: Information gathering → EOR vs. entity framing → Cross-functional triggers → …
  • Structured outside-counsel briefing requests
  • SKILL.md covers Matter context, Purpose, Load context and Output header, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

International Expansion is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Reference: implementation-planning framework for international hiring — EOR vs. entity decision framing, cross-functional triggers for tax/finance/HR, structured outside-counsel briefing requests, and a persistent gap tracker. Loaded by /expansion-kickoff and /expansion-update; not invoked directly.

Its SKILL.md is about 3.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A suite of plugins for legal workflows. The licence is Apache-2.0.

When your agent uses it

  • Structured outside-counsel briefing requests
  • A persistent gap tracker

Example prompts

  • “/international-expansion”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Information gathering
  2. EOR vs. entity framing
  3. Cross-functional triggers
  4. Country-specific briefing request
  5. Create the expansion tracker
  6. Output

What it can do on your machine

Read from SKILL.md and the folder at commit 4a6c651. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

International Expansion loads about 3.9k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 1,858 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from anthropics/claude-for-legal at commit 4a6c651, republished under its Apache-2.0 licence (© anthropics). 1,858 words, ~3,891 tokens.

Download SKILL.mdSave it as .claude/skills/international-expansion/SKILL.md (or your agent's skills folder).
name
international-expansion
description
Reference: implementation-planning framework for international hiring — EOR vs. entity decision framing, cross-functional triggers for tax/finance/HR, structured outside-counsel briefing requests, and a persistent gap tracker. Loaded by /expansion-kickoff and /expansion-update; not invoked directly.
user-invocable
false

International Expansion Skill

Matter context

Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled is ✗ (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run /employment-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at ~/.claude/plugins/config/claude-for-legal/employment-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.


Purpose

International hiring gets handled sloppily at scaleups because nobody owns the full picture. Legal knows the employment-law questions but not the PE risk questions. Finance knows the cost model but not the employee-representation triggers. HR knows the comp benchmarks but not the Day 1 compliance requirements.

This skill doesn't replace any of those functions. It maps the terrain, drafts the right questions for each stakeholder, produces a briefing request that walks outside counsel through the country-specific issues, and creates a tracker that keeps the project moving across sessions.

This skill assumes expansion is decided. It is not a "should we expand?" framework.

This skill does not contain country-specific employment law. The substantive rules change frequently and vary by role, headcount, and industry — the skill routes every country through an outside-counsel briefing rather than relying on a stored reference table.

Load context

Read ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → jurisdictional footprint, escalation table, any existing expansion notes.

Output header

Prepend the work-product header from ~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md → ## Outputs (it differs by user role — see ## Who's using this).

Workflow

Step 1 — Information gathering

Ask all of the following in a single block:

Before I build the expansion plan I need to understand the shape of this expansion. Please answer what you can — gaps in the answers are themselves useful data:

The expansion

  • Which country?
  • What roles are you hiring? (Job function matters — a sales rep closing deals creates different legal exposure than an engineer writing code)
  • How many hires are planned in the next 12 months?
  • When do you need the first person to start?

Current state

  • Do you already have a legal entity in this country?
  • Have you used an EOR provider before? Are you already considering one?
  • Has tax or finance been looped in yet?
  • Do you have outside employment counsel in this country?

Strategic context

  • Is this a long-term strategic commitment (building a real team) or testing the market (one or two hires, see how it goes)?
  • Who is the executive sponsor making the structure decision?

Wait for responses before proceeding.

Step 2 — EOR vs. entity framing

Do not make this decision. Frame it with enough precision that the CFO and tax counsel can make it.

Work through the following factors against the intake answers and produce a structured framing document:

The core trade-off:

FactorPoints toward EORPoints toward Entity
Headcount in 12 monthsFewer hiresMore hires
Timeline to first hireShort runwayLonger runway available
Strategic commitmentTesting the marketLong-term presence
Cost sensitivityEOR markup acceptableScale makes entity more efficient
Control needsLow — EOR employer handles local HRHigh — want direct employer relationship
IP sensitivityLowerHigher — entity ownership cleaner

Specific headcount break-even points, EOR markup ranges, setup costs, and timelines vary by country and provider — do not hardcode them. Route those questions to tax/finance and the EOR provider.

PE risk flag (route to tax counsel): If roles include sales, business development, account management, or anyone with authority to negotiate or sign contracts on behalf of the company — flag this explicitly:

PE Risk: [Role type] may create a taxable permanent establishment in [country] even before a legal entity exists. This is a tax question, not an employment question. Tax counsel must assess before the first hire.

Produce the question for the CFO/tax:

Questions for your CFO and tax counsel:

  • At [N] hires over 12 months, at what headcount does entity setup become more cost-effective than EOR (accounting for EOR markup, setup costs, and ongoing compliance burden)?
  • [If PE-risk roles:] Do these role types create a taxable permanent establishment in [country]? If yes, does that change the entity timeline?
  • If we start with EOR and convert to entity later, what are the transition risks for the employees already on the EOR?
  • Who is our preferred EOR provider for this country, and have we vetted their local compliance track record?
Step 3 — Cross-functional triggers

For each function that needs to be looped in, state: what they need to do, and the specific questions legal should ask them. Do not just say "loop in finance." Draft the ask.

Tax counsel (always required before first hire)

What they need to do: PE risk analysis, determine whether entity is required for tax purposes, advise on equity tax treatment in this jurisdiction.

Questions legal should ask:

  • Does hiring a [role type] in [country] create a permanent establishment or taxable nexus before we have an entity?
  • What is our exposure window if we start hiring before the PE question is resolved?
  • How are our equity awards (RSUs/options) taxed in [country]? Do we need local tax counsel to advise employees at grant and vesting?
  • If we set up an entity, what intercompany services agreement is needed between the subsidiary and the US parent?

Finance / Payroll (required before first paycheck)

What they need to do: identify local payroll provider (or confirm EOR handles it), budget mandatory employer contributions, set up local banking if entity.

Questions legal should ask:

  • Have we identified a local payroll provider? (If EOR: confirm EOR handles payroll including local social contributions)
  • What are the mandatory employer contributions in [country] — pension, social insurance, healthcare — and are these budgeted in the comp model?
  • How will equity grants be administered for employees in [country]? Has anyone modeled the employer-side tax withholding obligations at vesting?

HR / Total Rewards (required before offer is made)

What they need to do: benefits benchmarking, comp benchmarking against local market, confirm mandatory vs. supplemental benefits.

Questions legal should ask:

  • What benefits are legally mandatory in [country] vs. market-standard? (Do not want to accidentally promise more than required or less than market)
  • Is our standard equity package competitive in this market, or does local practice differ significantly?
  • Who will be this person's day-to-day manager — local or remote from HQ? (Affects employee-representation analysis and employment agreement terms in some jurisdictions)

Outside counsel (required — do not skip)

What they need to do: research and advise on the local employment framework for this role and headcount, review/draft local employment agreement, flag any structural issues with the proposed arrangement.

The outside-counsel briefing request in Step 4 is the agenda for this engagement. Send it at the start — do not ask piecemeal.

Show full SKILL.md (749 more words)Show less
Step 4 — Country-specific briefing request

Instead of a stored country reference table, this skill produces a structured outside-counsel briefing request. Substantive local law (entity requirements, statutory benefits and contributions, termination protections, notice periods, employee-representation / works-council / collective-bargaining obligations, mandatory leave, restrictive covenants, data protection, work authorization) varies by country and by role and headcount and by industry, and changes frequently. Treat every country as a country that requires verification — do not rely on the skill's own knowledge.

Draft the briefing request below, tailored to the intake answers:

Outside counsel briefing request — [Country]

We are planning to hire [N] employees in [Country] starting [date], in the following roles: [roles]. Target headcount over 12 months: [N]. Preferred structure (subject to your advice and tax counsel): [EOR / entity / undecided]. We need a briefing covering each of the following. Please answer as questions with cites to primary law, not as a reference table — we want to be able to track changes over time.

  1. Entity and engagement structure — what are our options (direct hire via entity, EOR, contractor) and what are the practical and legal trade-offs for this headcount and these roles?

  2. Employment contract requirements — what form is required or standard? What must be included? What cannot be included or is unenforceable? What language or translation requirements apply?

  3. Termination — what are the notice requirements and severance obligations? How difficult is termination in practice (protected-cause standards, social-selection rules in RIFs, reasonable-notice common-law exposure)? What documentation standard should we establish from day one?

  4. Mandatory benefits and employer contributions — what must we provide by law (pension, social insurance, healthcare, paid leave, bonuses)? What are the current employer contribution rates we should budget? Please cite the controlling statute and verify currency.

  5. Restrictive covenants — are non-competes enforceable? Under what conditions and with what compensation requirements? What confidentiality and IP assignment language holds up?

  6. Employee representation — are there works council, employee representation, union, or collective bargaining requirements? At what headcount do they trigger? What consultation or co-determination rights apply? Are we covered by any sectoral collective agreement even if we are not unionized?

  7. Data protection — what obligations apply to employee data? Is there a data transfer mechanism needed for employee data flowing to the US?

  8. Work authorization — what permits or visas are required for foreign nationals? What are the processing timelines?

  9. Industry-specific rules — are there sector rules, awards, or collective agreements that apply to our industry regardless of whether we are unionized?

  10. Contractor/independent-contractor risk — what is the country's test for classification, and what are the deemed-employment or reclassification risks for any contractor arrangements we may consider?

  11. Equity / incentive compensation — any local tax, securities, or employment-law rules that govern how we grant RSUs, options, or other equity here?

  12. Day 1 compliance — what must be in place before the first employee starts? Registration requirements, notices, filings, posters?

  13. Top 2-3 things that surprise US companies hiring here for the first time — what do you wish clients had asked you earlier? What has changed recently that a US team might not have caught?

Add this briefing request to the expansion tracker as a single open item: owner = Outside Counsel, status = open, with the full briefing agenda in the questions field. If the jurisdiction is one the team has asked about before, still send the briefing — this is a currency check, not a first contact.

Step 5 — Create the expansion tracker

Write a new file to ~/.claude/plugins/config/claude-for-legal/employment-legal/expansion-[country-slug].yaml with all open items identified in Steps 2-4. This file persists across sessions.

Format:

yaml
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]
country: [Country name]
country_slug: [lowercase-hyphenated]
kickoff_date: [ISO date]
first_hire_target: [ISO date or "TBD"]
headcount_12mo: [N]
roles: [list]
strategic_commitment: [testing / long-term]
eor_or_entity: [EOR / entity / undecided]
outside_counsel_engaged: [true / false]
pe_risk_flagged: [true / false]
last_updated: [ISO date]

open_items:
  - id: 1
    category: [structure / tax / finance / hr / outside-counsel / compliance]
    item: "[what needs to happen]"
    owner: "[function or person]"
    status: [open / in-progress / done / blocked]
    due: [ISO date or null]
    questions:
      - "[specific question drafted in Steps 2-4]"
    notes: ""

  - id: 2
    [etc.]

Generate one open item per action identified across Steps 2-4. Do not collapse multiple actions into one item — each item should be completable and attributable to a single owner.

Step 6 — Output

Jurisdiction assumption. This plan frames the expansion to the single country identified in intake. Local employment law, tax rules, employee-representation obligations, and data-protection requirements vary materially by country, region, industry, and headcount, and change frequently. Every substantive local-law answer comes from the outside-counsel briefing request, not from this skill. If the plan is adapted for another country later, re-run the briefing.

markdown
[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]

## International Expansion: [Country] — [Date]

**First hire target:** [date]
**Headcount (12 months):** [N]
**Roles:** [list]
**Tracker:** ~/.claude/plugins/config/claude-for-legal/employment-legal/expansion-[slug].yaml

---

### EOR vs. Entity

[Framing from Step 2 — table, PE risk flag if applicable, questions for CFO/tax]

---

### Who needs to be looped in — and what to ask them

**Tax counsel** — [N] questions
[Questions from Step 3]

**Finance / Payroll** — [N] questions
[Questions from Step 3]

**HR / Total Rewards** — [N] questions
[Questions from Step 3]

**Outside counsel** — see briefing request below
[Full briefing request from Step 4]

---

### Open items ([N] total)

| # | Item | Owner | Status |
|---|---|---|---|
| 1 | [item] | [owner] | Open |
[etc.]

---

Run `/employment-legal:expansion-update [country]` to update status
as items close.

What this skill does NOT do

  • Advise on specific local employment law — that is outside counsel's job.
  • Make the EOR vs. entity decision — frames it for the right decision-makers.
  • Draft the local employment agreement — flags that outside counsel must do this.
  • State country-specific rules from its own knowledge — every country is routed through an outside-counsel briefing.
  • Substitute for outside counsel engagement — every new country requires local counsel, no exceptions.

© anthropics, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in employment-legal/skills/international-expansion of anthropics/claude-for-legal.

Open the folder on GitHubat commit 4a6c651

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in anthropics/claude-for-legal, which our catalogue first saw on October 7, 2026.

Compare with similar skills

International Expansion next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

International Expansion compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
International Expansion this skillanthropics/claude-for-legal9.6k3 repos~3.9kAutomated safety check: PassApache-2.0
Internal Commsalirezarezvani/claude-skills28k—~3.4kAutomated safety check: PassMIT
Internal Communicationsickn33/agentic-awesome-skills47k1 repos~3.4kAutomated safety check: PassMIT
International ExpansionRefoundAI/lenny-skills1.4k—~1.7kAutomated safety check: PassMIT
Internal Communications Writeranthropics/skills180k38 repos~378Automated safety check: PassApache-2.0
Internal Comms Anthropicsickn33/agentic-awesome-skills47k1 repos~702Automated safety check: PassApache-2.0

Similar skills

  • Internal Comms

    alirezarezvani/claude-skills

    A skill your agent uses when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement…

    28k GitHub stars~3.4k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Internal Communication

    sickn33/agentic-awesome-skills

    Internal communication log: title, type, date, department, host and attendees, agenda, action items, follow-up date, meeting link and delivery status.

    47k GitHub starsUsed in 1 repo~3.4k tokens
    Writing & ContentAuto-check passed
  • International Expansion

    RefoundAI/lenny-skills

    Help users navigate the complexities of launching in new countries by identifying high potential markets and adapting products to local cultural and economic contexts.

    1.4k GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Official

    A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…

    180k GitHub starsUsed in 38 repos~378 tokens
    Writing & ContentAuto-check passed
  • Internal Comms Anthropic

    sickn33/agentic-awesome-skills

    Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources.

    47k GitHub starsUsed in 1 repo~702 tokens
    Writing & ContentAuto-check passed
  • Intl Expansion

    alirezarezvani/claude-skills

    International market expansion strategy. An agent skill from alirezarezvani/claude-skills.

    28k GitHub starsUsed in 1 repo~1.1k tokens
    Marketing & SEOAuto-check passed

More from anthropics/claude-for-legal

All 147 skills in this repo
  • Legal Clinic Client Intake

    anthropics/claude-for-legal

    Official

    Structures a legal clinic client intake interview and produces a case summary with cross-area issue spotting, conflict flags and triage classification.

    9.6k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed
  • Supervisor Review Queue

    anthropics/claude-for-legal

    Official

    Holds student work in a queue for a legal clinic professor to approve, edit-then-approve or return before anything reaches clients or courts.

    9.6k GitHub starsUsed in 3 repos~1.1k tokens
    Auto-check passed
  • Tabular Document Review

    anthropics/claude-for-legal

    Official

    Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.

    9.6k GitHub starsUsed in 3 repos~4.3k tokens
    Auto-check passed
  • Product Launch Legal Review

    anthropics/claude-for-legal

    Official

    Runs a category-by-category legal review of a product launch from a PRD or tracker ticket, calibrated to your team's framework, and writes a review memo in house format.

    9.6k GitHub starsUsed in 2 repos~5k tokens
    Auto-check passed
  • Legal Skills Registry Browser

    anthropics/claude-for-legal

    Official

    Searches watched registries for community legal skills, shows matches with descriptions and offers the full SKILL.md before anything is installed.

    9.6k GitHub starsUsed in 2 repos~620 tokens
    Auto-check passed
  • Contract Renewal Tracker

    anthropics/claude-for-legal

    Official

    Shows which contracts renew soon and when notice must be sent by, working from a maintained renewal register, and warns about missed cancellation windows.

    9.6k GitHub starsUsed in 2 repos~3.1k tokens
    Auto-check passed

Questions about International Expansion

What does International Expansion do?

Reference: implementation-planning framework for international hiring — EOR vs. International Expansion is an agent skill from anthropics/claude-for-legal, published by the product's own GitHub organization. Reference: implementation-planning framework for international hiring — EOR vs.

When should I use International Expansion?

International Expansion fits situations like: structured outside-counsel briefing requests; A persistent gap tracker.

How do I install International Expansion in Claude Code?

Run `npx skills add anthropics/claude-for-legal --skill international-expansion -a claude-code`. Or copy the skill folder (employment-legal/skills/international-expansion in anthropics/claude-for-legal) into .claude/skills/international-expansion in your project. Claude Code loads it when a task matches its description.

How do I install International Expansion in Codex?

Run `npx skills add anthropics/claude-for-legal --skill international-expansion -a codex`. Or copy the skill folder (employment-legal/skills/international-expansion in anthropics/claude-for-legal) into .agents/skills/international-expansion in your project. Codex loads it when a task matches its description.

Can I use International Expansion in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add anthropics/claude-for-legal --skill international-expansion -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/international-expansion, .gemini/skills/international-expansion, .github/skills/international-expansion and .opencode/skills/international-expansion in your project.

What does International Expansion need to run?

SKILL.md names no scripts, command-line tools or credentials: International Expansion is instructions for the agent only.

Does International Expansion access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is International Expansion safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does International Expansion use?

International Expansion is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does International Expansion use?

About 3.9k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to International Expansion?

Skills that share tags, products or a category with International Expansion: Internal Comms (alirezarezvani/claude-skills, 28k stars), Internal Communication (sickn33/agentic-awesome-skills, 47k stars), International Expansion (RefoundAI/lenny-skills, 1.4k stars) and Internal Communications Writer (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains International Expansion?

anthropics (a GitHub organization, an official publisher) maintains it in anthropics/claude-for-legal, which has 9,633 GitHub stars. The repository holds 147 skills in this directory. The repository was last updated on September 29, 2026.

Source: anthropics/claude-for-legal on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.