Turkey

Plan Turkey trips with city-coast-Cappadocia routing, verified entry rules, domestic transport strategy, and practical seasonal safety.

MIT-0 · Free to use, modify, and redistribute. No attribution required.
0 · 107 · 0 current installs · 0 all-time installs
byIván@ivangdavila
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (Turkey trip planning) align with the files and runtime instructions. The only required config path is ~/turkey/, which is appropriate for storing trip memory and is referenced throughout the guide.
Instruction Scope
SKILL.md and the companion markdown files document plan generation, local memory use, and how to initialize ~/turkey/. The instructions explicitly state the skill does not access files outside ~/turkey/ or make network requests. No steps ask the agent to read unrelated system files, to seek secrets, or to contact hidden external endpoints.
Install Mechanism
There is no install spec and no code to download or execute. This is instruction-only content (markdown files), so nothing is written to disk by an installer beyond the memory file the skill itself asks to create.
Credentials
The skill requests no environment variables, no credentials, and only a single config path (~/turkey/) for local memory. That is proportional to a trip-planning guide that stores user trip context.
Persistence & Privilege
The skill is not always-enabled and does not request elevated privileges. Its requested persistence is limited to its own memory folder under the user's home directory, which is consistent with its stated behavior.
Assessment
This skill is internally coherent for travel planning: it only stores trip context in ~/turkey/ and has no installs, network calls, or secret requirements. Before installing, confirm your agent platform enforces the stated runtime limits (some platforms may still allow network access or broader file permissions). Do not store sensitive credentials or private documents in ~/turkey/memory.md. If you plan to enable the skill to act autonomously, ensure that the agent's overall permissions (network access, file system scope) match your privacy expectations. If you want extra caution, inspect the created ~/turkey/ files after first use and avoid putting passports, unencrypted payment details, or other sensitive secrets into the skill's memory.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.0
Download zip
latestvk9705pdcx13yr978qfmhd4tz0d82qg7v

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🇹🇷 Clawdis
OSLinux · macOS · Windows
Config~/turkey/

SKILL.md

Setup

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

When to Use

User is planning a Turkey trip and needs practical guidance beyond generic highlights: visa pathway, route design, domestic transport choices, seasonal risks, regional tradeoffs, and on-the-ground execution.

Architecture

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

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

Quick Reference

TopicFile
Entry and Arrival
Visa, e-Visa, passport, booking namesentry-and-documents.md
Customs, airport arrival, first-hour logisticscustoms-and-arrival.md
Planning Backbone
Regional route selectionregions.md
Sample itinerariesitineraries.md
Where to stay by route styleaccommodation.md
Budget planningbudget-and-costs.md
Cards, cash, and tippingpayments-and-tipping.md
Transport
Flights, rail, buses, ferries, city transittransport-domestic.md
Driving and rental strategyroad-trips-and-driving.md
History and Place Logic
Museum and archaeology planningarchaeology-and-museums.md
Istanbul playbookistanbul.md
Cappadocia and Central Anatolia playbookcappadocia-and-central-anatolia.md
Aegean and west coast playbookaegean-and-west-coast.md
Mediterranean coast playbookmediterranean-coast.md
Black Sea and eastern Anatolia playbookblack-sea-and-eastern-anatolia.md
Southeast and Mesopotamia playbooksoutheast-and-mesopotamia.md
Lifestyle and Execution
Food by region and meal stylefood-guide.md
Nightlife by destination typenightlife.md
Traveling with childrenfamily-travel.md
Accessibility strategyaccessibility.md
Safety and Conditions
Emergencies, scams, heat, earthquake and fire logicsafety-and-emergencies.md
Climate and seasonality planningweather-and-seasonality.md
Tools
Connectivity and practical digital stacktelecoms-and-apps.md
Official source mapsources.md

Core Rules

1. Route by Cluster, Not by Country Count

Turkey rewards fewer bases with better logic. Keep one macro-cluster per week: Istanbul, Cappadocia plus Central Anatolia, one west-coast cluster, one Mediterranean cluster, or one southeast history cluster.

2. Confirm Entry Pathway Before Non-Refundables

Use entry-and-documents.md first. Some travelers are visa-free, some need e-Visa, and some need a consular visa. Do not assume one rule fits every passport.

3. Match Transport to Geography

Always offer at least two movement models:

  • Flight-heavy for west-east compression
  • Surface-heavy for one cluster where scenery and archaeology matter more than speed

4. Make Every Plan Season-Aware

Use weather-and-seasonality.md before promising balloons, beaches, long ruins days, mountain roads, or Black Sea viewpoints. Heat, wind, wildfire smoke, snow, and shoulder-season service changes reshape the trip.

5. Protect the High-Friction Bookings

Lock the fragile pieces first:

  • Balloon slots in Cappadocia
  • Cave hotel or small old-town rooms
  • Domestic flights on east-west moves
  • Museum and archaeology timing when doing dense historical days
  • Car rental for coast or inland routes

6. Budget With Real Turkey Math

Price the full route, not the hotel headline:

  • Airport transfers and intercity repositioning
  • Peak-season beach or resort premiums
  • Fuel, tolls, parking, and valet patterns in coastal routes
  • Museum/site passes and internal flight baggage fees

7. Build a Practical Operating Plan

Every output should include:

  • Base city logic
  • Day-by-day flow with transfer windows
  • Reservation deadlines
  • Weather or transport backup
  • Safety and local-context notes for the chosen region

Common Traps

  • Treating Istanbul, Cappadocia, Antalya, Ephesus, and Mardin as one short seamless loop.
  • Assuming all foreign travelers use the same visa pathway.
  • Booking the wrong Istanbul airport and discovering it too late.
  • Planning ruins, viewpoints, and beach time in July or August without heat logic.
  • Using a rental car by default inside dense urban cores where parking and traffic dominate.
  • Trying to "see the whole country" instead of choosing one west route or one east route.
  • Locking a balloon-dependent Cappadocia schedule without a wind-cancellation backup.

Security & Privacy

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

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

Related Skills

Install with clawhub install turkey if user confirms:

  • travel - General trip planning and itinerary structure
  • booking - Reservation workflow and confirmation hygiene
  • car-rental - Better rental strategy and handoff logistics
  • food - Deeper restaurant and cuisine planning
  • turkish - Language support for bookings, menus, and local interactions

Feedback

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

Files

27 total
Select a file
Select a file to preview.

Comments

Loading comments…