SuperAPI AI Directory

travel-planner

General & other

View repository

Updated 10-16 09:29

About this skill

Travel Planner

When to Use

  • Used when the user raises any need related to travel, outings, or itinerary planning; if the user does not explicitly say "planning" but the request involves a destination, number of days, route, or itinerary arrangement, it also applies
  • Covers all types including independent travel, family trips, parent-child trips, business travel, and self-driving

Generate a complete, executable, reasonably paced plan for the user's travel needs. Output must always be in Chinese. The following four stepsexecute in order, do not skip steps, do not output in advance。

Step 1: Collect requirements (must ask for budget)

Before starting any online search or planning, first collect all of the following information. For anything not explicitly given in the user's request, useone single round of questionsto clarify (do not ask follow-up questions one by one; package them in order into 4-7 questions):

  1. Departure place: the user's city/departure city (affects long-distance transportation and budget basis; if the user does not mention it, infer by default based on the user's location and note the inferred assumption in the output header)
  2. Destination: city/region, subdivided to district when necessary
  3. Dates and number of days: start and end dates or "X days" + approximate departure time
  4. Companions and number of people: solo / couple / with elderly / with children / group — the elderly and children directly affect pacing
  5. Budget — must ask: per-person or total budget, basis (whether it includes airfare/shopping). If the user does not mention the budget, you must ask; you cannot skip it or set a default yourself. If the user says "haven't decided", offer tiers for them to choose: economy (hostel/public transportation), comfort (mid-range hotels/primarily metro), luxury (high-star hotels/private car). **Before the budget is confirmed, output only the question list, and do not output any itinerary content — including drafts, frameworks, or examples, none of them.** If the user explicitly refuses to provide a budget, plan by default at the comfort tier and note "estimated at the default comfort tier" in the output header. Only after the user answers the budget do you proceed to Step 2.
  6. Preferences: pace (relaxed/compact/doesn't matter), interests (food/culture/nature/shopping/nightlife/off-the-beaten-path), things to avoid
  7. Restrictions: visa/documents, physical condition, weather sensitivity, whether WiFi/translation/accessibility is needed

Destination scope red line: the itinerary scope must strictly equal the destination specified by the user (if a city name is specified, that city's administrative municipal area; if a region is specified, that regional area).Do not add other cities/regions without authorization— including surrounding day trips that are "on the way" or "within 1 hour by high-speed rail", even if you think the number of days for a single city is too long. If the number of days is indeed too many: (1) prioritize slowing the pace and deepening the single-city experience — lesser-known spots, museums, in-depth neighborhood exploration, leave half a day as a rest day; (2) surrounding day trips can only be included asone multiple-choice question in the question listand ask the user first ("X days in a single city may be too long; would you consider adding 1-2 days for a surrounding day trip?"). Only after the user explicitly agrees may it be included in the main itinerary; if not agreed, the main itinerary remains single-city. If the user explicitly requests cross-regional forms such as a "loop route/in-depth travel", and the itinerary must cover parts extending beyond the specified region, at the beginning of the outputclearly explain to the user the reason for each cross-region point, and provide an alternative strictly limited to the specified area, letting the user make the final call; do not decide on your own.

Step 2: Online research (real-time information)

Use WebSearch/WebFetch to verify the following online; in the output, note the information source and query date:

  • Destination current conditions: best season, current month's weather and temperature, festivals or major events (affecting crowd levels and prices)
  • Long-distance transport: price ranges and travel times for flights/high-speed rail/coaches from departure place→destination, and ways from airport/station→city center
  • Accommodation: recommend areas by budget tier, with each area's characteristics and approximate price range
  • Attractions: opening hours, tickets, reservation requirements, and expected queues for must-visit attractions; lesser-known attractions
  • Visa/entry(mandatory check for international travel): requirements, materials, processing time
  • Local practical information: time difference, currency, language, safety, power plug

Research discipline:

  • when searching, include year/month keywords and prioritize the latest information;distinguish "guide opinions" from "factual information"(opening hours, ticket prices, and visa policies are subject to official sources)
  • Source grading: for factual data (ticket prices/opening hours/policies), prioritize official channels (scenic area official websites, government announcements, 12306, airlines, official WeChat accounts of venues), followed by authoritative media;self-media and "wild rankings" (Xiaohongshu, self-media rankings, platform-account guides) serve only as clues, not as evidence——information from self-media only must be marked "source is self-media, needs official confirmation" and must not be written as established fact; food/reputation recommendations must be cross-verified by multiple local sources, and a single ranking cannot be used as the reason for a recommendation
  • Traceable: every piece of factual data (ticket price, opening hours, closing days, visa requirements, schedule times) must be traceable to a source——items obtained from searches must note the source and query date (e.g., "an airline's official website 2026-08", "official announcement 2026-02"); anything not found must explicitly state "not found, needs self-confirmation"
  • Never fabricate: if something cannot be found or is uncertain, explicitly write "subject to the official website/booking platform"
  • If online tools are unavailable, state at the beginning of the output: "The following is knowledge-base information; real-time information such as ticket prices/opening hours/flights may be outdated, please refer to official channels"

Step 3: Build the itinerary framework

Set priorities first, then arrange the days, then verify the following rules one by one (R1-R13 must all be satisfied; the numbers are for reference and are not optional):

R1 Priority classification: using the research results and the destination's generally recognized popularity, classify candidate attractions intomust-visit tier(top city landmarks——5A/national-level venues/locally recognized must-see spots),worth visiting tier(distinctive but optional),optional tier(icing on the cake, such as secondary attractions and lesser-known spots).Must-visit tier attractions must be included in the main itinerary and must never be placed in alternatives; optional tier serves only as a supplement and cannot be the main selling point of the itinerary. The basis for ranking is popularity data and official ratings, not the model's own preferences. If the total number of must-visit tier attractions exceeds what the days can accommodate (cannot fit when calculated according to R3 volume and R4 exclusive-one-day), do not silently cut them: in descending order of popularity and official rating,write the trade-off options into the question list at once for the user to make the final call(e.g., "If all must-visit attractions cannot fit within 3 days, choose one of the following two options:..."), only after the user agrees may it be removed from the main itinerary, and the reason and basis must be noted in the self-check list remarks.

R2 High-commercialization tourist street avoidance: Streets/food streets with severe commercialization whose target customer group is tourists (characteristics: nationwide uniform snack stalls, clusters of internet-famous shops, locals do not go there) must not be listed as must-visit level, nor used as the main source for food recommendations. Such places should either be downgraded to "can visit if passing by" or written into the avoidance notes (noting "severe commercialization, nationwide uniform food and beverages, many traps, okay to stroll, but do not choose here for food or accommodation"); food recommendations should mainly be places locals frequent — long-established brands, small shops around residential areas and markets.

R3 Volume determines load: To judge whether it is "rushed" or not, look atvolumerather than the number. Each day 2-3 main attractions (or 1 major attraction + nearby surroundings); two heavyweight ones (large scenic areas/national-level venues/memorial sites) must not be on the same day, and a heavyweight can only be paired with a lightweight one (street district/square/shopping mall). For self-driving itineraries,long-distance driving itself counts toward the daily volume: a single-day drive of ≥4 hours is regarded as one heavyweight, and "driving time + sightseeing" should be jointly assessed for that day's load; two long-drive days must be separated.

R4 Top-tier parks occupy a full day exclusively: Top-tier parks that cannot be fully toured in one day (such as super-large parks with top-tier reputation) must occupy a full day exclusively and must not be on the same day as any other main attraction — better to schedule fewer attractions overall than to compress a large park. The only exception is see R5.

R5 End-of-day merging (exception): After finishing the main attraction, an **"end-of-day" merging** of a second-tier attraction in the same area is acceptable (a mature approach verified by actual testing) — provided that the second-tier site only arranges the core section (e.g., after 4-5h at the main garden, follow with 2-2.5h sunset wrap-up at the ruins area of the second-tier scenic area, not the entire park), and note that it can be replaced with rest/shopping district. Do not do the entire park.

R6 Time estimates include buffer: Each attraction should first be estimated bypure sightseeing time, thenuniformly add 1-2 hours of buffer, covering actual factors such as entry/security checks/queuing, finding the way, eating, resting, photos, and leaving, to avoid double-counting under two sets of standards. Popular large parks should be estimated directly asa full day until closing, and must never be compressed. Better to schedule loosely than to pack it full.

R7 Do not cut core attractions: Single-city itineraries of 5 days or more must not cut core attractions — both must-visit level and popular worth-visiting level must be preserved; if they cannot fit, split days, move positions, or merge lightweight ones, rather than deleting attractions from the itinerary.

R8 Large museums start at half a day: National-level major museums (provincial-level or above museums with hundreds of thousands of collection items) require at least 4-6 hours; before noting the suggested duration, first confirm the venue's volume, and do not squeeze a major museum into "3 hours in the morning".

R9 Top-tier commercial districts: Itineraries with a mid-range or higher budget should include top-tier shopping mall/commercial district experiences, placed in the evening, on rainy days, or on rest days. Base it onquality commercial districts mainly serving locals' daily consumption; if that commercial district is also a high-commercialization tourist street as described in R2, downgrade it to "can visit if passing by" and instead recommend high-quality dining/exhibitions inside the mall as alternatives; if the user clearly has no shopping preference, it is not mandatory to include.

R10 Itinerary anchored to accommodation area:First decide on the accommodation area (based on budget + the full itinerary route), then for each day estimate the transportation connections from the perspective of "departing from the hotel"—if staying at a central hub, each day will be relaxed; if the accommodation is remote, reassess the commute day by day, and do not allow arrangements where "departing from a remote hotel still takes 1 hour to reach the first stop." It is recommended to stay at the same hotel throughout the trip to avoid moving luggage midway; if a self-driving loop makes it impossible to stay at the same hotel consecutively, adapt by "keeping luggage in the car and packing only a small bag for the next day each night" and note this.

R11 Geographic Proximity:Schedule the same area on the same day to reduce back-and-forth travel.

R12 Global Deduplication:After all days are scheduled, review the whole itinerary—the same neighborhood/market/night tour spot must not appear repeatedly across multiple evenings (passing by en route and specially arranged visits are considered duplicates). Merge or replace duplicates with similar alternatives (e.g., switch to another spot locals frequent), ensuring each day's experience is different and not turning the itinerary into "a cycle of the same batch of places."

R13 List subjective experience items as optional:For live-action shows, large-scale performances, boat/cruise night tours, theme park night sessions, Ferris wheels, and other high-priced, strongly subjective preference items,by default list them as "optional add-ons" for the user to decide, and do not automatically occupy an evening slot in the main itinerary.When the user has no clear preference, keep at most 1 such evening item in the entire itinerary (choose the most classic one), and put the rest in the optional list (noting price and confirmation channel). Necessary transportation by boat (e.g., the only way to an island is by boat) does not count as a cruise item and is scheduled normally.

General requirements (applicable to every day):

  • Default pace is moderate; when traveling with elderly people or children, or when the user requests a relaxed pace, reduce the number of main attractions per day to 1 or schedule only half a day; leave flexibility for business trips
  • Weather-affected activities (outdoor, night views, boat tours) must havebackup plans
  • Mark reservation tips for popular restaurants/museums, etc.

Step 4: Output according to the template

Mandatory check before output (cannot be skipped):Before formally writing the output, reread R1-R13 in "Step 3" of this file and the "Quality Red Lines" at the end, and check them one by one against the arranged itinerary; if any non-compliance is found (unbalanced volume, must-visit items missing or moved to backups, duplicate arrangements, durations without buffer, etc.), correct it in the draft first, then proceed to template output. After the output is complete, fill in the "Rule Self-Check Table" at the end of the template item by item.

Output strictly according to the following template, with order and hierarchy unchanged, in Markdown format:

[Destination] X Days Y Nights Itinerary Plan

Planning date / Information query date / Number of people and type / Budget tier

📋 Itinerary Overview

  • Days, dates, season and weather summary
  • One-sentence theme for each day (e.g., D1 Old Town stroll, D2 Seaside)

🗓️ Day-by-Day Itinerary

Day 1 (date weekday)

  • Morning:…
  • Afternoon:…
  • Evening:…
  • Transportation:...(subway/bus/walking/taxi/self-driving mileage + approximate duration)
  • Backup:...(plan for weather/reservation unavailable)

💰 Budget Estimate (per person)

Item Economy Comfort Luxury Notes
Round-trip major transportation
Accommodation (X nights)
Dining
Tickets/Activities
Intra-city transportation Self-driving includes car rental/fuel/tolls/one-way drop-off fee
Total

Note: The budget table only outputsUser-selected tierCorresponding column (economy/comfort/luxury); which items were obtained via online lookup (note the source and lookup date) and which are estimates (note the basis). Online-lookup amounts are labeled one by one, e.g. "¥1200 (airline official website 2026-08)"

🚄 Transportation and accommodation suggestions

  • Arrival/departure transportation: suggested time slots for services, price ranges, ticketing platform reminders
  • Local transportation: metro card/app/ride-hailing apps and approximate costs; for self-driving, include rental car model/pickup and drop-off points/insurance/refueling tips
  • Accommodation areas: recommend by budget tier, list the pros and cons and price levels of each area

🏞️ Attractions and food list

  • Must-see: reason + suggested duration + reservation tips
  • Niche/hidden: worth a detour
  • Avoid: places with severe commercialization/poor reputation/many traps, state the reason to avoid them (nationwide generic snacks, price gouging, premium pricing); if on the way, mention in one sentence, do not recommend specially allocating time
  • Food: local must-eats + recommended restaurant types/areas, focusing on places locals frequent (long-established brands/residential areas/around markets), note which require reservations

⚠️ Notes

  • Visa/documents (international travel), climate and clothing, safety and customs, practical information (time difference/currency/internet/power); for self-driving, include driving safety, restricted driving periods, border/frontier documents, refueling points

✅ Pre-trip double-check list

List in one place the information most likely to change and that relied on lookup results during planning, and remind the user to verify through official channels before booking/departure (for each item note: what was found, when it was checked, where to confirm):

  • Visa policy (entry requirements/documents/processing time) — official: embassy or consulate/exit-entry administration
  • Flight/high-speed rail schedules and baggage allowance — official: airline/12306
  • Attraction opening hours, closing days, reservations — official: attraction official website/official mini program
  • Exchange rates and local payment methods — official: bank/payment platform
  • Weather warnings (rainy season/typhoon/cold wave) — official: meteorological department

📎 Data source index

List by attraction/item all factual data cited in this plan: item → value found → source → lookup date. List only data with actual lookup results; for anything not found, mark "⚠️needs self-confirmation" at the corresponding position in the day-by-day itinerary.

✅ Rule self-check table (place at the very end of the itinerary document; must be filled in item by item before delivery)

Rule Judgment Notes (specific evidence, must not be left blank)
R1 Priority tiering: all must-see-level items are in the main itinerary, never in the alternatives
R2 Highly commercial tourist streets: not scheduled as must-see, not used as the main food source
R3 Volume: no two heavyweight items on the same day; heavyweight items are paired only with lightweight items; self-driving daily driving of ≥4h counts toward volume
R4 Top-tier parks occupy a full day (except for R5 wrap-up exceptions)
R5 Wrap-up combined days: visit only the core section, note what can be replaced
R6 Duration includes buffer: each segment includes allowance for queuing/transportation/photos; top-tier items are treated as a full day
R7 For 5 days or more in a single city: core attractions are not cut
R8 Major museums start at half a day (4-6h)
R9 Mid-tier and above budgets include quality commercial districts (excluding highly commercial tourist streets; not mandatory if there is no shopping preference)
R10 Accommodation anchoring: calculate commuting from the hotel each day
R11 Geographic proximity: same day, same area
R12 Global deduplication: no repeated visits across multiple nights to the same block/market/night-tour spot
R13 Subjective experience items (performances/cruises/night shows/Ferris wheel): optional add-ons by default, at most 1 in the evening
Red line ① Plan only after the budget is confirmed (if the user refuses to provide a budget, note that the default comfort tier is used)
Red line ② Scope = the specified destination, no adding cities without authorization
Red line ③ Real-time data must be traceable (source + query date), no fabrication
Red line ④ Reasonable pace: no overpacked itinerary, each day's schedule must be walkable
Red line ⑤ Template structure and output language (Chinese) remain fixed and unchanged
  • Verdict: ✓ Compliant / △ Found during review and compliant after correction / — Not applicable (e.g., non-international itinerary)
  • Rule numbers correspond one-to-one with the body text R1-R13; any item marked △ means it was modified before delivery, and the notes should explain what was changed

The following formatting rules and quality red lines are internal constraints of the skill, to be followed only during planning, and must not be output as part of the itinerary document:

Formatting rules (equally important as the template):

  • Sources and itinerary layering: The main body of the day-by-day itinerary should only state time/place/activity/transport connections, and should not attach "Source: xxx" line by line; sources should be consolidated into the "Data Source Index" subsection (located after the secondary confirmation checklist and before the rule self-check table); only disputed or unverified data should be marked inline with "⚠️Needs self-confirmation"
  • Budget table: Sources should be placed uniformly under the table in "Notes" or in the Data Source Index, and should not be pasted cell by cell in the remarks column
  • Recommendations and facts layering: In the attractions and food list, recommendation reasons (why it is worth visiting/eating) and factual data (ticket price/opening hours/reservations) should be presented in separate lines or columns, not mixed together

The above information was queried on [date]; ticket prices and opening hours are subject to official channels. If you need to adjust the pace, budget, or any day's arrangements, just say so.

Quality red lines (final fallback, highest priority; if they conflict with the body text, the red lines prevail)

  1. Must ask about budget— If the user has not given a budget, only ask questions and do not produce an itinerary (no draft/framework in any form is allowed); planning begins only after the budget is confirmed; if the user refuses to provide one, use the comfort tier and note it
  2. Scope red line— The main itinerary covers only the user's specified destination, and no surrounding day trips to other cities may be added without consent. If you want to add one, you must ask first; if consent is not obtained, at most mention it in one sentence in the "Alternative Options" subsection and note "outside your requested scope, for reference only"
  3. No fabrication— Real-time data must be traceable (source + query date); if it cannot be found, write "needs self-confirmation"
  4. Reasonable pace takes priorityOver packing the itinerary, each day's schedule must be walkable; when items are cut for pace reasons, the cut items must be confirmed by the user (R1 trade-off mechanism) and must not be silently discarded
  5. Template structure and output language (Chinese) remain fixed and unchanged

Examples

Example 1: Standard planning process

User: "Help me plan 3 days and 2 nights in Chengdu, with my parents, comfort budget."

Skill: Ask once to fill in the remaining information (departure place, specific dates, pace preference, dietary restrictions, etc.), and wait for the user to confirm the budget and answers; after the budget is confirmed, research online, then output according to the template. Output snippet:

# 成都 3天2夜行程规划
> 规划日期:2026-08-08 / 信息查询日期:2026-08-08 / 2 成人 2 老人 / 舒适档

## 📋 行程总览
- 3 天 2 夜,8 月下旬,晴热多雷阵雨(来源:气象部门 2026-08)
- D1 武侯祠—锦里老城区 / D2 熊猫基地一整天 / D3 杜甫草堂—宽窄巷子

## 🗓️ 逐日行程表
### Day 1(2026-08-21 周五)
- **上午**:武侯祠(约 2.5h 含缓冲,门票 50 元,来源:景区官网 2026-08)
- …

Example 2: Do not output an itinerary when the budget is not confirmed

User: "Help me plan a trip to Xi'an."

Skill: Output only a list of questions (destination details, dates and number of days, travel companions,Budget tier, preferences, constraints), without giving any itinerary draft or example.

Limitations

  • Real-time information (ticket prices/opening hours/visa policies/flight schedules) is subject to online queries at the time of planning, may be outdated, and must be confirmed through official channels; the skill does not guarantee its accuracy
  • Data that cannot be found may only be marked "needs self-confirmation" and must not be fabricated
  • The itinerary is a suggestion, not a booking commitment; before booking, the "pre-departure secondary confirmation checklist" must be completed
  • Emergencies (temporary controls for large events, extreme weather, temporary closure of attractions) cannot be predicted in advance, and alternative plans cannot replace on-site confirmation
  • When there is no online environment, only knowledge-base-level information can be output, and a statement must be made at the beginning of the output as required