← Back to Skills Marketplace
Voyage
by
Indigo Karasu
· GitHub ↗
· v2.3.0
· MIT-0
273
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install ocas-voyage
Description
Travel planning, itinerary construction, and reservation management. Use when the user wants to plan a trip, build an itinerary, find lodging or restaurants,...
Usage Guidance
What to consider before installing:
- Self-update and cron: The skill will register a daily cron job and can pull and extract code from the specified GitHub repo at runtime. That means the skill can change its code automatically — if you don't trust the repo or want silent updates, disable auto-update or remove the cron.
- Undeclared binaries/credentials: The SKILL.md uses CLI commands (gh, tar, python3, base64) and may require GitHub authentication (GH_TOKEN) but the skill metadata does not declare these requirements. Confirm these tools are present and understand what credentials (if any) will be used.
- Persistence and data written: The skill writes plans, decisions.jsonl, events, and journals to ~/openclaw/data/ocas-voyage and ~/openclaw/journals/ocas-voyage. Ensure you are comfortable storing potentially sensitive trip/reservation info there.
- Cross-skill access: The skill says it may cooperate with other skills (Taste, Sift, Weave). Ask or inspect how that cooperation is implemented and whether it reads other skills' private data or tokens.
- Review the source: Because the skill can self-update from the GitHub repo, review the repository (or pin to a commit/tag) and prefer explicit, auditable update behavior (manual approval or signed releases).
If you want to proceed: require explicit disclosure of required binaries and auth, disable or review the auto-update cron, and audit the repository that will be pulled by voyage.update.
Capability Analysis
Type: OpenClaw Skill
Name: ocas-voyage
Version: 2.3.0
The skill implements an automated self-update mechanism (`voyage.update`) and a daily cron job (`voyage:update`) that executes shell commands to fetch, extract, and overwrite its own files from a remote GitHub repository. While these capabilities are documented for version management, the use of 'gh api', 'tar', and 'cp' to modify the local skill directory introduces significant supply-chain risk and persistent execution without robust verification. These behaviors are defined in SKILL.md and README.md.
Capability Assessment
Purpose & Capability
The name/description (travel planning, itineraries, reservations) aligns with the instructions to build plans, persist state, and recommend lodging/food/activities. However, the SKILL.md includes a self-update mechanism that downloads and extracts a GitHub tarball and uses gh/api commands — those capabilities are beyond simple itinerary construction and should have been declared (required binaries/permissions).
Instruction Scope
Runtime instructions include creating and writing files under ~/openclaw/data and ~/openclaw/journals (expected), registering a cron job to run daily, and a self-update flow that fetches remote skill.json and a tarball from a GitHub repo, then extracts/installs it. The file lists also mention optional cooperation with other skills (Sift, Taste, Weave) which could imply reading external skill data, but the instructions do not clearly limit or justify cross-skill access.
Install Mechanism
There is no install spec (instruction-only), which is low friction. But the self-update flow downloads a GitHub tarball and extracts it locally — this writes code to disk and effectively installs updates from a remote repo at runtime. Using GitHub as the source is reasonable, but self-updating behavior increases risk and should be explicit in metadata.
Credentials
skill.json declares no required env vars or credentials, yet the SKILL.md self-update steps call out `gh api` and base64/python processing; those commonly require the GitHub CLI and possibly authentication (GH_TOKEN) which are not declared. Also, optional cooperation with Taste/Weave implies access to other skills' data/models but no additional filesystem or credential access is declared. The absence of declared required binaries (gh, tar, python3, base64) and any GH auth requirement is a mismatch.
Persistence & Privilege
The skill persistently writes state, journals, and decision logs under home directories (declared in skill.json), and it registers a daily cron job to run `voyage.update`. Persisted cron-based self-updates give the skill ongoing ability to change its code and behavior without interactive consent; that increases the long-term blast radius and should be considered before enabling.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ocas-voyage - After installation, invoke the skill by name or use
/ocas-voyage - Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.3.0
- Added self-update capability via the new voyage.update command and cron integration; Voyage now pulls and installs updates from its GitHub source automatically.
- Documented skill initialization logic and ensured automatic creation of data directories and files on first run.
- Expanded command set with voyage.update and improved documentation of run completion steps.
- Introduced background task scheduling for automatic daily updates.
- SKILL.md and usage documentation significantly revised for clarity, including trigger phrases and updated config versioning.
- README.md file added.
v2.0.0
- Added references/journal.md support file for journaling runs.
- Introduced new `voyage.journal` command for end-of-run journaling.
- Defined journaling storage path and Action Journal outputs.
- Expanded configuration (config.json) and storage layout details; now supports overwriting root via OCAS_ROOT.
- Specified skill responsibility boundaries and clarified optional cooperation with other skills.
- Added skill OKRs for feasibility, constraint compliance, and availability honesty.
v1.0.1
ocas-voyage 1.0.1 Changelog
- Clarified scope: Focuses on travel itinerary construction, lodging, dining, and activity recommendations strictly grounded in user constraints.
- Added detailed descriptions for when to use and not use the skill.
- Outlined all main commands and their intent.
- Introduced "core promise," highlighting transparent reasoning and explicit flagging of uncertainties.
- Listed strict invariants (dietary, budget, feasibility, and reservation-readiness).
- Described support files, storage layout, and comprehensive validation rules.
Metadata
Frequently Asked Questions
What is Voyage?
Travel planning, itinerary construction, and reservation management. Use when the user wants to plan a trip, build an itinerary, find lodging or restaurants,... It is an AI Agent Skill for Claude Code / OpenClaw, with 273 downloads so far.
How do I install Voyage?
Run "/install ocas-voyage" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Voyage free?
Yes, Voyage is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Voyage support?
Voyage is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Voyage?
It is built and maintained by Indigo Karasu (@indigokarasu); the current version is v2.3.0.
More Skills