Update to Mappu

{
  "description": "Hand a trip plan written with the traveler to Mappu as a draft only its link can open, which they keep by signing in, or point them to Mappu's own planner or importer. Never performs purchases or account changes.",
  "included_files": [],
  "name": "mappu-trip-handoff",
  "skill_md_contents": "---\nname: mappu-trip-handoff\ndescription: Hand a trip plan written with the traveler to Mappu as a draft only its link can open, which they keep by signing in, or point them to Mappu's own planner or importer. Never performs purchases or account changes.\n---\n\n# Hand a travel plan back to its traveler\n\nRead [authentication and permission boundaries](https://www.mappu.ai/auth.md).\nConfirm what the traveler wants: browse an example, keep a plan you wrote\ntogether, plan from scratch in Mappu, or import a plan they already have. Ask for\nmissing trip details only when they are necessary; never ask for credentials,\ncontact details or payment information.\n\nFor examples, cite the exact canonical itinerary page. A published example has\nnot been saved to their account.\n\nBefore planning, call `mappu_get_trip_planning_guide` on `https://api.mappu.ai/mcp`\nand follow it: it is how Mappu's own planner works and writes, in Mappu's warm\nlocal-guide voice. In short, plan around the traveler's own request and interests:\n\n- Give each day a theme and group its stops by area so the route does not double\n  back. Morning, afternoon and evening each include a real place.\n- Put stops in the order they happen, with real start times that leave time to\n  get from one to the next. Check opening days against each day's actual\n  weekday, holidays and the season; never schedule a known closure.\n- Name a restaurant or bar only when you are confident it exists and fits;\n  otherwise name the market, street or district.\n- Write like a guide: what each place is, why it suits this traveler, what to\n  look for, and one insider tip. Do not invent prices or schedules.\n- Mappu's published walks and audio guides are extras: add one as a stop where\n  it fits, never as the outline of a day.\n\nTo keep a plan you wrote together, call `mappu_save_trip_plan` on\n`https://api.mappu.ai/mcp` with the whole plan at the depth you gave in the\nconversation: a title and a short summary, the traveler's language, the\ndestinations, optional dates, and for each day a themed title, its stops in\norder (start time, description, tip, and the place as \"Place, City\" for the\nmap), the day's food and its practical tips. Mappu finds the places after the\ntraveler keeps the draft. Use one `idempotencyKey` per plan and reuse it only to\nretry the same plan.\n\nGive the returned `claimUrl` to the traveler and to nobody else; the draft is\nviewable only with the code in that link. Tell them what happens next: they open\nthe link, press Keep this plan and sign in or create a free Mappu account; the\nplan is added to My Trips and opens in Mappu. Mention that the draft expires after 7 days\nunless kept. Saving runs no model, books nothing, buys nothing and spends no\ncredits.\n\nIf the tool is unavailable or refuses the plan, say so. As alternatives, direct\nthe traveler to `https://www.mappu.ai/` to plan from scratch, or to\n`https://www.mappu.ai/tools/import-my-itinerary` to paste a plan they already\nhave. Do not encode private trip text into URL query parameters.\n\nLet the traveler complete sign-in, security challenges, privacy/legal choices,\ngeneration, editing and any purchase inside Mappu. Do not reuse the app's OAuth\nclient or browser tokens, and do not call account or credit APIs.\n\nReport only what actually happened. A link is a handoff, not a kept trip,\nconfirmed booking or purchase.\n"
}