travel-requirement-intake

To turn a natural language travel request into structured itinerary requirements, submit your message to the Skill and it extracts predefined fields like destination_scope, total_days, start_date, budget_total, and transport_mode, outputting a structured JSON for macro planning.

Structured travel planning data extraction enforces a fixed key schema including destination_scope, total_days, start_city, start_date, budget_total, transport_mode, travel_style, pace, high_altitude_acceptance, and daily_driving_preference to ensure complete macro planning readiness.

Yes, you can use this for city walks and POI recommendations as well as full itineraries. The Skill applies to all nearby travel scenarios, extracting the same structured planning requirements from your natural language request.

If your travel planning request is missing required information like budget or pace, the Skill detects the incomplete fields and generates targeted follow-up questions to capture the missing details before finalizing the structured requirements JSON.

This Skill only parses requirements and does not generate a full travel itinerary. It transforms your natural language request into a SkillResult-compatible JSON containing structured fields, preparing the data for downstream macro planning workflows.

The best way to prepare travel data for downstream macro planning automation is to provide a detailed natural language travel request. The Skill extracts and validates all required fields, outputting a structured JSON ready for automated itinerary generation.