chile_skill
- Python
2.5k
GitHub Stars
27
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill chile- _meta.json267 B
- accessibility.md987 B
- atacama.md1.3 KB
- budget-and-payments.md1.6 KB
- carretera-austral-and-aysen.md1005 B
- customs-and-biosecurity.md1.8 KB
- entry-and-documents.md2.2 KB
- family-travel.md966 B
- food-and-wine.md1.2 KB
- itineraries.md1.5 KB
- lake-district-and-chiloe.md1.2 KB
- memory-template.md1.5 KB
- national-parks.md1.9 KB
- nightlife.md971 B
- patagonia-and-torres-del-paine.md1.4 KB
- rapa-nui.md1.1 KB
- regions.md1.8 KB
- road-trips-and-driving.md1.8 KB
- safety-and-emergencies.md1.4 KB
- santiago.md1.3 KB
- setup.md2.2 KB
- SKILL.md5.4 KB
- sources.md3.3 KB
- telecoms-and-apps.md1.5 KB
- transport-domestic.md1.9 KB
- valparaiso-and-vina.md1.1 KB
- weather-and-seasonality.md1.6 KB
Overview
This skill plans Chile trips with macro-region triage, verified entry rules, long-distance logistics, and practical safety measures for cities, desert, lakes, and Patagonia. It focuses on operational plans: base choices, day-by-day flows, transfer windows, reservation deadlines, and concrete backups for weather, strikes, or closures. Designed to turn vague travel goals into executable itineraries with realistic timing and costs.
How this skill works
It inspects the traveler’s priorities, trip length, season, and mobility constraints to recommend one or two viable macro-regions and base pairs. It verifies entry pathway and biosecurity obligations, then builds both a flight-heavy and a road-heavy logistics model, pricing the full travel chain. Finally, it flags incompatible combos, lists reservation risk points, and supplies safety and contingency notes tailored to each region.
When to use it
- You need to choose which Chile macro-region(s) fit your trip length and season
- You want realistic routing for long transfers (Calama, Puerto Natales, ferry timetables)
- You must confirm entry rules, SAG/biosecurity obligations, or special Rapa Nui requirements
- You need reservation timing, park permits, or refugio/tour planning
- You want two logistics models (fast vs scenic) and clear tradeoffs
Best practices
- Lock the macro-region by latitude early; don’t try Atacama + Patagonia on short trips
- Solve entry pathway and SAG/ customs declarations before booking flights
- Always produce a flight-first and a bus/drive-first plan with explicit tradeoffs
- Budget the full chain: domestic transfers, park fees, baggage and last-mile taxis
- Flag season and weather risks (Atacama altitude, Patagonian wind, ferry schedules) and provide backups
Example use cases
- 7-day Santiago + Atacama trip with altitude acclimatization plan and contingency day
- 14-day northern + lake-district loop with road vs flight logistics and reservation deadlines
- 10–12-day Torres del Paine focused trip with park permits, transfer windows, and refugio backup options
- Carretera Austral road-trip plan with ferry timings, bad-season slack, and resupply points
- Rapa Nui visit plan including entry validations, timing, and permit checklist
FAQ
Yes, but it will flag likely incompatibilities and recommend realistic splits or an added travel day; it prioritizes latitude-based routing to avoid overambitious plans.
Will it make bookings or access my files?
No. It does not make network requests or access files outside the local trip memory. It outputs operational recommendations you can use to book manually.
How does it treat weather and cancellations?
It builds weather- and season-aware plans, highlights high-risk days, and includes explicit contingency windows for delays, strikes, or closures.
