assess-trail-conditions
关于
This skill assesses trail safety by analyzing weather, terrain, and maintenance data to generate a GREEN/YELLOW/RED rating with go/no-go recommendations. It's designed for use during hike planning, after weather changes, or before committing to exposed routes. Developers can integrate it for safety decision-making using tools like WebFetch and WebSearch.
快速安装
Claude Code
推荐npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/assess-trail-conditions在 Claude Code 中复制并粘贴此命令以安装该技能
技能文档
Wegbedingungen bewerten
Bewerten current trail conditions for safety decision-making vor a planned hike or waehrend tour planning.
Wann verwenden
- The day vor or morning of a planned hike to make a go/no-go decision
- During tour planning to assess seasonal viability of a route
- After unexpected weather changes waehrend a multi-day tour
- When reports suggest trail damage, closures, or unusual hazards
- Before committing to an alpine or exposed route
Eingaben
- Erforderlich: Trail name, region, and approximate coordinates or waypoints
- Erforderlich: Planned date(s) of the hike
- Optional: Trail difficulty rating (SAC T1-T6)
- Optional: Maximum elevation on the route
- Optional: Known hazard points (river crossings, exposed ridges, glaciers)
- Optional: Group experience level (affects risk tolerance thresholds)
Vorgehensweise
Schritt 1: Sammeln Weather Data
Sammeln weather forecasts from multiple sources for the trail's elevation range.
Weather Data Sources (in preference order):
┌────────────────────────┬──────────────────────────────────────┐
│ Source │ Best for │
├────────────────────────┼──────────────────────────────────────┤
│ National weather svc │ Official forecasts with warnings │
│ (MeteoSwiss, ZAMG, │ │
│ DWD, Meteo-France) │ │
├────────────────────────┼──────────────────────────────────────┤
│ Mountain-specific │ Altitude-stratified forecasts │
│ forecasts (e.g., │ (valley vs. summit conditions) │
│ bergfex, meteoblue) │ │
├────────────────────────┼──────────────────────────────────────┤
│ Avalanche bulletins │ Snow stability (winter/spring) │
│ (SLF, EAWS members) │ │
├────────────────────────┼──────────────────────────────────────┤
│ Local webcams │ Real-time visual conditions │
├────────────────────────┼──────────────────────────────────────┤
│ Recent trip reports │ On-the-ground observations │
└────────────────────────┴──────────────────────────────────────┘
Sammeln die folgenden data points:
Weather Assessment:
┌─────────────────────┬───────────────┬───────────────────────────┐
│ Parameter │ Valley │ Summit/Ridge │
├─────────────────────┼───────────────┼───────────────────────────┤
│ Temperature (C) │ │ │
│ Wind speed (km/h) │ │ │
│ Wind gusts (km/h) │ │ │
│ Precipitation (mm) │ │ │
│ Precipitation type │ │ │
│ Visibility (km) │ │ │
│ Cloud base (m) │ │ │
│ Freezing level (m) │ │ │
│ Snow line (m) │ │ │
│ Thunderstorm risk │ │ │
│ UV index │ │ │
└─────────────────────┴───────────────┴───────────────────────────┘
Erwartet: Weather data from mindestens 2 independent sources, with altitude-specific information for both the lowest and highest points of the route.
Bei Fehler: If detailed mountain forecasts are unavailable for the specific region, use general forecasts with altitude adjustments: temperature drops ungefaehr 6.5 C per 1000 m of elevation gain, wind speed increases with altitude and exposure. If forecasts disagree, plan for the worse prediction.
Schritt 2: Bewerten Terrain Conditions
Bewerten the current state of the trail surface, snow, water, and exposure hazards.
Terrain Condition Factors:
┌──────────────────────┬─────────────────────────────────────────┐
│ Factor │ Assessment Method │
├──────────────────────┼─────────────────────────────────────────┤
│ Snow cover │ Compare current snow line to route's │
│ │ highest point. If route goes above snow │
│ │ line, assess whether snow gear is │
│ │ needed and if the group has it. │
├──────────────────────┼─────────────────────────────────────────┤
│ Ice │ North-facing slopes above freezing │
│ │ level may retain ice even in summer. │
│ │ Check recent overnight temps. │
├──────────────────────┼─────────────────────────────────────────┤
│ River/stream │ Check recent rainfall totals. Rivers │
│ crossings │ can be impassable 24-48 hrs after │
│ │ heavy rain or during snowmelt peak. │
├──────────────────────┼─────────────────────────────────────────┤
│ Rockfall zones │ More active after freeze-thaw cycles │
│ │ and rain. Early morning passage is │
│ │ safer (frozen in place overnight). │
├──────────────────────┼─────────────────────────────────────────┤
│ Mud/erosion │ Recent rain makes steep trails │
│ │ slippery and increases fall risk. │
│ │ Poles recommended. │
├──────────────────────┼─────────────────────────────────────────┤
│ Exposure (ridges, │ Wind speed determines whether exposed │
│ cliff paths) │ sections are safe. Gusts >60 km/h make │
│ │ exposed ridges dangerous. │
└──────────────────────┴─────────────────────────────────────────┘
Data sources for terrain conditions:
- Recent trip reports (hiking forums, mountain club sites)
- Hut warden reports (call the nearest hut)
- Webcams at or near the trail
- Avalanche bulletins (include snow and terrain info even in summer)
- Trail maintenance authorities (national park offices, Alpenverein sections)
Erwartet: A terrain assessment fuer jede significant hazard point on the route, basierend auf current data no more than 48 hours old.
Bei Fehler: If current condition data is unavailable (remote area, no recent reports), assume conditions are worse than average for the season. Contact the nearest staffed hut or mountain rescue station for local knowledge.
Schritt 3: Bewerten Trail Status
Pruefen auf closures, diversions, and maintenance issues on the planned route.
Trail Status Sources:
┌────────────────────────┬──────────────────────────────────────┐
│ Source │ Information type │
├────────────────────────┼──────────────────────────────────────┤
│ Official trail portals │ Closures, diversions, damage reports │
│ (regional/national) │ │
├────────────────────────┼──────────────────────────────────────┤
│ National park websites │ Seasonal closures (wildlife, snow) │
├────────────────────────┼──────────────────────────────────────┤
│ Hut websites/phones │ Hut opening dates, path conditions │
├────────────────────────┼──────────────────────────────────────┤
│ Local tourism offices │ Recent trail work, event closures │
├────────────────────────┼──────────────────────────────────────┤
│ Hiking community │ Unofficial reports, photos, GPX │
│ (forums, apps) │ tracks showing actual paths taken │
└────────────────────────┴──────────────────────────────────────┘
Check for:
- Full closures: Trail impassable or legally closed (wildlife protection, construction)
- Partial closures: Sections closed with official diversions
- Seasonal closures: Trail not yet open for the season (snow, hut not staffed)
- Damage reports: Landslides, bridge washouts, trail erosion
- Event impacts: Races, military exercises, hunting seasons
Erwartet: Confirmed trail status (open, teilweise closed, closed) with any diversions mapped and time impact estimated.
Bei Fehler: If trail status cannot be confirmed, plan for potential diversions. Carry a detailed map (not just the trail app route) so that alternatives kann navigated on the spot. If a trail is listed as closed, respect the closure even if it appears passable.
Schritt 4: Rate Safety Level
Kombinieren all assessment data into an overall safety rating.
Safety Rating Criteria:
┌─────────┬────────────────────────────────────────────────────┐
│ Rating │ Criteria │
├─────────┼────────────────────────────────────────────────────┤
│ GREEN │ All of: │
│ │ - Weather forecast stable, no severe warnings │
│ │ - Trail open with no significant hazards │
│ │ - Terrain conditions normal for the season │
│ │ - Route within group's capability │
│ │ - Visibility good (>5 km at altitude) │
├─────────┼────────────────────────────────────────────────────┤
│ YELLOW │ One or more of: │
│ │ - Afternoon thunderstorm risk (>30%) │
│ │ - Wind gusts 40-60 km/h on exposed sections │
│ │ - Trail partially closed (diversion available) │
│ │ - Snow patches requiring care but no special gear │
│ │ - Recent rain making terrain slippery │
│ │ - Route near the group's capability limit │
│ │ Decision: Proceed with extra caution and backup │
├─────────┼────────────────────────────────────────────────────┤
│ RED │ Any of: │
│ │ - Severe weather warning (storm, heavy snow) │
│ │ - Wind gusts >60 km/h on exposed terrain │
│ │ - Trail closed (no safe diversion) │
│ │ - Snow/ice requiring gear the group lacks │
│ │ - Visibility <1 km on unmarked/exposed terrain │
│ │ - River crossings at dangerous water levels │
│ │ - Avalanche danger level 3+ on route │
│ │ - Route clearly exceeds group's capability │
│ │ Decision: Do not proceed. Choose alternative or │
│ │ postpone. │
└─────────┴────────────────────────────────────────────────────┘
For YELLOW ratings, define specific mitigation actions:
- Early start to beat nachnoon weather
- Turnaround time if conditions worsen
- Specific sections to monitor closely
- Communication plan if group separates
Erwartet: A clear GREEN, YELLOW, or RED rating with specific justification. YELLOW ratings include actionable mitigation steps and defined trigger points for abort.
Bei Fehler: If the assessment is inconclusive (insufficient data to rate confidently), treat it as YELLOW at minimum. Uncertainty should increase caution, not decrease it. If any single factor is RED, the overall rating is RED unabhaengig von other factors.
Schritt 5: Generieren Conditions Report
Compile the assessment into a concise, actionable report.
Conditions Report Template:
═══════════════════════════════════════════════
TRAIL CONDITIONS REPORT
───────────────────────────────────────────────
Trail: [Name / Route Number]
Date: [Assessment date and time]
Hike date:[Planned date]
Rating: [GREEN / YELLOW / RED]
───────────────────────────────────────────────
WEATHER SUMMARY
Valley: [temp]C, [wind] km/h, [precipitation]
Summit: [temp]C, [wind] km/h, [precipitation]
Outlook: [trend: improving / stable / deteriorating]
Alerts: [any active warnings]
TERRAIN CONDITIONS
Snow line: [elevation] m ([above/below] route max)
Trail surface: [dry / wet / muddy / icy / snow-covered]
Water levels: [normal / elevated / dangerous]
Rockfall risk: [low / moderate / high]
TRAIL STATUS
Status: [open / partially closed / closed]
Diversions: [none / details]
Known issues:[list any damage or hazards]
RECOMMENDATIONS
[Specific actions based on rating:]
- [e.g., Start by 06:00 to clear ridge before noon]
- [e.g., Carry microspikes for north-facing traverse]
- [e.g., Turnaround by 13:00 if clouds build]
DECISION
[GO / GO WITH CAUTION / NO-GO]
[Reasoning in 1-2 sentences]
═══════════════════════════════════════════════
Erwartet: A complete, dated conditions report that enables an informed go/no-go decision. The report sollte shareable with all group members and understandable ohne additional context.
Bei Fehler: If der Bericht cannot be completed (e.g., key data unavailable), state what is unknown and how it affects the decision. An incomplete assessment with acknowledged gaps is safer than a false sense of certainty.
Validierung
- Weather data collected from mindestens 2 independent sources
- Altitude-specific forecasts obtained (not just valley weather)
- Terrain conditions assessed for all key hazard points on the route
- Trail status verified (open/closed/diversions)
- Safety rating assigned with clear justification
- Mitigations defined for YELLOW ratings
- Conditions report is complete and dated
- Report shared with all group members
- Assessment is no more than 24 hours old at time of departure
Haeufige Stolperfallen
- Valley weather bias: Clear skies in the valley mean nothing at altitude. Always check summit-level forecasts; conditions kann dramatically different 1000 m higher.
- Stale data: A report from 3 days ago is unreliable. Mountain conditions change rapidly. Reassess on the morning of the hike.
- Optimism bias: The desire to hike a planned route makes people rationalize marginal conditions. If you have to argue the case for going, the conditions are probably not good enough.
- Single-source reliance: One forecast kann wrong. Cross-check with mindestens two sources, and weight local/mountain-specific sources over general ones.
- Ignoring trend: Current conditions kann acceptable but deteriorating. A deteriorating trend requires more caution than the snapshot suggests.
- Social pressure override: Never proceed because the group is eager or because you drove a long way. The mountain wird there next week; you might not be.
- Snow line miscalculation: The reported snow line is an average. North-facing slopes can hold snow 200-500 m unter der Berichted line.
Verwandte Skills
plan-hiking-tour— uses this assessment as input for the safety evaluation stepcheck-hiking-gear— gear adjustments basierend auf assessed conditions (add microspikes, extra layers)plan-tour-route— trail condition awareness for broader tour planningcreate-spatial-visualization— visualize hazard zones on a map overlay
GitHub 仓库
相关推荐技能
railway-docs
文档Railway Docs Skill可实时获取最新的Railway官方文档,确保回答的准确性。当开发者询问Railway功能特性、工作原理或分享docs.railway.com链接时,应优先使用此技能。它通过专门的LLM优化文档源提供最新信息,避免依赖过时记忆来回答技术问题。
n8n-code-python
文档该Skill为在n8n平台的Python代码节点中编写代码提供专家指导,特别适用于需要使用_input/_json/_node语法、Python标准库或了解n8n中Python限制的场景。它强调JavaScript应作为首选方案,仅当需要特定Python功能或对Python语法更熟悉时才使用Python。Skill提供了快速入门模板和关键注意事项,帮助开发者在n8n中高效编写Python代码。
archon
文档Archon Skill为开发者提供了基于RAG的语义搜索和项目任务管理功能,可通过REST API访问知识库。它支持文档搜索、网站爬取、文件上传和版本控制,适用于技术文档查询和项目管理场景。首次使用时需要配置Archon主机地址,建议在处理外部文档时优先使用该Skill。
n8n-code-javascript
文档这个Skill为n8n工作流中的JavaScript代码节点提供专业指导,涵盖数据处理、HTTP请求和日期操作等核心场景。它详细解释了如何正确使用n8n特有的`$input`/`$json`语法、`$helpers`工具以及DateTime对象,并包含关键的错误排查和模式选择建议。开发者通过该Skill能快速掌握Code节点的正确返回格式、数据访问方法和常见陷阱解决方案。
