Indonesia

Setup

If ~/indonesia/ does not exist or is empty, read setup.md and start naturally.

When to Use

User is planning an Indonesia trip and needs practical guidance beyond generic highlights: visa pathway, island choice, route design, surf and weather fit, transport tradeoffs, and on-the-ground execution across a large archipelago.

Architecture

Memory lives in ~/indonesia/. See setup.md for first activation flow and memory-template.md for the file structure.

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

Quick Reference

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

Core Rules

1. Route by Islands and Transfer Friction, Not by Postcard Count

Indonesia punishes over-routing. For most users, keep one main island cluster per week:

• Bali plus Nusa or Bali plus Lombok
• Java backbone with Yogyakarta and East Java
• Flores and Komodo
• Sumatra wildlife and volcanoes

2. Clear Entry Path First

Use entry-and-documents.md before recommending non-refundable flights. Visa-free, VOA, onward-proof expectations, passport validity, and Bali levy assumptions can change how safe the booking path is.

3. Match the Island to the User, Not the Hype

Always identify the user's real objective:

• First trip and easy logistics
• Surf and beach time
• Diving and boats
• Culture and temples
• Volcanoes and hiking
• Family pacing
• Low-friction luxury or remote nature

4. Make Every Plan Season-Aware

Use weather-and-seasonality.md before locking islands, boat days, dive trips, volcano starts, or beach-heavy routes. Indonesia weather is not one national answer, and sea conditions matter as much as rain.

5. Treat Boats, Scooters, and Mountain Sun as Real Risk

Do not romanticize fast boats, scooters, or volcano starts:

• Tight same-day boat plus flight chains are fragile
• Beginner scooter recommendations are often bad advice
• Heat, dehydration, altitude, rough roads, and poor clinic access change destination fit

6. Budget With Real Archipelago Math

Price the whole route, not the villa headline:

• Domestic flight baggage
• Boat tickets and harbor transfers
• Driver days and airport friction
• Tourist levy, visa fees, park fees, and guide costs
• Cash-only moments outside major hubs

7. Deliver Operational Plans

Every output should include:

• Base logic and what to skip
• Day-by-day flow with realistic transfer windows
• What must be booked early
• Weather or sea-condition fallback
• Safety, payment, and mobility notes for the chosen route

Common Traps

• Treating Indonesia as "Bali and maybe something else" instead of an archipelago with very different operating conditions.
• Trying Bali, Yogyakarta, Komodo, Gilis, and Sumatra in one short trip.
• Assuming cards, ATMs, data, sidewalks, and English work equally well everywhere.
• Booking fast boats and flights on the same day with no buffer.
• Sending families or older travelers to Nusa Penida, Bromo, or Komodo without discussing stairs, roads, ladders, heat, or medical backup.
• Giving one monsoon answer for the whole country.
• Recommending scooters by default to users who are tired, inexperienced, or traveling in rain season.

Security & Privacy

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

This skill does NOT: Access files outside ~/indonesia/ 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
• food — Deeper restaurant and cuisine planning
• esim — Better mobile-data setup before arrival
• indonesian — Language support for bookings, transport, and daily interactions

Feedback

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