{"id":"accessible-travel-planner","name":"accessible-travel-planner","summary":"障害やアクセスのニーズに実際に対応できる旅行を計画しましょう。実際のアクセシビリティ(単なる「アクセシブル」ラベルではなく)を確認し、支援を事前に予約し、装備や薬の計画を立て、アクセスがうまくいかない場合の対策も備えましょう。","body":"# Accessible Travel Planner Skill\n\nTravel with a disability fails on the gap between \"accessible\" as a label and\naccessible as a reality: the \"accessible\" hotel room with a step to the bathroom, the\nairline assistance that wasn't actually booked, the wheelchair that arrives damaged,\nthe medication held at a border. The disabled travelers who have good trips plan\ndifferently — they verify access against their *specific* needs rather than trusting\nthe word, book assistance well ahead and get it in writing, and pre-plan for the\npredictable failures. This skill runs that planning. It can't guarantee a provider's\naccess, so it verifies specifics with the source and builds the contingencies for when\nthings go wrong anyway.\n\n## What This Skill Produces\n\n- An **access-verified itinerary**: for each leg and stay, the specific questions to\n  confirm against *your* needs (door widths, step-free routes, roll-in shower, bed\n  height, hearing/vision provisions) — because \"accessible\" means different things\n- An **assistance-booking checklist**: flight/rail/transfer assistance booked in\n  advance with the deadlines, confirmations in writing, and what to reconfirm and when\n- An **equipment & medication plan**: protecting mobility equipment in transit,\n  battery/wheelchair airline rules, carrying medication across borders, and backups\n- **Contingency scripts**: for the assistance that doesn't show, the damaged equipment,\n  the room that isn't as described — what to say and to whom, in the moment\n\n## Required Inputs\n\nAsk for (if not already provided):\n- The trip (where, when, how — flying/rail/road) and the specific access needs\n  (mobility aid used, transfer ability, sensory needs, medical equipment, fatigue/\n  pacing, service animal)\n- The bookings made or being considered (airline, hotels, transfers) so they can be\n  access-checked\n- Equipment and medication involved, and any documentation the user has (medical\n  letters, equipment specs)\n- Risk tolerance and support: solo or with a companion, and how much buffer they want\n\n## Framework\n\n1. **Verify access against YOUR needs, not the label.** For each provider, generate the\n   specific questions to ask directly (\"is the route from lobby to room step-free?\",\n   \"exact bathroom door width?\", \"is it a roll-in shower or a tub?\", \"bed height?\") and\n   get answers in writing. A photo request beats a promise. \"Accessible\" unconfirmed is\n   a coin flip.\n2. **Book assistance early and in writing.** Airline/rail special-assistance has advance\n   deadlines (often 48h+); book it, get a reference, and reconfirm 24–48h before.\n   Transfers and equipment (aisle chairs, hoists) are separate bookings. The written\n   confirmation is what you hold up when it's not on the system.\n3. **Protect equipment and medication.** Mobility equipment: airline battery/wheelchair\n   rules, gate-checking, tagging, photographing its condition before handover, and a\n   damage-claim plan. Medication: carry-on with documentation, quantity/import rules by\n   destination (verify with the embassy/airline), a time-zone dosing plan, and backups\n   for the essentials.\n4. **Plan the fatigue and the pacing.** Access isn't only physical — build in the rest,\n   the buffer between connections, the shorter days. An itinerary that would exhaust a\n   non-disabled traveler is a guaranteed bad trip; pace it to the real energy budget\n   (see [[spoon-planner]]).\n5. **Pre-write the contingencies.** The predictable failures — assistance no-show,\n   damaged equipment, a room that doesn't match — each get a script and an escalation:\n   who to demand at the airport, the equipment-damage claim on the spot, the\n   room-doesn't-work conversation and the backup. Knowing the move in advance turns a\n   trip-ruining crisis into a handled hiccup.\n\n## Output Format\n\n```\n## Access-verify these (get answers in writing/photos)\n| Leg / stay | The specific questions for YOUR needs |\n\n## Assistance bookings\n| Service | Book by | Reference | Reconfirm at |\n\n## Equipment & medication\n[Mobility-aid transit protection + damage plan · airline battery/chair rules ·\nmedication documentation, import rules (verify), dosing across time zones, backups]\n\n## Pacing\n[Buffers, rest days, realistic daily load — to your energy budget]\n\n## When it goes wrong (scripts)\n[Assistance no-show · damaged equipment (claim on the spot) · room not as described]\n\n⚠ Confirm every access and rule detail with the specific provider/airline/authority —\nthis plans and prompts, it can't certify a venue's access.\n```\n\n## Quality Checks\n\n- [ ] Access is verified with specific questions against the user's needs, in writing —\n      never trusting the \"accessible\" label\n- [ ] Assistance bookings have advance deadlines, references, and a reconfirm step\n- [ ] Equipment protection (with a damage plan) and medication/import rules are covered\n- [ ] Pacing/fatigue is planned, not just physical access\n- [ ] Contingency scripts exist for the predictable failures\n\n## Anti-Patterns\n\n- [ ] Do not trust \"accessible\" without verifying the specifics that matter to this\n      traveler\n- [ ] Do not assert airline/border/medication rules as fact — they vary and change;\n      route to the provider/embassy to confirm\n- [ ] Do not plan a punishing pace — access includes energy, not just ramps\n- [ ] Do not skip the written confirmations — they're the leverage when assistance\n      \"isn't on the system\"\n- [ ] Do not omit the contingencies — the failures are predictable, so the responses\n      should be pre-made\n\n## Related\n\n[[spoon-planner]] and [[flare-day-planner]] for the energy/health layer;\n[[venue-access-check]] for checking a single place; [[relocation-planner]] for moving\nrather than visiting; [[travel-itinerary|group-trip-negotiator]] for the group version.","author":"@mohitagw15856","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/accessible-travel-planner","license":"MIT","category":"writing","lang":"en","tokens":1304,"stars":0,"calls30d":2,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}