Business travel itinerary
Turns business appointments, locations, travel preferences, and policy rules into a coordinated itinerary with timing, budget estimates, and preparation requirements. Use for multi-stop work trips and conference travel; keywords include travel plan, itinerary, business trip, travel policy, cost estimate, and logistics.
Veröffentlicht 21. Aug. 2026 · Aktualisiert 26. Aug. 2026
Voraussetzungen
Add the company travel policy and approval thresholds. Define buffer rules and accepted estimate sources.
Skill-Dokument
Das vollständige SKILL.md, das dein Agent liest und befolgt.
Business travel itinerary
Purpose
Organize a business trip into a practical sequence of appointments, travel segments, buffers, estimated costs, and preparation items using the supplied information.
Scope
Cover dates, locations, appointment windows, travel durations supplied in the corpus, accommodation constraints, policy checks, budget lines, and required documents.
Excluded: Booking travel, relying on unverified live availability, and making a personal or policy approval decision.
Data basis
- Appointment list, locations, traveler preferences, and trip purpose.
- Travel policy, budget, existing reservations, and supplied duration or cost data.
Result
Produce an itinerary document, a cost-estimate sheet by trip segment, and a preparation checklist with policy exceptions.
Quality criteria
- Appointments are ordered chronologically and geographically where locations are known.
- Every transition has a stated duration or an explicit missing-data flag.
- Buffers and conflicts are visible rather than silently compressed.
- Cost lines identify source, currency, and estimate status.
- Policy exceptions cite the relevant rule and trip line.
Instructions
Use supplied travel times and prices only; do not invent live options. Keep local time zones explicit when the trip crosses them. Mark assumptions separately from confirmed reservations. If the schedule cannot fit, show the conflict and the smallest set of alternatives without selecting one for the traveler.
Adapt before use
- Add the company travel policy and approval thresholds.
- Define preferred buffer rules and accepted estimate sources.
- Define required traveler documents and emergency fields.
- Define the default currency and how estimates from different currencies are shown.
- Define the required lead time for policy exceptions and preparation tasks.
- Define whether personal preferences may affect route comparisons and how they are recorded.
- Define the source hierarchy for reservations, appointment times, policy limits, and supplied estimates.
- Define the preferred presentation for local time and time-zone changes.
Verwandte Skills
- Company wiki page
Creates or refreshes a navigable company wiki page from authoritative policies, procedures, and operational references, with named owners, version dates, links, and explicit knowledge gaps. Use for internal documentation, SOP pages, knowledge-base maintenance, or policy publishing drafts.
- Document summary and action items
Turns business documents into a concise audience-specific summary, a cited action register, and a separate list of dates and commitments. Use for board papers, project material, policies, proposals, reports, meeting notes, and document review; keywords include summary, action items, deadlines, commitments, and key dates.
- Email intake triage
Classifies an email corpus by topic, urgency, ownership, response need, and due date, then drafts focused replies for the highest-priority messages. Use for shared inbox exports, executive inbox reviews, service requests, and administrative intake; keywords include email triage, inbox review, prioritization, delegation, and reply drafts.
- Handbook page draft
Drafts a publishable internal-handbook page from approved policy sources, turning rules into audience-specific guidance with definitions, procedures, decision tables, examples, exceptions, and ownership metadata. Use for employee handbooks, IT runbooks, security guidance, HR knowledge bases, and policy-to-practice documentation.