Travel Planning
v1.0.1Plan trips with itineraries, multi-city routing, budget optimization, family logistics, packing lists, and visa timelines.
⭐ 0· 1.4k·10 current·11 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the actual behavior: an instruction-only travel planner that reads and writes markdown files in a local ~/travel-planning/ folder, offers itinerary/budget/packing templates, and requires no external credentials or binaries.
Instruction Scope
Instructions explicitly direct the agent to read and write files under ~/travel-planning/ (memory.md, trips/, bookings.md, etc.) and to ask for user consent before storing document metadata. That file I/O is coherent for this purpose. One ambiguity: setup.md asks to “Save their answer to their MAIN memory” which could mean a platform-wide/shared memory location (not just the skill's ~/travel-planning/ folder). It’s unclear whether the skill will modify agent-global memory or only its own folder—this is an implementation/platform detail you may want to confirm.
Install Mechanism
No install spec and no code files — instruction-only — so nothing is downloaded or installed. The only persistence is the markdown files the skill will create under ~/travel-planning/ when used.
Credentials
The skill requests no environment variables, no credentials, and does not reference external endpoints. It does propose storing limited document metadata (passport expiry, policy numbers) only with explicit user consent; that is proportionate for a travel planner. It does not request full document images or secret tokens.
Persistence & Privilege
always:false (normal). The skill intends to persist user data in ~/travel-planning/ and to record an activation preference in 'MAIN memory' (ambiguous). Persisting data in a skill-specific folder is expected; persisting into a platform-global memory would be broader — confirm whether write access is limited to the skill's own files.
Assessment
This skill appears internally consistent: it is instruction-only, needs no external credentials, and stores trip data as local markdown files in ~/travel-planning/. Before installing or enabling it: 1) Confirm with the platform whether "MAIN memory" means a global agent memory (if you want to avoid cross-skill/global storage). 2) Be mindful what you share — the skill states it will only store passport expiry and reference numbers with consent and will not store full images; do not upload full document images. 3) Inspect and back up ~/travel-planning/ if you enable the skill; you can delete or move those files at any time. 4) If you prefer, disable autonomous invocation or limit its activation triggers so it only runs when you explicitly ask. 5) Because the source is 'unknown', if you need stronger assurance ask the publisher for more provenance (who maintains it, where source is hosted). Overall the behaviour matches the travel-planning purpose, but confirm the platform-level memory behavior if you want to avoid any global writes.Like a lobster shell, security has layers — review code before you run it.
latestvk972whd1p069te71s7pmqt5bgx81qx0w
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
✈️ Clawdis
OSLinux · macOS · Windows