Skip to main content
ClaudeWave
ES, Spanish
Skill1.5k estrellas del repoactualizado 5d ago

accessible-travel-planner

Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/accessible-travel-planner && cp -r /tmp/accessible-travel-planner/exports/openclaw/accessible-travel-planner ~/.claude/skills/accessible-travel-planner
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Accessible Travel Planner Skill

Travel with a disability fails on the gap between "accessible" as a label and
accessible as a reality: the "accessible" hotel room with a step to the bathroom, the
airline assistance that wasn't actually booked, the wheelchair that arrives damaged,
the medication held at a border. The disabled travelers who have good trips plan
differently — they verify access against their *specific* needs rather than trusting
the word, book assistance well ahead and get it in writing, and pre-plan for the
predictable failures. This skill runs that planning. It can't guarantee a provider's
access, so it verifies specifics with the source and builds the contingencies for when
things go wrong anyway.

## What This Skill Produces

- An **access-verified itinerary**: for each leg and stay, the specific questions to
  confirm against *your* needs (door widths, step-free routes, roll-in shower, bed
  height, hearing/vision provisions) — because "accessible" means different things
- An **assistance-booking checklist**: flight/rail/transfer assistance booked in
  advance with the deadlines, confirmations in writing, and what to reconfirm and when
- An **equipment & medication plan**: protecting mobility equipment in transit,
  battery/wheelchair airline rules, carrying medication across borders, and backups
- **Contingency scripts**: for the assistance that doesn't show, the damaged equipment,
  the room that isn't as described — what to say and to whom, in the moment

## Required Inputs

Ask for (if not already provided):
- The trip (where, when, how — flying/rail/road) and the specific access needs
  (mobility aid used, transfer ability, sensory needs, medical equipment, fatigue/
  pacing, service animal)
- The bookings made or being considered (airline, hotels, transfers) so they can be
  access-checked
- Equipment and medication involved, and any documentation the user has (medical
  letters, equipment specs)
- Risk tolerance and support: solo or with a companion, and how much buffer they want

## Framework

1. **Verify access against YOUR needs, not the label.** For each provider, generate the
   specific questions to ask directly ("is the route from lobby to room step-free?",
   "exact bathroom door width?", "is it a roll-in shower or a tub?", "bed height?") and
   get answers in writing. A photo request beats a promise. "Accessible" unconfirmed is
   a coin flip.
2. **Book assistance early and in writing.** Airline/rail special-assistance has advance
   deadlines (often 48h+); book it, get a reference, and reconfirm 24–48h before.
   Transfers and equipment (aisle chairs, hoists) are separate bookings. The written
   confirmation is what you hold up when it's not on the system.
3. **Protect equipment and medication.** Mobility equipment: airline battery/wheelchair
   rules, gate-checking, tagging, photographing its condition before handover, and a
   damage-claim plan. Medication: carry-on with documentation, quantity/import rules by
   destination (verify with the embassy/airline), a time-zone dosing plan, and backups
   for the essentials.
4. **Plan the fatigue and the pacing.** Access isn't only physical — build in the rest,
   the buffer between connections, the shorter days. An itinerary that would exhaust a
   non-disabled traveler is a guaranteed bad trip; pace it to the real energy budget
   (see [[spoon-planner]]).
5. **Pre-write the contingencies.** The predictable failures — assistance no-show,
   damaged equipment, a room that doesn't match — each get a script and an escalation:
   who to demand at the airport, the equipment-damage claim on the spot, the
   room-doesn't-work conversation and the backup. Knowing the move in advance turns a
   trip-ruining crisis into a handled hiccup.

## Output Format

```
## Access-verify these (get answers in writing/photos)
| Leg / stay | The specific questions for YOUR needs |

## Assistance bookings
| Service | Book by | Reference | Reconfirm at |

## Equipment & medication
[Mobility-aid transit protection + damage plan · airline battery/chair rules ·
medication documentation, import rules (verify), dosing across time zones, backups]

## Pacing
[Buffers, rest days, realistic daily load — to your energy budget]

## When it goes wrong (scripts)
[Assistance no-show · damaged equipment (claim on the spot) · room not as described]

⚠ Confirm every access and rule detail with the specific provider/airline/authority —
this plans and prompts, it can't certify a venue's access.
```

## Quality Checks

- [ ] Access is verified with specific questions against the user's needs, in writing —
      never trusting the "accessible" label
- [ ] Assistance bookings have advance deadlines, references, and a reconfirm step
- [ ] Equipment protection (with a damage plan) and medication/import rules are covered
- [ ] Pacing/fatigue is planned, not just physical access
- [ ] Contingency scripts exist for the predictable failures

## Anti-Patterns

- [ ] Do not trust "accessible" without verifying the specifics that matter to this
      traveler
- [ ] Do not assert airline/border/medication rules as fact — they vary and change;
      route to the provider/embassy to confirm
- [ ] Do not plan a punishing pace — access includes energy, not just ramps
- [ ] Do not skip the written confirmations — they're the leverage when assistance
      "isn't on the system"
- [ ] Do not omit the contingencies — the failures are predictable, so the responses
      should be pre-made

## Related

[[spoon-planner]] and [[flare-day-planner]] for the energy/health layer;
[[venue-access-check]] for checking a single place; [[relocation-planner]] for moving
rather than visiting; [[travel-itinerary|group-trip-negotiator]] for the group version.
360-feedback-templateSkill

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

401k-plan-decoderSkill

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

ab-test-plannerSkill

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

ab-test-readoutSkill

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

accessibility-auditSkill

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

accommodation-requestSkill

Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.

account-planSkill

Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.

account-recovery-planSkill

Get back into a locked or hacked account the right way — the official recovery routes, what proof you'll need, and how to re-secure it so it doesn't happen again. Use when asked I'm locked out of my account, my account got hacked, help me recover my [email/social/bank] account, or I lost access to 2FA. Produces the official recovery path for the account type, the identity proof to prepare, a re-securing checklist for after you're back in, and warnings about fake 'recovery' services and support scams.