skill-hec-ovi-agentickit-propose-flight · by Install
$ agentstack add skill-hec-ovi-agentickit-propose-flight ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hec-ovi-agentickit-propose-flight) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Page scope
propose_flight is registered ONLY on the Itinerary page (URL pattern /trips//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_flighttwice 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hec-ovi
- Source: hec-ovi/agentickit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.