plan-eu-relocation
关于
This skill creates structured, dependency-aware timelines for relocations to or within the EU/DACH region. It maps bureaucratic steps, tracks deadlines, and handles country-specific procedures. Use it for coordinating complex moves, especially when integrating with employer HR or managing tight deadlines.
快速安装
Claude Code
推荐npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/plan-eu-relocation在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
Plan EU Relocation
Structured, dependency-aware relocation plan for EU/DACH moves → bureaucratic steps, deadlines, country-specific reqs.
Use When
- Move EU/DACH → EU/DACH
- Non-EU → EU/DACH
- Need step dependencies before start
- Coord employment relocation w/ employer HR
- Tight deadlines (job start, lease, school)
- Want single end-to-end doc
In
Required
- Origin country: Current residence
- Destination: Target (Germany, Austria, Switzerland primary; other EU OK)
- Nationality: Citizenship(s), EU/non-EU
- Employment type: Employed (local), posted, self-employed, freelance, unemployed, student, retired
- Move date: Approx physical move
- Household: Single, couple, family w/ kids (ages), pets
Optional
- Job start date: First day in destination
- Housing: Secured, searching, employer-provided
- Insurance: Health, liability, household
- Language: Destination level (A1-C2 or none)
- Special: Disability, pregnancy, military, legal matters, custody
- Prior EU regs: Previous Anmeldung or equivalent
Do
Step 1: Assess Situation
Gather personal, professional, legal context → which bureaucratic tracks apply.
- EU vs non-EU status, all members
- Visa or residence permit needed? (non-EU, non-EEA family)
- Employment type → work permit separate from residence permit?
- Bilateral agreements (social security, tax treaties, qualification recognition)
- Move type: permanent, temp (under/over 183 days), cross-border commute
- Fixed dates: job start, lease start, school year, notice periods
→ Profile doc: nationality, employment, move type, fixed dates.
If err: nationality or employment ambiguous (dual w/ one non-EU, contractor vs employee unclear) → escalate to legal advisor or destination embassy. No guessing visa reqs.
Step 2: Map Dependency Chain
Bureaucratic steps + prereqs → correct execution order.
- Destination registrations:
- Residence reg (Anmeldung / Meldezettel / Anmeldung bei der Gemeinde)
- Tax reg or number assignment
- Health insurance enroll
- Social security reg
- Bank account
- Vehicle re-reg (if applicable)
- School/childcare enroll (if applicable)
- Pet import (if applicable)
- Origin deregistration:
- Residence dereg (Abmeldung or equivalent)
- Tax office notif
- Insurance cancel/transfer
- Utility cancel
- Mail forward
- Map deps as DAG:
- Residence reg → needs signed lease
- Tax number → needs residence reg
- Bank account → may need residence reg + tax number
- Health insurance → may need employment contract or residence reg
- Social security coord → depends on employment type
- Find parallel tracks → simultaneous steps
- Mark in-person vs online/mail steps
→ Dependency graph (textual or visual): all steps, prereqs, parallels.
If err: deps unclear for country → search official sources (Germany: bmi.bund.de, Austria: oesterreich.gv.at, Switzerland: ch.ch). Never assume cross-country transfer.
Step 3: Create Timeline w/ Deadlines
Dependency graph → calendar timeline aligned w/ move date.
- Backwards from move date + fixed deadlines (job, school)
- Per step, estimate:
- Lead time (earliest start)
- Processing time (authority duration)
- Buffer time (slack for delays)
- Calendar windows:
- Pre-move (from origin): visa, insurance research, doc prep
- Move-week: Anmeldung, bank, SIM
- Post-move (within legal deadlines): tax reg, vehicle re-reg, origin dereg
- Statutory deadlines + penalties:
- Germany: Anmeldung within 14 days
- Austria: Meldezettel within 3 days
- Switzerland: Anmeldung within 14 days (canton varies)
- Tax reg deadlines vary
- Appointment lead times (some Buergeramt → 2-6 weeks advance)
→ Week-by-week timeline 8-12 wks pre-move to 4-8 wks post, each step in its window.
If err: appointment availability unpredictable (big German cities) → 2-week buffer, alt offices or early-morning walk-ins.
Step 4: Identify Country-Specific Procedures
Tailor generic plan to destination's reqs + conventions.
- Germany:
- Buergeramt Anmeldung (needs Wohnungsgeberbestaetigung from landlord)
- Finanzamt tax ID (Steueridentifikationsnummer by mail in 2-4 wks)
- Gesetzliche or private Krankenversicherung enroll
- Rentenversicherung coord
- Rundfunkbeitrag (GEZ) reg
- Elterngeld/Kindergeld if applicable
- Austria:
- Meldezettel at Meldeamt (within 3 days)
- Finanzamt → Steuernummer
- e-card health insurance (employer or self-reg w/ OeGK)
- Sozialversicherung coord
- Switzerland:
- Einwohnerkontrolle reg (within 14 days, canton-dependent)
- AHV/IV/EO social insurance reg
- Mandatory health insurance (Grundversicherung) within 3 mo
- Quellensteuer or regular tax (permit-dependent)
- Residence permit (B or L) via employer or canton
- Cross-ref each procedure w/ docs needed (see check-relocation-documents)
→ Country-specific list: exact office names, forms, processing times.
If err: smaller municipality → procedures may differ from national standard. Check Gemeinde/Kommune website or call Buergerservice direct.
Step 5: Flag High-Risk Items
Steps where missed deadlines → fines, legal consequences, cascading delays.
- Mark all w/ statutory deadlines (Anmeldung, tax reg, insurance enroll)
- Penalty per missed deadline:
- Late Anmeldung Germany: fine up to 1,000 EUR
- Late Meldezettel Austria: fine up to 726 EUR
- Late health insurance Switzerland: retroactive premiums + surcharge
- Bottleneck steps blocking downstream:
- No Anmeldung = no tax ID = no payroll = no bank account (sometimes)
- Flag items needing originals hard to replace (birth, marriage, degree)
- Seasonal risks: end-of-year → office closures; September → school enrollment pressure
- Origin deadlines (dereg, tax year coord, insurance notice periods)
→ Risk register: each item, deadline, penalty, mitigation.
If err: penalty/deadlines unconfirmable from official sources → mark "unconfirmed", recommend direct inquiry. No invented penalties.
Step 6: Generate Relocation Plan Doc
Compile findings → single actionable plan.
- Sections:
- Exec summary (move type, dates, household)
- Dependency graph (visual or textual)
- Timeline (week-by-week checklist)
- Country-specific procedures (destination)
- Dereg procedures (origin)
- Risk register (high-pri highlighted)
- Doc checklist (cross-ref check-relocation-documents)
- Contact list (offices, phones, appointment URLs)
- Per checklist item:
- Status (not started / in progress / done / blocked)
- Deadline
- Deps
- Notes/tips
- "First 48 hours" quick-ref card → most time-critical post-arrival
- "What-if" section: common disruptions (apt falls through, job date changes, mail delays)
→ Complete plan doc ready to execute, all items traceable to graph + risk register.
If err: too complex for single doc (multi-country w/ separate visa tracks per dependent) → master timeline + per-person sub-plans.
Check
- Every step in graph has source (official site, embassy, legal ref)
- All statutory deadlines noted w/ legal basis
- Timeline accounts for weekends, holidays, closures
- No step before its deps
- Risk register covers min: Anmeldung, tax reg, health insurance, social security
- Doc checklist cross-refs check-relocation-documents
- Fixed dates (job, lease) in timeline w/o conflicts
Traps
- Assume all EU same procedures: Deadlines, docs, office structures vary even within DACH
- Underestimate appointment leads: Berlin/Hamburg/Munich Buergeramt → 4-6 wks booking; plan or use walk-ins
- Forget origin country: Dereg, tax notifs, insurance cancel periods at origin = as important as destination
- Ignore 183-day tax rule: >183 days in country/yr → full tax residency. Coord move date.
- No originals: DACH offices need originals (not copies), some need certified translations. Digital often not accepted.
- Treat Switzerland like EU: Not in EU. Different rules for residence permits, health, social — even for EU nationals.
- Health insurance gap: Between origin cancel + destination enroll → uncovered period. Travel/international insurance to bridge.
- Overlook pet rules: Pet passports, rabies titers, breed-specific import → adds weeks.
→
- check-relocation-documents — verify doc completeness per step
- navigate-dach-bureaucracy — detailed DACH gov procedures
GitHub 仓库
相关推荐技能
railway-docs
文档Railway Docs Skill可实时获取最新的Railway官方文档,确保回答的准确性。当开发者询问Railway功能特性、工作原理或分享docs.railway.com链接时,应优先使用此技能。它通过专门的LLM优化文档源提供最新信息,避免依赖过时记忆来回答技术问题。
n8n-code-python
文档该Skill为在n8n平台的Python代码节点中编写代码提供专家指导,特别适用于需要使用_input/_json/_node语法、Python标准库或了解n8n中Python限制的场景。它强调JavaScript应作为首选方案,仅当需要特定Python功能或对Python语法更熟悉时才使用Python。Skill提供了快速入门模板和关键注意事项,帮助开发者在n8n中高效编写Python代码。
archon
文档Archon Skill为开发者提供了基于RAG的语义搜索和项目任务管理功能,可通过REST API访问知识库。它支持文档搜索、网站爬取、文件上传和版本控制,适用于技术文档查询和项目管理场景。首次使用时需要配置Archon主机地址,建议在处理外部文档时优先使用该Skill。
n8n-code-javascript
文档这个Skill为n8n工作流中的JavaScript代码节点提供专业指导,涵盖数据处理、HTTP请求和日期操作等核心场景。它详细解释了如何正确使用n8n特有的`$input`/`$json`语法、`$helpers`工具以及DateTime对象,并包含关键的错误排查和模式选择建议。开发者通过该Skill能快速掌握Code节点的正确返回格式、数据访问方法和常见陷阱解决方案。
