MCP HubMCP Hub
Volver a habilidades

plan-hiking-tour

pjt222
Actualizado Yesterday
2 vistas
17
2
17
Ver en GitHub
Diseñoaidesign

Acerca de

Esta habilidad ayuda a los desarrolladores a planificar rutas de senderismo seleccionando caminos según la dificultad (clasificaciones SAC/UIAA) y la condición física del grupo, mientras calcula los tiempos de viaje usando el método Munter y evalúa el desnivel y la seguridad. Soporta la planificación de excursiones de un día, travesías de varios días de refugio a refugio y rutas alpinas. Úsala para generar itinerarios realistas y gestionar la logística pernocta para grupos de trekking.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/plan-hiking-tour

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

Plan Hiking Tour

Plan hiking tour: trail pick, time est, elevation, safety for groups of varying fitness.

Use When

  • Day hike or multi-day trekking
  • Trail pick for group fitness + experience
  • Realistic time est for route
  • Route safe given conditions?
  • Hut-to-hut w/ overnight logistics

In

  • Required: Region/area
  • Required: Group profile (n people, fitness, experience)
  • Required: Time available (day duration or n days)
  • Optional: Difficulty pref (SAC T1-T6 or easy/mod/hard)
  • Optional: Elevation gain/loss tolerance (m)
  • Optional: Specific peaks, huts, destinations
  • Optional: Season + weather window

Do

Step 1: Define Requirements

Params constraining trail pick.

Group Fitness Classification:
┌──────────────┬──────────────────────────────────────────────────┐
│ Level        │ Capabilities                                     │
├──────────────┼──────────────────────────────────────────────────┤
│ Beginner     │ 3-4 hrs walking, <500 m elevation gain,          │
│              │ well-marked paths only (SAC T1-T2)               │
├──────────────┼──────────────────────────────────────────────────┤
│ Intermediate │ 5-7 hrs walking, 500-1000 m elevation gain,      │
│              │ mountain trails with some exposure (SAC T2-T3)   │
├──────────────┼──────────────────────────────────────────────────┤
│ Advanced     │ 7-10 hrs walking, 1000-1500 m elevation gain,    │
│              │ alpine trails, scrambling (SAC T3-T5)            │
├──────────────┼──────────────────────────────────────────────────┤
│ Expert       │ 10+ hrs, 1500+ m gain, via ferrata, glacier,     │
│              │ technical terrain (SAC T5-T6, UIAA I-III)        │
└──────────────┴──────────────────────────────────────────────────┘

SAC Hiking Scale Reference:
  T1 - Hiking:         Well-maintained paths, no exposure
  T2 - Mountain hiking: Marked trails, some steep sections
  T3 - Demanding:      Exposed sections, scree, basic scrambling
  T4 - Alpine hiking:  Simple scrambling, steep exposed terrain
  T5 - Demanding alpine: Challenging scrambling, glacier crossings
  T6 - Difficult alpine: Very exposed climbing, technical ice/rock

Document group's weakest-link fitness → max difficulty.

→ Requirements profile: group level, time budget, elevation tolerance, must-include/must-avoid.

If err: mixed fitness → plan for weakest, identify optional extensions for stronger (peak side trip while others rest at hut).

Step 2: Select Trail Candidates

Research + shortlist trails matching reqs.

Trail data sources:

  • Hiking guidebooks + regional sites
  • OpenStreetMap (sac_scale tag)
  • National/regional trail DBs (SchweizMobil, Alpenverein)
  • WebSearch "[region] hiking trails [difficulty]"

Per candidate, collect:

Trail Data Sheet:
┌─────────────────────┬──────────────────────────────────────┐
│ Field               │ Value                                │
├─────────────────────┼──────────────────────────────────────┤
│ Trail name/number   │                                      │
│ Start point         │ Name, elevation, access              │
│ End point           │ Name, elevation, access              │
│ Distance (km)       │                                      │
│ Elevation gain (m)  │                                      │
│ Elevation loss (m)  │                                      │
│ Highest point (m)   │                                      │
│ Difficulty (SAC)    │                                      │
│ Exposure            │ None / Moderate / Significant        │
│ Markings            │ Well-marked / Sparse / Unmarked      │
│ Huts/shelters       │ Names and locations along route      │
│ Water sources       │ Reliable / Seasonal / None           │
│ Season              │ Months when passable                 │
│ Escape routes       │ Points where you can exit early      │
└─────────────────────┴──────────────────────────────────────┘

