assess-trail-conditions
Evaluate current trail conditions including weather, snow line, river crossings, exposure, and trail maintenance status for safety decision-making. Produces a GREEN/YELLOW/RED safety rating with actionable go/no-go recommendations. Use the day before or morning of a planned hike, during tour planning to assess seasonal viability, after unexpected weather changes on a multi-day tour, when reports suggest trail damage or closures, or before committing to an alpine or exposed route.
Best use case
assess-trail-conditions is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Evaluate current trail conditions including weather, snow line, river crossings, exposure, and trail maintenance status for safety decision-making. Produces a GREEN/YELLOW/RED safety rating with actionable go/no-go recommendations. Use the day before or morning of a planned hike, during tour planning to assess seasonal viability, after unexpected weather changes on a multi-day tour, when reports suggest trail damage or closures, or before committing to an alpine or exposed route.
Teams using assess-trail-conditions should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/assess-trail-conditions/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How assess-trail-conditions Compares
| Feature / Agent | assess-trail-conditions | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Evaluate current trail conditions including weather, snow line, river crossings, exposure, and trail maintenance status for safety decision-making. Produces a GREEN/YELLOW/RED safety rating with actionable go/no-go recommendations. Use the day before or morning of a planned hike, during tour planning to assess seasonal viability, after unexpected weather changes on a multi-day tour, when reports suggest trail damage or closures, or before committing to an alpine or exposed route.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Assess Trail Conditions Evaluate current trail conditions for safety decision-making before a planned hike or during tour planning. ## When to Use - The day before 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 during a multi-day tour - When reports suggest trail damage, closures, or unusual hazards - Before committing to an alpine or exposed route ## Inputs - **Required**: Trail name, region, and approximate coordinates or waypoints - **Required**: 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) ## Procedure ### Step 1: Gather Weather Data Collect 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 │ └────────────────────────┴──────────────────────────────────────┘ ``` Collect the following 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 │ │ │ └─────────────────────┴───────────────┴───────────────────────────┘ ``` **Got:** Weather data from at least 2 independent sources, with altitude-specific information for both the lowest and highest points of the route. **If fail:** If detailed mountain forecasts are unavailable for the specific region, use general forecasts with altitude adjustments: temperature drops approximately 6.5 C per 1000 m of elevation gain, wind speed increases with altitude and exposure. If forecasts disagree, plan for the worse prediction. ### Step 2: Assess Terrain Conditions Evaluate 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) **Got:** A terrain assessment for each significant hazard point on the route, based on current data no more than 48 hours old. **If fail:** 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. ### Step 3: Evaluate Trail Status Check for 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: 1. **Full closures**: Trail impassable or legally closed (wildlife protection, construction) 2. **Partial closures**: Sections closed with official diversions 3. **Seasonal closures**: Trail not yet open for the season (snow, hut not staffed) 4. **Damage reports**: Landslides, bridge washouts, trail erosion 5. **Event impacts**: Races, military exercises, hunting seasons **Got:** Confirmed trail status (open, partially closed, closed) with any diversions mapped and time impact estimated. **If fail:** If trail status cannot be confirmed, plan for potential diversions. Carry a detailed map (not the trail app route) so that alternatives can be navigated on the spot. If a trail is listed as closed, respect the closure even if it appears passable. ### Step 4: Rate Safety Level Combine 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 afternoon weather - Turnaround time if conditions worsen - Specific sections to monitor closely - Communication plan if group separates **Got:** A clear GREEN, YELLOW, or RED rating with specific justification. YELLOW ratings include actionable mitigation steps and defined trigger points for abort. **If fail:** 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 regardless of other factors. ### Step 5: Generate 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] ═══════════════════════════════════════════════ ``` **Got:** A complete, dated conditions report that enables an informed go/no-go decision. The report should be shareable with all group members and understandable without additional context. **If fail:** If the report 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. ## Validation - [ ] Weather data collected from at least 2 independent sources - [ ] Altitude-specific forecasts obtained (not 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 ## Pitfalls - **Valley weather bias**: Clear skies in the valley mean nothing at altitude. Always check summit-level forecasts; conditions can be 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 can be wrong. Cross-check with at least two sources, and weight local/mountain-specific sources over general ones. - **Ignoring trend**: Current conditions may be 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 will be 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 below the reported line. ## Related Skills - `plan-hiking-tour` — uses this assessment as input for the safety evaluation step - `check-hiking-gear` — gear adjustments based on assessed conditions (add microspikes, extra layers) - `plan-tour-route` — trail condition awareness for broader tour planning - `create-spatial-visualization` — visualize hazard zones on a map overlay
Related Skills
perform-csv-assessment
Perform a Computer Systems Validation (CSV) assessment following GAMP 5 methodology. Covers user requirements, risk assessment, IQ/OQ/PQ planning, traceability matrix creation, and validation summary reporting. Use when a new computerized system is being introduced in a GxP environment, when an existing validated system is undergoing significant change, when periodic revalidation is required, or when a regulatory inspection demands a validation gap analysis.
implement-audit-trail
Implement audit trail functionality for R projects in regulated environments. Covers logging, provenance tracking, electronic signatures, data integrity checks, and 21 CFR Part 11 compliance. Use when an R analysis requires electronic records compliance (21 CFR Part 11), when you need to track who did what and when in an analysis, when implementing data provenance tracking, or when creating tamper-evident analysis logs for regulatory submissions.
assess-ip-landscape
Map the intellectual property landscape for a technology domain or product area. Covers patent cluster analysis, white space identification, competitor IP portfolio assessment, freedom-to-operate preliminary screening, and strategic IP positioning recommendations. Use before starting R&D in a new technology area, when evaluating market entry against incumbents with strong patent portfolios, preparing for investment due diligence, informing a patent filing strategy, or assessing freedom-to-operate risk for a new product.
assess-context
AI context assessment — evaluating problem malleability, mapping structural rigidity versus flexibility, analyzing transformation pressure, and estimating capacity to adapt. Use when a complex task feels stuck and it is unclear whether to push through or pivot, before a significant approach change to assess whether the current reasoning structure can support it, when accumulated workarounds suggest the underlying approach may be wrong, or as a periodic structural health check during extended multi-step tasks.
skill-name-here
One to three sentences describing what this skill accomplishes, followed by key activation triggers. This field is the primary mechanism agents use to decide whether to activate the skill — it is read during discovery before the full body is loaded. Start with a verb. Include the most important "when to use" conditions inline. Max 1024 characters.
write-vignette
Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.
write-validation-documentation
Write IQ/OQ/PQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.
write-testthat-tests
Write comprehensive testthat (edition 3) tests for R package functions. Covers test organization, expectations, fixtures, mocking, snapshot tests, parameterized tests, and achieving high coverage. Use when adding tests for new package functions, increasing test coverage for existing code, writing regression tests for bug fixes, or setting up test infrastructure for a package that lacks it.
write-standard-operating-procedure
Write a GxP-compliant Standard Operating Procedure (SOP). Covers regulatory SOP template structure (purpose, scope, definitions, responsibilities, procedure, references, revision history), approval workflow design, periodic review scheduling, and operational procedures for system use. Use when a new validated system requires operational procedures, when existing informal procedures need formalisation, when an audit finding cites missing procedures, when a change control triggers SOP updates, or when periodic review identifies outdated procedural content.
write-roxygen-docs
Write roxygen2 documentation for R package functions, datasets, and classes. Covers all standard tags, cross-references, examples, and generating NAMESPACE entries. Follows tidyverse documentation style. Use when adding documentation to new exported functions, documenting internal helpers or datasets, documenting S3/S4/R6 classes and methods, or fixing documentation-related R CMD check notes.
write-incident-runbook
Create structured incident runbooks with diagnostic steps, resolution procedures, escalation paths, and communication templates for effective incident response. Use when documenting response procedures for recurring alerts, standardizing incident response across an on-call rotation, reducing MTTR with clear diagnostic steps, creating training materials for new team members, or linking alert annotations directly to resolution procedures.
write-helm-chart
Create production-ready Helm charts for Kubernetes application deployment with templating, values management, chart dependencies, hooks, and testing. Covers chart structure, Go template syntax, values.yaml design, chart repositories, versioning, and best practices for maintainable and reusable charts. Use when packaging a Kubernetes application for repeatable deployments, parameterizing manifests for multiple environments, managing complex multi-component applications with dependencies, or standardizing deployment practices with versioned rollback capability across teams.