travel-planner-pro

Provide a destination, dates, and traveler details, and the skill builds a verified day-by-day route, writes it as whitelisted Feishu XML, then creates the document with lark-cli docs +create. The final reply returns only the document title, URL, and pre-departure recheck items.

It covers city first visits, weekend short trips, food-themed routes, family and senior travel, self-driving road books, outbound independent travel, layover planning, destination comparison, and budget or points optimization. Each scenario routes to specific reference files and uses a tailored document structure.

Yes, it verifies visas, weather, opening hours, reservation windows, transport schedules, and dynamic prices before writing the guide. Facts are labeled as verified, reference, or estimated, and unverifiable items become explicit recheck actions instead of fabricated claims.

The skill falls back to a same-structure Markdown version with a recheck checklist and clearly states that no Feishu online document was created. The failure reason and the local XML file path are reported in the chat reply, never inside the document body.

This version does not search, generate, download, or insert images, and it forbids image-plan files and media-insert calls. Visual richness comes from callouts, grids, tables, checkboxes, bookmarks, and semantic colors instead of pictures.

Feasibility gates cap leisure days at two to three main points, fewer for families, seniors, or jet-lagged travelers, with one main geographic area per day. This keeps transport time, queues, meals, and rest realistic instead of producing unexecutable attraction lists.