assess-trail-conditions
정보
이 스킬은 날씨, 지형, 관리 상태 데이터를 분석하여 트레일 안전성을 평가하고 GREEN/YELLOW/RED 등급과 진행/중지 권고안을 제공합니다. 등산 계획 수립 중이나 변화하는 조건에 대응하여 노출 위험, 설선, 하천 횡단 등의 위험을 평가하도록 설계되었습니다. 개발자들은 여행 또는 야외 활동 애플리케이션에서 안전 결정을 지원하기 위해 이 기능을 통합할 수 있습니다.
빠른 설치
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-conditionsClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Assess Trail Conditions
Eval current trail conditions → safety decision pre-hike or during tour plan.
Use When
- Day before or morning of planned hike → go/no-go
- Tour planning → seasonal viability
- After unexpected weather on multi-day tour
- Reports suggest trail damage, closures, unusual hazards
- Before committing alpine or exposed route
In
- Required: Trail name, region, coords/waypoints
- Required: Planned date(s)
- Optional: Difficulty (SAC T1-T6)
- Optional: Max elevation
- Optional: Known hazard pts (river crossings, exposed ridges, glaciers)
- Optional: Group exp level (risk tolerance thresholds)
Do
Step 1: Gather Weather
Forecasts from multi srcs for 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 │
└────────────────────────┴──────────────────────────────────────┘
Collect:
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 │ │ │
└─────────────────────┴───────────────┴───────────────────────────┘
→ Weather from ≥2 independent srcs + altitude-specific for lowest + highest route pts.
If err: Detailed mountain forecasts unavail for region → general forecasts + altitude adjustments: temp drops ~6.5 C per 1000 m gain, wind increases w/ altitude + exposure. Forecasts disagree → plan worse prediction.
Step 2: Assess Terrain
Current state of trail surface, snow, water, 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 srcs for terrain:
- Recent trip reports (forums, club sites)
- Hut warden reports (call nearest)
- Webcams at/near trail
- Avalanche bulletins (snow + terrain info even summer)
- Trail maintenance authorities (nat park offices, Alpenverein)
→ Terrain assessment per significant hazard pt, current data ≤48 hr old.
If err: Current data unavail (remote, no recent reports) → assume worse than avg for season. Contact nearest staffed hut or mountain rescue for local knowledge.
Step 3: Eval Trail Status
Closures, diversions, maintenance on 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 w/ official diversions
- Seasonal closures: Not yet open (snow, hut not staffed)
- Damage reports: Landslides, bridge washouts, trail erosion
- Event impacts: Races, military exercises, hunting seasons
→ Confirmed trail status (open, partially closed, closed) + diversions mapped + time impact estimated.
If err: Status can't be confirmed → plan potential diversions. Carry detailed map (not just trail app route) → alternatives navigable on spot. Listed closed → respect even if appears passable.
Step 4: Rate Safety Level
Combine all into 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. │
└─────────┴────────────────────────────────────────────────────┘
YELLOW ratings → specific mitigation actions:
- Early start → beat afternoon weather
- Turnaround time if conditions worsen
- Specific sections to monitor closely
- Communication plan if group separates
→ Clear GREEN/YELLOW/RED + specific justification. YELLOW → actionable mitigation + defined trigger pts for abort.
If err: Inconclusive (insufficient data) → treat YELLOW min. Uncertainty should increase caution. Any single RED → overall RED regardless of others.
Step 5: Generate Report
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]
═══════════════════════════════════════════════
→ Complete dated conditions report enabling informed go/no-go. Shareable w/ all group + understandable no additional ctx.
If err: Can't complete report (key data unavail) → state what unknown + how affects decision. Incomplete + acknowledged gaps safer than false certainty.
Check
- Weather from ≥2 independent srcs
- Altitude-specific forecasts (not just valley)
- Terrain assessed all key hazard pts
- Trail status verified (open/closed/diversions)
- Safety rating assigned + clear justification
- Mitigations defined for YELLOW
- Report complete + dated
- Report shared w/ all group members
- Assessment ≤24 hr old at departure
Traps
- Valley weather bias: Clear valley means nothing at altitude. Always check summit-level; dramatically different 1000 m higher.
- Stale data: Report from 3 days unreliable. Mountain conditions change rapidly. Reassess morning of hike.
- Optimism bias: Desire → rationalize marginal conditions. Argue case for going → probably not good enough.
- Single-src reliance: 1 forecast can be wrong. Cross-check ≥2 srcs, weight local/mountain-specific > general.
- Ignore trend: Current acceptable but deteriorating → more caution than snapshot suggests.
- Social pressure override: Never proceed because group eager or long drive. Mountain will be there next week; you might not.
- Snow line miscalc: Reported snow line = avg. North-facing slopes hold snow 200-500 m below reported.
→
plan-hiking-tour— uses this assessment as input for safety eval stepcheck-hiking-gear— gear adjustments per assessed conditions (microspikes, extra layers)plan-tour-route— trail condition awareness for broader tour planningcreate-spatial-visualization— visualize hazard zones on map overlay
GitHub 저장소
연관 스킬
railway-docs
문서이 스킬은 Railway의 기능, 작동 방식 또는 특정 문서 URL에 대한 질문에 답하기 위해 최신 Railway 문서를 가져옵니다. 개발자들이 Railway의 공식 소스로부터 정확하고 최신 정보를 직접 받을 수 있도록 보장합니다. 사용자가 Railway의 작동 방식을 묻거나 Railway 문서를 참조할 때 사용하세요.
n8n-code-python
문서이 Claude Skill은 n8n의 Code 노드에서 Python 코드를 작성할 때 전문적인 지침을 제공하며, 특히 Python 표준 라이브러리 사용과 n8n의 특수 구문인 `_input`, `_json`, `_node` 작업에 중점을 둡니다. 이는 개발자가 n8n 내에서 Python의 제한 사항을 이해하도록 돕고, 대부분의 워크플로에는 JavaScript 사용을 권장하면서도 특정 데이터 변환 요구사항에 대한 Python 솔루션을 제안합니다.
archon
문서Archon 스킬은 REST API를 통해 RAG 기반 시맨틱 검색과 프로젝트 관리를 제공합니다. 이 스킬을 사용하여 문서 검색, 계층적 프로젝트/태스크 관리, 문서 업로드 기능을 갖춘 지식 검색을 수행할 수 있습니다. 외부 문서를 검색할 때는 다른 소스를 사용하기 전에 항상 Archon을 최우선으로 활용하세요.
n8n-code-javascript
문서이 Claude Skill은 n8n의 Code 노드에서 JavaScript 코드 작성에 대한 전문적인 지침을 제공합니다. `$input`/`$json` 변수, HTTP 헬퍼, DateTime 처리와 같은 필수적인 n8n 특정 구문을 다루며 일반적인 오류를 해결합니다. Code 노드에서 사용자 정의 JavaScript 처리가 필요한 n8n 워크플로우를 개발할 때 활용하세요.