Shortlist 2-3 fits + 1 easier backup.

→ Trail shortlist w/ complete data sheets, all in capability range.

If err: no trails match all → relax least important constraint first (typically distance before difficulty). Trail data incomplete → note gaps, verify on-site or contact local tourism.

Step 3: Calc Times via Munter Formula

SAC Munter → realistic time estimate.

Munter Formula:
  Time (hours) = (horizontal_km + vertical_km) / pace

  Where:
  - horizontal_km = trail distance in km
  - vertical_km   = elevation gain in meters / 100
                     (each 100 m up counts as 1 km)
  - pace           = km/h achieved on flat ground

Pace by Fitness Level:
┌──────────────┬────────────────┬──────────────────────────────┐
│ Level        │ Pace (km/h)    │ Notes                        │
├──────────────┼────────────────┼──────────────────────────────┤
│ Beginner     │ 3.5            │ Includes frequent stops      │
│ Intermediate │ 4.0            │ Steady pace, short breaks    │
│ Advanced     │ 4.5            │ Efficient pace, few breaks   │
│ Expert       │ 5.0            │ Fast and steady              │
│ With kids    │ 2.5-3.0        │ Very frequent stops          │
│ Heavy pack   │ Subtract 0.5   │ Multi-day with full pack     │
└──────────────┴────────────────┴──────────────────────────────┘

Descent Adjustment:
  - Gentle descent (<20% grade): adds minimal time
  - Steep descent (>20% grade): add elevation_loss_m / 200 hours
  - Very steep/technical: add elevation_loss_m / 150 hours

Example:

Trail: 12 km distance, 850 m elevation gain, 400 m steep descent
Group: Intermediate (pace = 4.0 km/h)

Ascent component:  (12 + 850/100) / 4.0 = (12 + 8.5) / 4.0 = 5.1 hours
Descent component: 400 / 200 = 2.0 hours additional for steep descent
Total estimate:    5.1 + 2.0 = 7.1 hours (round to 7-7.5 hours)

Add breaks: +30 min lunch, +15 min x 3 short breaks = +75 min
Total with breaks: approximately 8.5 hours trailhead to trailhead

→ Time estimates per candidate w/ break time. Be conservative (early > dark hike).

If err: calc'd times exceed daylight → too long. Shorten (closer end or skip section via transport) or split 2 days. Untested group → use beginner pace day 1, adjust by actual perf.

Step 4: Assess Safety

Objective + subjective hazards for selected route.

Safety Assessment Checklist:
┌──────────────────────┬────────────┬──────────────────────────────┐
│ Hazard               │ Rating     │ Mitigation                   │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Weather forecast     │ Good/Fair/ │ Check 3 sources; define      │
│                      │ Poor       │ turn-around weather triggers  │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Thunderstorm risk    │ Low/Med/   │ Plan to be below treeline    │
│                      │ High       │ by early afternoon           │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Snow/ice on trail    │ None/Some/ │ Check snow line; carry       │
│                      │ Extensive  │ microspikes if needed        │
├──────────────────────┼────────────┼──────────────────────────────┤
│ River crossings      │ Dry/Normal/│ Check recent rainfall;       │
│                      │ High water │ identify bridges or fords    │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Exposure/fall risk   │ None/Mod/  │ Assess group comfort level;  │
│                      │ Significant│ carry slings for short-roping│
├──────────────────────┼────────────┼──────────────────────────────┤
│ Trail condition      │ Good/Fair/ │ Check maintenance reports;   │
│                      │ Poor       │ plan for slower pace if poor │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Escape routes        │ Multiple/  │ Identify exit points and     │
│                      │ Few/None   │ nearest road access          │
├──────────────────────┼────────────┼──────────────────────────────┤
│ Cell coverage        │ Good/Spotty│ Download offline maps;       │
│                      │ /None      │ carry emergency beacon if    │
│                      │            │ remote                       │
└──────────────────────┴────────────┴──────────────────────────────┘

Overall Safety Rating:
  GREEN  - All factors favorable, proceed as planned
  YELLOW - One or more concerns, proceed with extra caution and backup plan
  RED    - Significant hazards present, postpone or choose alternative route

→ Completed safety assess: hazards rated, mitigations doc'd. Overall GREEN/YELLOW/RED → go/no-go.

