skill-hec-ovi-agentickit-add-day-item · by Install
$ agentstack add skill-hec-ovi-agentickit-add-day-item ✓ 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-add-day-item) 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
add_day_item is registered ONLY on the Itinerary page (URL pattern /trips//itinerary). On every other page the tool is not in the registry and a call will silently fail.
If the user asks to add an itinerary item from a different page, reply: "Open the trip's Itinerary page; I can add items there." Do not retry under another name; do not invent a confirmation.
When to use
Call add_day_item when the user wants to add something to a specific day of the trip's itinerary AND you are on the Itinerary page. Typical phrasings:
- "add Eiffel Tower to day 2"
- "schedule lunch at Cantina at 1pm on Friday"
- "put the museum visit on day 3"
- "add a note: bring an umbrella"
Do NOT call for trip-level edits (title, dates, total budget) — those go through update_ actions auto-registered by usePilotState.
How to use
- Identify the day. The user may say "day 2" or a date like "Friday".
If a date, convert with compute_relative_date to a YYYY-MM-DD value, then look up which day index that matches in the trip state.
- Call
add_day_item({ dayIndex, kind, title, time?, location?, notes? }).
kind is one of: activity, meal, transit, note.
- The framework will pop a confirm modal (mutating). The user approves
or cancels. Wait for the result.
- After the user decides, acknowledge in one sentence:
- approved → "Added Eiffel Tower to day 2."
- cancelled → "Cancelled — nothing added."
Anti-patterns
- Do NOT add items in bulk without confirming each one. If the user says
"add 5 things", do them one at a time.
- Do NOT guess the
kind. If unclear, default toactivity. - Do NOT skip the date resolution step; "Friday" without conversion is a
hallucination risk.
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.