Propose hotel

Skill hec-ovi/agentickit/examples/travel/.pilot/skills/propose-hotel

AI copilot for React apps. Reads your state, fills forms, confirms actions, calls your tools. Multi-agent, AI SDK 6 + AG-UI, markdown skills. MIT.

Install

npx -y skills add hec-ovi/agentickit --skill propose-hotel

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Surface hotel 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 and Trip Detail pages.

SKILL.md

2.5 KB, as published. Nobody here has run it

Page scope

propose_hotel is registered ONLY on the Itinerary page (URL pattern /trips/<tripId>/itinerary). On every other page the tool is not in the registry and a call will silently fail.

Before calling, confirm you are on the Itinerary page. If you are NOT, do NOT call this tool. Reply: "Open the trip's Itinerary page first; I can propose hotels from there." Never invent fake results, never apologize for a tool error, never retry on a different tool name.

When to use

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

"find a hotel in Lisbon for the 12th to the 15th"
"where should I stay near the city center"
"I need a hotel under $150 a night"
"show me accommodation options"

Do NOT call for general hotel-industry questions or for opinions about specific brands. Answer in prose for those.

How to use

Resolve dates first. If the user gave relative dates ("next weekend", "Friday to Sunday"), call compute_relative_date to convert them to YYYY-MM-DD.
Call propose_hotel({ destination, checkIn, checkOut, maxPricePerNight? }). The tool mounts an inline picker in the chat with 2-4 options. The agent loop pauses until the user picks or skips.
After the user picks, acknowledge in one sentence and stop. The picker writes the choice into trip state.
If the user skips, offer one alternative ("want me to widen the price range?").

Output expectations

The tool resolves with the picked option (or { skipped: true }). The picker UI already displayed prices, ratings, and amenities, so a short acknowledgement is enough.

Anti-patterns

Do NOT call propose_hotel repeatedly without user input.
Do NOT prompt for clarification before calling — the picker IS the disambiguation.
Do NOT re-list the options in prose after the picker resolves.
Do NOT propose a flight here; if the user mentioned both, do hotels first then offer flights in the next turn.