How do I install the Propose Flight skill?

Run npx skillmds@latest add hec-ovi/propose-flight in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Propose Flight safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Propose Flight?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Propose Flight free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Propose Flight?

hec-ovi (@hec-ovi) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Propose Flight by hec-ovi — Agent Skill

Name: Propose Flight
Author: hec-ovi

Propose Flight

Surface flight options as a picker the user chooses from. Mounts an inline UI in the chat (renderAndWait) and pauses until the user picks one or skips. Used during the Itinerary page; a flights specialist agent also exists at /agents.

hec-ovi 936e0c4 2.5 KB Updated Sep 17, 2026

File contents

Page scope

propose_flight is registered ONLY on the Itinerary page (URL pattern /trips/<tripId>/itinerary). The tool is mounted by the React component on that page; on every other page (Trips, Trip Detail, Packing, Booking, Preferences, Agents, Threads, Lab) it is NOT in the registry and a call will silently fail.

Before calling, read the registered context. If active_trip state is present and you can see the user is on the Itinerary page, proceed. If not, do NOT call. Instead reply: "Open the trip's Itinerary page first; I can propose flights from there." This redirection is the correct behavior; never invent fake results, never apologize for a tool error, never retry on a different name.

When to use

Call propose_flight when the user wants flight options AND you are on the Itinerary page. Typical phrasings:

"find me a flight from JFK to Lisbon on the 12th"
"what flights are there from LAX next Friday"
"show me morning flights"
"I need a return on Sunday"

Do NOT call when the user is asking ABOUT flights as a topic (prices in general, airline opinions). Answer in prose for those.

How to use

Resolve the dates first. If the user said "the 12th" or "next Friday", call compute_relative_date to get a YYYY-MM-DD value. Never invent.
Call propose_flight({ origin, destination, date, returnDate? }). The tool mounts an inline picker in the chat with 2-4 options. The agent loop pauses until the user picks one or skips.
After the user picks, narrate the choice in one sentence and stop. The picker writes the chosen flight into trip state automatically.
If the user skips, acknowledge and offer one alternative ("want me to widen the date range?").

Output expectations

The tool resolves with the picked option (or { skipped: true }). You do NOT need to emit prices, times, or details — the picker UI already showed them and the user just made a choice. One sentence acknowledging is enough.

Anti-patterns

Do NOT call propose_flight twice in a row without user input between.
Do NOT prompt the user to "describe the kind of flight you want" before calling — the picker IS the disambiguation.
Do NOT narrate every option in prose after the picker resolves; the user already saw them.

---name: propose-flightdescription: Surface flight options as a picker the user chooses from. Mounts an inline UI in the chat (renderAndWait) and pauses until the user picks one or skips. Used during the Itinerary page; a flights specialist agent also exists at /agents.---# Page scope`propose_flight` is registered ONLY on the **Itinerary page** (URL pattern `/trips/<tripId>/itinerary`). The tool is mounted by the React component on that page; on every other page (Trips, Trip Detail, Packing, Booking, Preferences, Agents, Threads, Lab) it is NOT in the registry and a call will silently fail.Before calling, read the registered context. If `active_trip` state is present and you can see the user is on the Itinerary page, proceed. If not, do NOT call. Instead reply: "Open the trip's Itinerary page first; I can propose flights from there." This redirection is the correct behavior; never invent fake results, never apologize for a tool error, never retry on a different name.# When to useCall `propose_flight` when the user wants flight options AND you are on the Itinerary page. Typical phrasings:- "find me a flight from JFK to Lisbon on the 12th"- "what flights are there from LAX next Friday"- "show me morning flights"- "I need a return on Sunday"Do NOT call when the user is asking ABOUT flights as a topic (prices ingeneral, airline opinions). Answer in prose for those.# How to use1. Resolve the dates first. If the user said "the 12th" or "next Friday", call `compute_relative_date` to get a `YYYY-MM-DD` value. Never invent.2. Call `propose_flight({ origin, destination, date, returnDate? })`. The tool mounts an inline picker in the chat with 2-4 options. The agent loop pauses until the user picks one or skips.3. After the user picks, narrate the choice in one sentence and stop. The picker writes the chosen flight into trip state automatically.4. If the user skips, acknowledge and offer one alternative ("want me to widen the date range?").# Output expectationsThe tool resolves with the picked option (or `{ skipped: true }`). You doNOT need to emit prices, times, or details — the picker UI already showedthem and the user just made a choice. One sentence acknowledging is enough.# Anti-patterns- Do NOT call `propose_flight` twice in a row without user input between.- Do NOT prompt the user to "describe the kind of flight you want" before calling — the picker IS the disambiguation.- Do NOT narrate every option in prose after the picker resolves; the user already saw them.

Frequently asked questions