Chile

Setup

If ~/chile/ doesn't exist or is empty, read setup.md and start naturally.

When to Use

User is planning a Chile trip and needs more than generic sightseeing advice: which macro-region to choose, how to route huge distances, what to reserve early, and how to handle entry, SAG declaration, weather, transport, and safety on the ground.

Architecture

Memory lives in ~/chile/. See memory-template.md for structure.

~/chile/
└── memory.md     # Trip context and evolving constraints

Quick Reference

Use this map to load only the Chile subtopic that changes the decision in front of you.

Core Rules

1. Route by Latitude, Not by FOMO

Chile is long, transfer-heavy, and season-sensitive. For short trips, lock one macro-region plus Santiago/central coast at most.

2. Solve Entry and SAG First

Before building routes, confirm the traveler's entry pathway in entry-and-documents.md and declaration obligations in customs-and-biosecurity.md. Chile is strict about undeclared animal and plant products.

3. Treat Atacama Altitude and Patagonia Weather as Trip-Shaping

Use atacama.md, patagonia-and-torres-del-paine.md, and weather-and-seasonality.md before promising ambitious days. Altitude, wind, rain, park closures, and ferry timing can break a pretty itinerary.

4. Always Offer Two Logistics Models

For each plan provide:

• A faster flight-heavy version
• A slower bus/road-heavy version

Explain the tradeoff in cost, scenery, fatigue, reservation pressure, and weather resilience.

5. Price the Full Chain, Not the Headline Fare

Budget using complete Chile trip math: domestic flights, Calama/Puerto Natales transfers, park tickets, refugios or tours, baggage, tolls, and card-vs-cash friction in smaller towns.

6. Flag Incompatible Combos Early

Call out mistakes before the user books:

• Atacama plus Torres del Paine in a short trip
• Carretera Austral in bad season without slack
• Rapa Nui planned without the extra entry requirements
• Dense city stays in Valparaiso hill areas without mobility review

7. Deliver Operational Plans

Output should include:

• Best base or base pair
• Day-by-day flow with transfer windows
• Reservation deadlines and risk points
• Weather and altitude notes
• Backup plan for delays, strikes, or closures

Common Traps

• Treating Chile like a compact destination instead of a north-south corridor.
• Trying to do Atacama, lakes, and Patagonia in one short trip.
• Ignoring Calama, Puerto Natales, and ferry transfer overhead.
• Arriving to San Pedro and doing the highest-altitude day immediately.
• Leaving Torres del Paine reservations until the last minute in high season.
• Assuming cards, signal, and transport frequency are equally easy everywhere.

Security & Privacy

Data that stays local: Trip preferences in ~/chile/

This skill does NOT: Access files outside ~/chile/ or make network requests.

Related Skills

Install with clawhub install \x3Cslug> if user confirms:

• travel — General trip planning and itinerary structure
• booking — Reservation workflows and confirmation hygiene
• car-rental — Better self-drive strategy and handoff logistics
• food — Deeper restaurant and cuisine planning
• spanish — Language support for bookings, menus, and practical interactions

Feedback

• If useful: clawhub star chile
• Stay updated: clawhub sync