| name | tripit |
| description | Operate and validate the TripIt CLI for trip and itinerary workflows. Use this skill when users ask to authenticate with TripIt, run `tripit` CLI commands, create/list/get/update/delete trips and child items (hotels, flights, transport, activities), or execute end-to-end validation flows based on README.md and AI_TEST_HARNESS.md. |
TripIt Skill
Overview
Use this skill to run reliable TripIt CLI workflows and validate behavior with repeatable command sequences.
Prioritize commands documented in README.md and test-flow coverage in AI_TEST_HARNESS.md.
Requirements
Install the CLI before any tripit command:
npm install -g tripit
This adds the tripit executable to the OS so tripit --help and other subcommands are available.
If running directly from this repository without global install, use:
fnox run -- bun index.ts --help
Workflow
- Confirm CLI availability:
tripit --help
- Authenticate:
tripit login
- Run the CRUD flow:
- Create trip
- List and get trip
- Create child resources (hotel, flight, transport, activity)
- Attach and remove documents on child resources
- Update trip and child resources
- Delete child resources, then delete trip
- Verify command coverage:
- Run
--help on root and key subcommands
- Compare supported commands to the harness checklist in
AI_TEST_HARNESS.md
- Call out missing tests and suggest additions
Command Examples
Use these common examples from README.md:
tripit trips create --name "Test Trip" --start 2026-03-20 --end 2026-03-23 --location "Tokyo" -o json
tripit trips list
tripit trips get <TRIP_UUID>
tripit trips update <TRIP_UUID> --name "Updated Test Trip"
tripit trips delete <TRIP_UUID>
Additional lifecycle examples:
tripit trips create --name "CLI Example Trip" --start 2026-05-10 --end 2026-05-14 --location "Lisbon" -o json
tripit hotels create --trip <TRIP_UUID> --name "Example Hotel" --checkin 2026-05-10 --checkout 2026-05-14 --checkin-time 15:00 --checkout-time 11:00 --timezone UTC --address "1 Example Ave" --city "Lisbon" --country PT -o json
tripit hotels delete <HOTEL_UUID>
tripit flights create --trip <TRIP_UUID> --name "Outbound Flight" --airline "Example Air" --from "San Francisco" --from-code US --to "Lisbon" --to-code PT --airline-code EA --flight-num 456 --depart-date 2026-05-10 --depart-time 08:30 --depart-tz UTC --arrive-date 2026-05-10 --arrive-time 17:00 --arrive-tz UTC -o json
tripit flights delete <FLIGHT_UUID>
tripit documents attach <HOTEL_UUID> --file ./confirmation.pdf --caption "Booking Confirmation"
tripit documents attach <ACTIVITY_UUID> --file ./ticket.png
tripit documents remove <HOTEL_UUID> --caption "Booking Confirmation"
tripit documents remove <HOTEL_UUID> --all
tripit activities create --trip <TRIP_UUID> --name "City Walk" --start-date 2026-05-11 --start-time 10:00 --end-date 2026-05-11 --end-time 12:00 --timezone UTC --address "100 Main St" --location-name "Old Town" -o json
tripit activities delete <ACTIVITY_UUID>
For harness-style examples that run against index.ts via fnox, read:
references/ai-test-harness-examples.md
Output Expectations
When executing a validation task, report:
- Commands run
- IDs created (
TRIP_UUID and child UUIDs)
- Verification result after each update/delete
- Gaps between implemented CLI commands and harness coverage
References
README.md
AI_TEST_HARNESS.md
references/ai-test-harness-examples.md