[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718E6244AHDX9SXFSC2JPV6":3,"skill-same:01M718E6244AHDX9SXFSC2JPV6":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M718E6244AHDX9SXFSC2JPV6","international-expansion",null,"Reference: implementation-planning framework for international hiring — EOR vs. entity decision framing, cross-functional triggers for tax\u002Ffinance\u002FHR, structured outside-counsel briefing requests, and a persistent gap tracker. Loaded by \u002Fexpansion-kickoff and \u002Fexpansion-update; not invoked directly.","anthropics\u002Fclaude-for-legal","anthropics","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F76263028?v=4","01M697XGDPXJAVQ8391V2BCYTE","Anthropic","01M7189QY7HXHMC9BW4MFHPZ6H",10006,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Femployment-legal\u002Fskills\u002Finternational-expansion\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"international expansion","expansion","international","tax","update","Hiring","tracker","requests","functional","Counsel","gap","kickoff","hr","false","briefing","triggers","decision","planning framework","for","planning","2026-11-10 10:12:30",false,"---\nname: international-expansion\ndescription: >\n  Reference: implementation-planning framework for international hiring — EOR\n  vs. entity decision framing, cross-functional triggers for tax\u002Ffinance\u002FHR,\n  structured outside-counsel briefing requests, and a persistent gap tracker.\n  Loaded by \u002Fexpansion-kickoff and \u002Fexpansion-update; not invoked directly.\nuser-invocable: false\n---\n\n# International Expansion Skill\n\n## Matter context\n\n**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 `\u002Femployment-legal:matter-workspace switch \u003Cslug>` or say `practice-level`.\" Load the active matter's `matter.md` for matter-specific context and overrides. Write outputs to the matter folder at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nInternational hiring gets handled sloppily at scaleups because nobody owns\nthe full picture. Legal knows the employment-law questions but not the PE\nrisk questions. Finance knows the cost model but not the employee-representation\ntriggers. HR knows the comp benchmarks but not the Day 1 compliance requirements.\n\nThis skill doesn't replace any of those functions. It maps the terrain, drafts\nthe right questions for each stakeholder, produces a briefing request that\nwalks outside counsel through the country-specific issues, and creates a\ntracker that keeps the project moving across sessions.\n\nThis skill assumes expansion is decided. It is not a \"should we expand?\"\nframework.\n\nThis skill does not contain country-specific employment law. The substantive\nrules change frequently and vary by role, headcount, and industry — the skill\nroutes every country through an outside-counsel briefing rather than relying\non a stored reference table.\n\n## Load context\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002FCLAUDE.md` → jurisdictional footprint, escalation table, any existing\nexpansion notes.\n\n## Output header\n\nPrepend the work-product header from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002FCLAUDE.md` → `## Outputs` (it differs by user role — see `## Who's using this`).\n\n## Workflow\n\n### Step 1 — Information gathering\n\nAsk all of the following in a single block:\n\n> Before I build the expansion plan I need to understand the shape of this\n> expansion. Please answer what you can — gaps in the answers are themselves\n> useful data:\n>\n> **The expansion**\n> - Which country?\n> - What roles are you hiring? (Job function matters — a sales rep closing\n>   deals creates different legal exposure than an engineer writing code)\n> - How many hires are planned in the next 12 months?\n> - When do you need the first person to start?\n>\n> **Current state**\n> - Do you already have a legal entity in this country?\n> - Have you used an EOR provider before? Are you already considering one?\n> - Has tax or finance been looped in yet?\n> - Do you have outside employment counsel in this country?\n>\n> **Strategic context**\n> - Is this a long-term strategic commitment (building a real team) or\n>   testing the market (one or two hires, see how it goes)?\n> - Who is the executive sponsor making the structure decision?\n\nWait for responses before proceeding.\n\n### Step 2 — EOR vs. entity framing\n\nDo not make this decision. Frame it with enough precision that the CFO and\ntax counsel can make it.\n\nWork through the following factors against the intake answers and produce a\nstructured framing document:\n\n**The core trade-off:**\n\n| Factor | Points toward EOR | Points toward Entity |\n|---|---|---|\n| Headcount in 12 months | Fewer hires | More hires |\n| Timeline to first hire | Short runway | Longer runway available |\n| Strategic commitment | Testing the market | Long-term presence |\n| Cost sensitivity | EOR markup acceptable | Scale makes entity more efficient |\n| Control needs | Low — EOR employer handles local HR | High — want direct employer relationship |\n| IP sensitivity | Lower | Higher — entity ownership cleaner |\n\nSpecific headcount break-even points, EOR markup ranges, setup costs, and\ntimelines vary by country and provider — do not hardcode them. Route those\nquestions to tax\u002Ffinance and the EOR provider.\n\n**PE risk flag (route to tax counsel):**\nIf roles include sales, business development, account management, or anyone\nwith authority to negotiate or sign contracts on behalf of the company —\nflag this explicitly:\n\n> PE Risk: [Role type] may create a taxable permanent establishment in\n> [country] even before a legal entity exists. This is a tax question, not\n> an employment question. Tax counsel must assess before the first hire.\n\n**Produce the question for the CFO\u002Ftax:**\n\n> Questions for your CFO and tax counsel:\n> - At [N] hires over 12 months, at what headcount does entity setup become\n>   more cost-effective than EOR (accounting for EOR markup, setup costs,\n>   and ongoing compliance burden)?\n> - [If PE-risk roles:] Do these role types create a taxable permanent\n>   establishment in [country]? If yes, does that change the entity timeline?\n> - If we start with EOR and convert to entity later, what are the transition\n>   risks for the employees already on the EOR?\n> - Who is our preferred EOR provider for this country, and have we vetted\n>   their local compliance track record?\n\n### Step 3 — Cross-functional triggers\n\nFor each function that needs to be looped in, state: what they need to do,\nand the specific questions legal should ask them. Do not just say \"loop in\nfinance.\" Draft the ask.\n\n**Tax counsel** (always required before first hire)\n\nWhat they need to do: PE risk analysis, determine whether entity is required\nfor tax purposes, advise on equity tax treatment in this jurisdiction.\n\nQuestions legal should ask:\n- Does hiring a [role type] in [country] create a permanent establishment or\n  taxable nexus before we have an entity?\n- What is our exposure window if we start hiring before the PE question is\n  resolved?\n- How are our equity awards (RSUs\u002Foptions) taxed in [country]? Do we need\n  local tax counsel to advise employees at grant and vesting?\n- If we set up an entity, what intercompany services agreement is needed\n  between the subsidiary and the US parent?\n\n**Finance \u002F Payroll** (required before first paycheck)\n\nWhat they need to do: identify local payroll provider (or confirm EOR handles\nit), budget mandatory employer contributions, set up local banking if entity.\n\nQuestions legal should ask:\n- Have we identified a local payroll provider? (If EOR: confirm EOR handles\n  payroll including local social contributions)\n- What are the mandatory employer contributions in [country] — pension,\n  social insurance, healthcare — and are these budgeted in the comp model?\n- How will equity grants be administered for employees in [country]? Has\n  anyone modeled the employer-side tax withholding obligations at vesting?\n\n**HR \u002F Total Rewards** (required before offer is made)\n\nWhat they need to do: benefits benchmarking, comp benchmarking against local\nmarket, confirm mandatory vs. supplemental benefits.\n\nQuestions legal should ask:\n- What benefits are legally mandatory in [country] vs. market-standard? (Do\n  not want to accidentally promise more than required or less than market)\n- Is our standard equity package competitive in this market, or does local\n  practice differ significantly?\n- Who will be this person's day-to-day manager — local or remote from HQ?\n  (Affects employee-representation analysis and employment agreement terms\n  in some jurisdictions)\n\n**Outside counsel** (required — do not skip)\n\nWhat they need to do: research and advise on the local employment framework\nfor this role and headcount, review\u002Fdraft local employment agreement, flag\nany structural issues with the proposed arrangement.\n\nThe outside-counsel briefing request in Step 4 is the agenda for this\nengagement. Send it at the start — do not ask piecemeal.\n\n### Step 4 — Country-specific briefing request\n\nInstead of a stored country reference table, this skill produces a structured\noutside-counsel briefing request. Substantive local law (entity requirements,\nstatutory benefits and contributions, termination protections, notice periods,\nemployee-representation \u002F works-council \u002F collective-bargaining obligations,\nmandatory leave, restrictive covenants, data protection, work authorization)\nvaries by country *and* by role and headcount *and* by industry, and changes\nfrequently. Treat every country as a country that requires verification — do\nnot rely on the skill's own knowledge.\n\nDraft the briefing request below, tailored to the intake answers:\n\n**Outside counsel briefing request — [Country]**\n\n> We are planning to hire [N] employees in [Country] starting [date], in the\n> following roles: [roles]. Target headcount over 12 months: [N]. Preferred\n> structure (subject to your advice and tax counsel): [EOR \u002F entity \u002F\n> undecided]. We need a briefing covering each of the following. Please\n> answer as questions with cites to primary law, not as a reference table —\n> we want to be able to track changes over time.\n>\n> 1. **Entity and engagement structure** — what are our options (direct\n>    hire via entity, EOR, contractor) and what are the practical and legal\n>    trade-offs for this headcount and these roles?\n>\n> 2. **Employment contract requirements** — what form is required or standard?\n>    What must be included? What cannot be included or is unenforceable?\n>    What language or translation requirements apply?\n>\n> 3. **Termination** — what are the notice requirements and severance\n>    obligations? How difficult is termination in practice (protected-cause\n>    standards, social-selection rules in RIFs, reasonable-notice common-law\n>    exposure)? What documentation standard should we establish from day one?\n>\n> 4. **Mandatory benefits and employer contributions** — what must we provide\n>    by law (pension, social insurance, healthcare, paid leave, bonuses)?\n>    What are the current employer contribution rates we should budget?\n>    Please cite the controlling statute and verify currency.\n>\n> 5. **Restrictive covenants** — are non-competes enforceable? Under what\n>    conditions and with what compensation requirements? What confidentiality\n>    and IP assignment language holds up?\n>\n> 6. **Employee representation** — are there works council, employee\n>    representation, union, or collective bargaining requirements? At what\n>    headcount do they trigger? What consultation or co-determination rights\n>    apply? Are we covered by any sectoral collective agreement even if we\n>    are not unionized?\n>\n> 7. **Data protection** — what obligations apply to employee data? Is there\n>    a data transfer mechanism needed for employee data flowing to the US?\n>\n> 8. **Work authorization** — what permits or visas are required for foreign\n>    nationals? What are the processing timelines?\n>\n> 9. **Industry-specific rules** — are there sector rules, awards, or\n>    collective agreements that apply to our industry regardless of whether\n>    we are unionized?\n>\n> 10. **Contractor\u002Findependent-contractor risk** — what is the country's test\n>     for classification, and what are the deemed-employment or reclassification\n>     risks for any contractor arrangements we may consider?\n>\n> 11. **Equity \u002F incentive compensation** — any local tax, securities, or\n>     employment-law rules that govern how we grant RSUs, options, or other\n>     equity here?\n>\n> 12. **Day 1 compliance** — what must be in place before the first employee\n>     starts? Registration requirements, notices, filings, posters?\n>\n> 13. **Top 2-3 things that surprise US companies hiring here for the first\n>     time** — what do you wish clients had asked you earlier? What has\n>     *changed recently* that a US team might not have caught?\n\nAdd this briefing request to the expansion tracker as a single open item:\nowner = Outside Counsel, status = open, with the full briefing agenda in\nthe questions field. If the jurisdiction is one the team has asked about\nbefore, still send the briefing — this is a currency check, not a first\ncontact.\n\n### Step 5 — Create the expansion tracker\n\nWrite a new file to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002Fexpansion-[country-slug].yaml` with all open items\nidentified in Steps 2-4. This file persists across sessions.\n\nFormat:\n\n```yaml\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\ncountry: [Country name]\ncountry_slug: [lowercase-hyphenated]\nkickoff_date: [ISO date]\nfirst_hire_target: [ISO date or \"TBD\"]\nheadcount_12mo: [N]\nroles: [list]\nstrategic_commitment: [testing \u002F long-term]\neor_or_entity: [EOR \u002F entity \u002F undecided]\noutside_counsel_engaged: [true \u002F false]\npe_risk_flagged: [true \u002F false]\nlast_updated: [ISO date]\n\nopen_items:\n  - id: 1\n    category: [structure \u002F tax \u002F finance \u002F hr \u002F outside-counsel \u002F compliance]\n    item: \"[what needs to happen]\"\n    owner: \"[function or person]\"\n    status: [open \u002F in-progress \u002F done \u002F blocked]\n    due: [ISO date or null]\n    questions:\n      - \"[specific question drafted in Steps 2-4]\"\n    notes: \"\"\n\n  - id: 2\n    [etc.]\n```\n\nGenerate one open item per action identified across Steps 2-4. Do not collapse\nmultiple actions into one item — each item should be completable and\nattributable to a single owner.\n\n### Step 6 — Output\n\n> **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.\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n## International Expansion: [Country] — [Date]\n\n**First hire target:** [date]\n**Headcount (12 months):** [N]\n**Roles:** [list]\n**Tracker:** ~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002Fexpansion-[slug].yaml\n\n---\n\n### EOR vs. Entity\n\n[Framing from Step 2 — table, PE risk flag if applicable, questions for CFO\u002Ftax]\n\n---\n\n### Who needs to be looped in — and what to ask them\n\n**Tax counsel** — [N] questions\n[Questions from Step 3]\n\n**Finance \u002F Payroll** — [N] questions\n[Questions from Step 3]\n\n**HR \u002F Total Rewards** — [N] questions\n[Questions from Step 3]\n\n**Outside counsel** — see briefing request below\n[Full briefing request from Step 4]\n\n---\n\n### Open items ([N] total)\n\n| # | Item | Owner | Status |\n|---|---|---|---|\n| 1 | [item] | [owner] | Open |\n[etc.]\n\n---\n\nRun `\u002Femployment-legal:expansion-update [country]` to update status\nas items close.\n```\n\n## What this skill does NOT do\n\n- Advise on specific local employment law — that is outside counsel's job.\n- Make the EOR vs. entity decision — frames it for the right decision-makers.\n- Draft the local employment agreement — flags that outside counsel must do\n  this.\n- State country-specific rules from its own knowledge — every country is\n  routed through an outside-counsel briefing.\n- Substitute for outside counsel engagement — every new country requires\n  local counsel, no exceptions.\n","# International Expansion Skill\n\n## Matter context\n\n**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 `\u002Femployment-legal:matter-workspace switch \u003Cslug>` or say `practice-level`.\" Load the active matter's `matter.md` for matter-specific context and overrides. Write outputs to the matter folder at `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002Fmatters\u002F\u003Cmatter-slug>\u002F`. Never read another matter's files unless `Cross-matter context` is `on`.\n\n---\n\n## Purpose\n\nInternational hiring gets handled sloppily at scaleups because nobody owns\nthe full picture. Legal knows the employment-law questions but not the PE\nrisk questions. Finance knows the cost model but not the employee-representation\ntriggers. HR knows the comp benchmarks but not the Day 1 compliance requirements.\n\nThis skill doesn't replace any of those functions. It maps the terrain, drafts\nthe right questions for each stakeholder, produces a briefing request that\nwalks outside counsel through the country-specific issues, and creates a\ntracker that keeps the project moving across sessions.\n\nThis skill assumes expansion is decided. It is not a \"should we expand?\"\nframework.\n\nThis skill does not contain country-specific employment law. The substantive\nrules change frequently and vary by role, headcount, and industry — the skill\nroutes every country through an outside-counsel briefing rather than relying\non a stored reference table.\n\n## Load context\n\nRead `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002FCLAUDE.md` → jurisdictional footprint, escalation table, any existing\nexpansion notes.\n\n## Output header\n\nPrepend the work-product header from `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002FCLAUDE.md` → `## Outputs` (it differs by user role — see `## Who's using this`).\n\n## Workflow\n\n### Step 1 — Information gathering\n\nAsk all of the following in a single block:\n\n> Before I build the expansion plan I need to understand the shape of this\n> expansion. Please answer what you can — gaps in the answers are themselves\n> useful data:\n>\n> **The expansion**\n> - Which country?\n> - What roles are you hiring? (Job function matters — a sales rep closing\n>   deals creates different legal exposure than an engineer writing code)\n> - How many hires are planned in the next 12 months?\n> - When do you need the first person to start?\n>\n> **Current state**\n> - Do you already have a legal entity in this country?\n> - Have you used an EOR provider before? Are you already considering one?\n> - Has tax or finance been looped in yet?\n> - Do you have outside employment counsel in this country?\n>\n> **Strategic context**\n> - Is this a long-term strategic commitment (building a real team) or\n>   testing the market (one or two hires, see how it goes)?\n> - Who is the executive sponsor making the structure decision?\n\nWait for responses before proceeding.\n\n### Step 2 — EOR vs. entity framing\n\nDo not make this decision. Frame it with enough precision that the CFO and\ntax counsel can make it.\n\nWork through the following factors against the intake answers and produce a\nstructured framing document:\n\n**The core trade-off:**\n\n| Factor | Points toward EOR | Points toward Entity |\n|---|---|---|\n| Headcount in 12 months | Fewer hires | More hires |\n| Timeline to first hire | Short runway | Longer runway available |\n| Strategic commitment | Testing the market | Long-term presence |\n| Cost sensitivity | EOR markup acceptable | Scale makes entity more efficient |\n| Control needs | Low — EOR employer handles local HR | High — want direct employer relationship |\n| IP sensitivity | Lower | Higher — entity ownership cleaner |\n\nSpecific headcount break-even points, EOR markup ranges, setup costs, and\ntimelines vary by country and provider — do not hardcode them. Route those\nquestions to tax\u002Ffinance and the EOR provider.\n\n**PE risk flag (route to tax counsel):**\nIf roles include sales, business development, account management, or anyone\nwith authority to negotiate or sign contracts on behalf of the company —\nflag this explicitly:\n\n> PE Risk: [Role type] may create a taxable permanent establishment in\n> [country] even before a legal entity exists. This is a tax question, not\n> an employment question. Tax counsel must assess before the first hire.\n\n**Produce the question for the CFO\u002Ftax:**\n\n> Questions for your CFO and tax counsel:\n> - At [N] hires over 12 months, at what headcount does entity setup become\n>   more cost-effective than EOR (accounting for EOR markup, setup costs,\n>   and ongoing compliance burden)?\n> - [If PE-risk roles:] Do these role types create a taxable permanent\n>   establishment in [country]? If yes, does that change the entity timeline?\n> - If we start with EOR and convert to entity later, what are the transition\n>   risks for the employees already on the EOR?\n> - Who is our preferred EOR provider for this country, and have we vetted\n>   their local compliance track record?\n\n### Step 3 — Cross-functional triggers\n\nFor each function that needs to be looped in, state: what they need to do,\nand the specific questions legal should ask them. Do not just say \"loop in\nfinance.\" Draft the ask.\n\n**Tax counsel** (always required before first hire)\n\nWhat they need to do: PE risk analysis, determine whether entity is required\nfor tax purposes, advise on equity tax treatment in this jurisdiction.\n\nQuestions legal should ask:\n- Does hiring a [role type] in [country] create a permanent establishment or\n  taxable nexus before we have an entity?\n- What is our exposure window if we start hiring before the PE question is\n  resolved?\n- How are our equity awards (RSUs\u002Foptions) taxed in [country]? Do we need\n  local tax counsel to advise employees at grant and vesting?\n- If we set up an entity, what intercompany services agreement is needed\n  between the subsidiary and the US parent?\n\n**Finance \u002F Payroll** (required before first paycheck)\n\nWhat they need to do: identify local payroll provider (or confirm EOR handles\nit), budget mandatory employer contributions, set up local banking if entity.\n\nQuestions legal should ask:\n- Have we identified a local payroll provider? (If EOR: confirm EOR handles\n  payroll including local social contributions)\n- What are the mandatory employer contributions in [country] — pension,\n  social insurance, healthcare — and are these budgeted in the comp model?\n- How will equity grants be administered for employees in [country]? Has\n  anyone modeled the employer-side tax withholding obligations at vesting?\n\n**HR \u002F Total Rewards** (required before offer is made)\n\nWhat they need to do: benefits benchmarking, comp benchmarking against local\nmarket, confirm mandatory vs. supplemental benefits.\n\nQuestions legal should ask:\n- What benefits are legally mandatory in [country] vs. market-standard? (Do\n  not want to accidentally promise more than required or less than market)\n- Is our standard equity package competitive in this market, or does local\n  practice differ significantly?\n- Who will be this person's day-to-day manager — local or remote from HQ?\n  (Affects employee-representation analysis and employment agreement terms\n  in some jurisdictions)\n\n**Outside counsel** (required — do not skip)\n\nWhat they need to do: research and advise on the local employment framework\nfor this role and headcount, review\u002Fdraft local employment agreement, flag\nany structural issues with the proposed arrangement.\n\nThe outside-counsel briefing request in Step 4 is the agenda for this\nengagement. Send it at the start — do not ask piecemeal.\n\n### Step 4 — Country-specific briefing request\n\nInstead of a stored country reference table, this skill produces a structured\noutside-counsel briefing request. Substantive local law (entity requirements,\nstatutory benefits and contributions, termination protections, notice periods,\nemployee-representation \u002F works-council \u002F collective-bargaining obligations,\nmandatory leave, restrictive covenants, data protection, work authorization)\nvaries by country *and* by role and headcount *and* by industry, and changes\nfrequently. Treat every country as a country that requires verification — do\nnot rely on the skill's own knowledge.\n\nDraft the briefing request below, tailored to the intake answers:\n\n**Outside counsel briefing request — [Country]**\n\n> We are planning to hire [N] employees in [Country] starting [date], in the\n> following roles: [roles]. Target headcount over 12 months: [N]. Preferred\n> structure (subject to your advice and tax counsel): [EOR \u002F entity \u002F\n> undecided]. We need a briefing covering each of the following. Please\n> answer as questions with cites to primary law, not as a reference table —\n> we want to be able to track changes over time.\n>\n> 1. **Entity and engagement structure** — what are our options (direct\n>    hire via entity, EOR, contractor) and what are the practical and legal\n>    trade-offs for this headcount and these roles?\n>\n> 2. **Employment contract requirements** — what form is required or standard?\n>    What must be included? What cannot be included or is unenforceable?\n>    What language or translation requirements apply?\n>\n> 3. **Termination** — what are the notice requirements and severance\n>    obligations? How difficult is termination in practice (protected-cause\n>    standards, social-selection rules in RIFs, reasonable-notice common-law\n>    exposure)? What documentation standard should we establish from day one?\n>\n> 4. **Mandatory benefits and employer contributions** — what must we provide\n>    by law (pension, social insurance, healthcare, paid leave, bonuses)?\n>    What are the current employer contribution rates we should budget?\n>    Please cite the controlling statute and verify currency.\n>\n> 5. **Restrictive covenants** — are non-competes enforceable? Under what\n>    conditions and with what compensation requirements? What confidentiality\n>    and IP assignment language holds up?\n>\n> 6. **Employee representation** — are there works council, employee\n>    representation, union, or collective bargaining requirements? At what\n>    headcount do they trigger? What consultation or co-determination rights\n>    apply? Are we covered by any sectoral collective agreement even if we\n>    are not unionized?\n>\n> 7. **Data protection** — what obligations apply to employee data? Is there\n>    a data transfer mechanism needed for employee data flowing to the US?\n>\n> 8. **Work authorization** — what permits or visas are required for foreign\n>    nationals? What are the processing timelines?\n>\n> 9. **Industry-specific rules** — are there sector rules, awards, or\n>    collective agreements that apply to our industry regardless of whether\n>    we are unionized?\n>\n> 10. **Contractor\u002Findependent-contractor risk** — what is the country's test\n>     for classification, and what are the deemed-employment or reclassification\n>     risks for any contractor arrangements we may consider?\n>\n> 11. **Equity \u002F incentive compensation** — any local tax, securities, or\n>     employment-law rules that govern how we grant RSUs, options, or other\n>     equity here?\n>\n> 12. **Day 1 compliance** — what must be in place before the first employee\n>     starts? Registration requirements, notices, filings, posters?\n>\n> 13. **Top 2-3 things that surprise US companies hiring here for the first\n>     time** — what do you wish clients had asked you earlier? What has\n>     *changed recently* that a US team might not have caught?\n\nAdd this briefing request to the expansion tracker as a single open item:\nowner = Outside Counsel, status = open, with the full briefing agenda in\nthe questions field. If the jurisdiction is one the team has asked about\nbefore, still send the briefing — this is a currency check, not a first\ncontact.\n\n### Step 5 — Create the expansion tracker\n\nWrite a new file to `~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002Fexpansion-[country-slug].yaml` with all open items\nidentified in Steps 2-4. This file persists across sessions.\n\nFormat:\n\n```yaml\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\ncountry: [Country name]\ncountry_slug: [lowercase-hyphenated]\nkickoff_date: [ISO date]\nfirst_hire_target: [ISO date or \"TBD\"]\nheadcount_12mo: [N]\nroles: [list]\nstrategic_commitment: [testing \u002F long-term]\neor_or_entity: [EOR \u002F entity \u002F undecided]\noutside_counsel_engaged: [true \u002F false]\npe_risk_flagged: [true \u002F false]\nlast_updated: [ISO date]\n\nopen_items:\n  - id: 1\n    category: [structure \u002F tax \u002F finance \u002F hr \u002F outside-counsel \u002F compliance]\n    item: \"[what needs to happen]\"\n    owner: \"[function or person]\"\n    status: [open \u002F in-progress \u002F done \u002F blocked]\n    due: [ISO date or null]\n    questions:\n      - \"[specific question drafted in Steps 2-4]\"\n    notes: \"\"\n\n  - id: 2\n    [etc.]\n```\n\nGenerate one open item per action identified across Steps 2-4. Do not collapse\nmultiple actions into one item — each item should be completable and\nattributable to a single owner.\n\n### Step 6 — Output\n\n> **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.\n\n```markdown\n[WORK-PRODUCT HEADER — per plugin config ## Outputs — differs by role; see `## Who's using this`]\n\n## International Expansion: [Country] — [Date]\n\n**First hire target:** [date]\n**Headcount (12 months):** [N]\n**Roles:** [list]\n**Tracker:** ~\u002F.claude\u002Fplugins\u002Fconfig\u002Fclaude-for-legal\u002Femployment-legal\u002Fexpansion-[slug].yaml\n\n---\n\n### EOR vs. Entity\n\n[Framing from Step 2 — table, PE risk flag if applicable, questions for CFO\u002Ftax]\n\n---\n\n### Who needs to be looped in — and what to ask them\n\n**Tax counsel** — [N] questions\n[Questions from Step 3]\n\n**Finance \u002F Payroll** — [N] questions\n[Questions from Step 3]\n\n**HR \u002F Total Rewards** — [N] questions\n[Questions from Step 3]\n\n**Outside counsel** — see briefing request below\n[Full briefing request from Step 4]\n\n---\n\n### Open items ([N] total)\n\n| # | Item | Owner | Status |\n|---|---|---|---|\n| 1 | [item] | [owner] | Open |\n[etc.]\n\n---\n\nRun `\u002Femployment-legal:expansion-update [country]` to update status\nas items close.\n```\n\n## What this skill does NOT do\n\n- Advise on specific local employment law — that is outside counsel's job.\n- Make the EOR vs. entity decision — frames it for the right decision-makers.\n- Draft the local employment agreement — flags that outside counsel must do\n  this.\n- State country-specific rules from its own knowledge — every country is\n  routed through an outside-counsel briefing.\n- Substitute for outside counsel engagement — every new country requires\n  local counsel, no exceptions.\n",{"name":5,"description":44,"user-invocable":40},"Reference: implementation-planning framework for international hiring — EOR vs. entity decision framing, cross-functional triggers for tax\u002Ffinance\u002FHR, structured outside-counsel briefing requests, and a persistent gap tracker. Loaded by \u002Fexpansion-kickoff and \u002Fexpansion-update; not invoked directly.\n","main","4a6c651889c97cc9140580363c73e0eb17379c2b","employment-legal\u002Fskills\u002Finternational-expansion",1968,"https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal","https:\u002F\u002Fgithub.com\u002Fanthropics","https:\u002F\u002Fanthropic.com","2026-11-14 23:30:58",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add anthropics\u002Fclaude-for-legal --skill international-expansion",{"tool":59,"command":60},"bunx","bunx skills add anthropics\u002Fclaude-for-legal --skill international-expansion",{"tool":62,"command":63},"pnpm","pnpm dlx skills add anthropics\u002Fclaude-for-legal --skill international-expansion","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Femployment-legal\u002Fskills\u002Finternational-expansion\u002FSKILL.md",true,[],[68,98,119,138,160,172],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"publishedAt":39},"01M718SG9G2R92ECCD0HYK2R5E","reg-feed-watcher","Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says \"check the feeds\", \"what's new\", \"regulatory update\", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Freg-feed-watcher\u002FSKILL.md",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[80,81,82,83,84,85,86,87,37,88,89,90,91,92,93,94,95,23,96,97],"reg","watcher","reg feed watcher","running","feeds","filtered","diff","development","classification","new","now","use","scheduled","when","check","last","report","regulatory",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":39},"01M718SCRTBN55DMTVSPG67A7N","policy-redraft","Produce a proposed marked-up policy redraft that closes a gap found by \u002Fregulatory-legal:gaps or \u002Fregulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says \"redraft the policy\", \"draft the policy fix\", \"mark up the policy\", or when gap-surfacer hands off a gap for drafting.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-redraft\u002FSKILL.md",[],[105,106,86,37,107,108,109,91,110,93,111,112,113,114,115,29,116,117,97,118],"policy","policy redraft","up","fix","produce","documents","drafting","gaps","review","draft","id","mark","first","direct",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":39},"01M718S8RV0C4NMVKG078CBFXP","policy-diff","Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says \"diff this reg against our policies\", \"which policy does this affect\", or \"gap analysis\", or when reg-feed-watcher hands off a material item.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fpolicy-diff\u002FSKILL.md",[],[86,105,126,127,93,128,129,80,130,81,131,132,133,134,91,135,29,136,137,97],"policy diff","which","you","analysis","text","change","paste","library","material","gap analysis","what the","name",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":39},"01M718S6521Y0FT4T24VCFKVG5","matter-workspace","Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fmatter-workspace\u002FSKILL.md",[],[145,146,127,147,148,149,89,91,93,128,150,151,152,153,154,155,156,157,158,159],"workspace","matter workspace","switch","manage","workspaces","keep","across","create","engagement","close","active","clients","list","it","context",{"skillNo":161,"name":112,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":39},"01M718S3FPEJNQGCMQ1AR8M4HE","Open gaps tracker — what's flagged and not yet closed. Use when the user asks \"what gaps are open\", \"gap tracker\", \"remediation status\", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgaps\u002FSKILL.md",[],[112,115,29,166,154,25,167,168,169,91,170,93,171],"risk","remediation","status","open","accept","user",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":183,"publishedAt":39},"01M718S06WSZ9Y24JKYM0VVPPE","gap-surfacer","Reference: shared gap- and comment-tracker framework backing \u002Fregulatory-legal:gaps and \u002Fregulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.","https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fclaude-for-legal\u002Fblob\u002Fmain\u002Fregulatory-legal\u002Fskills\u002Fgap-surfacer\u002FSKILL.md",[178],{"categoryNo":179,"categoryName":180,"taxonomyType":181,"taxonomyTypeDesc":182},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,184,185,186,86,105,187,169,188,189,32,190,112,191,192,193,194,25,167,195],"gap surfacer","shared","tracks","send","confirmation","aging","comments","with","work","slack","via","surfaces"]