If err: RED on primary → switch to backup from Step 2. All RED (severe weather) → postpone. Never override RED for schedule.

Step 5: Plan Logistics

Practical details for hiking day or multi-day.

Logistics Checklist:
┌──────────────────────┬──────────────────────────────────────────┐
│ Category             │ Details to confirm                       │
├──────────────────────┼──────────────────────────────────────────┤
│ Trailhead access     │ Driving directions, parking, bus/train   │
│ Hut reservations     │ Booking required? Half-board available?  │
│ Water resupply       │ Reliable sources along route             │
│ Food                 │ Packed lunch, hut meals, snacks          │
│ Gear                 │ See check-hiking-gear skill              │
│ Emergency contacts   │ Mountain rescue #, local emergency       │
│ Map and navigation   │ Paper map, offline GPS, waypoints loaded │
│ Group communication  │ Meeting points if group separates        │
│ Return transport     │ Last bus/train time from endpoint        │
│ Parking shuttle      │ If start != end, how to retrieve car     │
└──────────────────────┴──────────────────────────────────────────┘

Multi-day:

  1. Book huts well in advance (popular fill months ahead)
  2. Plan resupply for food + water
  3. Bail-out points per day (exit if injury or weather turns)
  4. Share itinerary w/ someone not on hike

→ All logistics confirmed or flagged. Hut bookings made. Transport arranged. Emergency plan doc'd.

If err: huts full → check nearby (bivouacs, camping, lower huts w/ longer approach). Trailhead access complicated (closed road) → arrange alt transport or adjust start.

Step 6: Generate Hiking Plan

Compile everything → complete plan doc.

Hiking Plan Document Structure:
1. Summary
   - Route name, dates, total distance/elevation
   - Group members and emergency contacts
   - Overall difficulty and safety rating

2. Day-by-Day Itinerary
   - Start/end points with times
   - Distance, elevation gain/loss, estimated time
   - Key waypoints and navigation notes
   - Water sources and meal plans
   - Escape route options

3. Safety Information
   - Weather forecast (to be updated day-of)
   - Known hazards and mitigations
   - Turn-around time and triggers
   - Emergency procedures and contacts

4. Logistics
   - Transport arrangements
   - Accommodation bookings
   - Gear checklist reference

5. Maps
   - Overview map with all days
   - Elevation profile for each day

→ Complete plan shareable w/ participants + emergency contact. Actionable w/o more research.

If err: plan has gaps that can't fill before departure → doc clearly, assign someone per item. Critical safety gaps (no escape route, no weather check plan) → resolve before departure.

Check

  • Trail difficulty matches group fitness + experience
  • Time estimates use Munter w/ appropriate pace
  • Safety assess complete, all hazards rated
  • Overall rating GREEN or YELLOW (not RED)
  • Hut bookings confirmed for multi-day
  • Water resupply per segment ID'd
  • Escape routes mapped per day
  • Emergency contacts + procedures doc'd
  • Itinerary shared w/ emergency contact not on hike
  • Gear checklist generated (via check-hiking-gear)

Traps

  • Plan for fastest: Plan for slowest. Group moves at weakest link's pace.
  • Ignore descent time: Steep descents slow + punishing on knees. Munter accounts but many underestimate.
  • No turnaround: Hard turnaround (typically early afternoon for alpine) → avoid darkness or afternoon storms.
  • Skip backup route: Weather + conditions change. Always have easier alt.
  • Overload day 1: Start shorter + easier → assess group pace, acclimatize, especially altitude.
  • Underestimate altitude: >2500 m → reduce pace 10-20% for unacclimatized. >3000 m → altitude sickness risk real.
  • Hut booking assume: Popular Alpine huts → reservations wks/mo ahead. Never assume walk-in in high season.

  • check-hiking-gear — gear checklist for planned hike
  • assess-trail-conditions — current conditions on selected trail
  • plan-tour-route — broader tour planning for non-hiking segments
  • create-spatial-visualization — viz route + elevation profile
  • generate-tour-report — compile plan into formatted report

Repositorio GitHub

pjt222/agent-almanac
Ruta: i18n/caveman-ultra/skills/plan-hiking-tour
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

Habilidades relacionadas

executing-plans

Diseño

Utilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.

Ver habilidad

requesting-code-review

Diseño

Esta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.

Ver habilidad

connect-mcp-server

Diseño

Esta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.

Ver habilidad

web-cli-teleport

Diseño

Esta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.

Ver habilidad