Skills

JourniOne Travel Planning Skill: From Idea to Day-by-Day Routes and a Shareable Travel Journal

Best for gradually refining a travel idea into a day-by-day itinerary and generating a shareable, map-equipped Travel Journal; before using it, confirm your client supports remote MCP and can install the two dependencies, TourMind hotel Skill and Kiwi MCP.

Official source · JourniOne · Travel Journal Creator (JourniOne-Planning-Skills)

Install

https://github.com/JourniOne-ai/JourniOne-Planning-Skills/blob/main/INSTALL.md

Who It's For

  • For anyone who wants to quickly turn a travel idea into a day-by-day itinerary, and ultimately get a visual, shareable Travel Journal complete with maps. It connects hotel and flight search on demand — hotels and flights are only queried when the user asks.
  • The officially described workflow: just describe your travel needs in natural language, no need to type the Skill name; you first explore and refine your ideas and daily plan, and the visual guide is only generated after you confirm.
  • Prerequisites and limitations: the bundled scripts require Node.js 22 or higher; the client needs to support web search, file access, HTTPS requests, and remote MCP. It depends on TourMind hotel Skill and Kiwi MCP; the installation agent checks and prepares these dependencies (reusing existing capabilities where possible), and initialization is only considered complete when the client can discover both dependencies.
  • When it's not a good fit: the official materials don't state anything about offline availability or applicability to specific industries/text types, so this cannot be confirmed; if your environment can't meet the client capabilities or dependencies above, the official documentation offers no alternatives.

Your First Try in 3 Minutes

The officially recommended main path is importing the repository through your client's Skill manager; you can also use a release package per the official installation guide (INSTALL.md). No copy-paste terminal install command is provided officially, so this guide keeps the link path to the official installation guide.

  1. Prerequisites: confirm your client supports web search, file access, HTTPS requests, and remote MCP, and that Node.js 22+ is installed. If TourMind hotel Skill or Kiwi MCP is missing, the installation agent automatically checks and prepares it, prompting you only when permissions, manual steps, or a reload are needed.
  2. Installation location: import the repository in your client's Skill manager, or use the release package as described in INSTALL.md.
  3. Trigger a low-risk task: describe a simple travel need to the agent in natural language, e.g. "Help me plan a three-day Kyoto itinerary" — no need to type the Skill name.
  4. Success signal: the agent starts exploring ideas and a daily plan with you, and offers an adjustable day-by-day route. No visual guide is generated at this stage, and hotels/flights are not searched by default.
  5. Side-effect confirmation point: only when you explicitly confirm you want a visual guide will it connect to journione.ai to generate a Travel Journal; hotel and flight searches likewise happen only when requested. Aside from these officially documented network queries, whether the installation and runtime involve any other file reads/writes, command execution, or network activity is not covered by the official evidence.

Note: creating a JourniOne guide itself does not require a JourniOne token or a local JourniOne MCP service.

Use Cases

Case 1: From idea to day-by-day route (recommended first try)

Scenario: you're planning a vacation but have nothing concrete yet. Tell the agent, "I'd like to take my family to Dali for four days, at a relaxed pace." The agent explores ideas and proposes a daily plan; you can keep the conversation going to adjust the pace and add or remove places. Expected result: a day-by-day route draft you can revise repeatedly; hotels and flights are not queried automatically. The evidence ends here — the official materials don't show a finer output format.

Case 2: Generate a shareable visual Travel Journal

Scenario: your route is set and you want something ready to share. Explicitly confirm in the conversation that you want a visual guide. The agent connects to journione.ai (default, no token or local JourniOne MCP needed) and produces a Travel Journal guide with maps. Expected result: a shareable visual guide. This step involves explicit outbound network access and is an action requiring your confirmation; generation time and the guide's content details are not documented officially.

Usage Boundaries

  • Network access: connects to journione.ai by default; hotel and flight searches go through TourMind hotel Skill and Kiwi MCP, and only happen when the user asks. Beyond this, the official documentation doesn't define any other network boundaries.
  • Side effects and confirmation points: generating a visual guide requires user confirmation before it runs; if dependencies are missing, the installation agent prompts for permissions or manual steps. Whether it reads/writes files locally is not covered by the official evidence — the existing documentation only mentions that the client needs file access capability, which can't be used to infer that it definitely will or won't modify your files.
  • Runtime environment and client prerequisites: Node.js 22+; the client must support web search, file access, HTTPS requests, and remote MCP. The official materials don't list a set of verified specific clients.
  • Officially stated limitations: initialization is only complete when the client can discover both dependencies — TourMind hotel Skill and Kiwi MCP.
  • Not yet confirmed: the range of supported text/conversation languages, offline usage, and platform-specific differences in manual release-package installation — in all cases, defer to the actual content of INSTALL.md. Anything not covered by this guide's evidence is not speculated about.