菜单
Audit Boise Trails Challenge route or activity geometry against official segment-edge requirements. Use when reviewing challenge completion, segment lists, trail-system packages, route optimization, activity proof, GPX coverage, or ascent-direction correctness.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Review Boise Trails Challenge GPX, phone packets, cue sheets, live maps, field cards, field-packet exports, or certification audits for field usability. Use before treating a GPX, route card, written menu, phone packet, live map, cue sheet, or generated field artifact as runnable from the parked car and back.
Repair Boise Trails Challenge plans after field feedback, missed segments, extra segments, closures, route-list changes, access blockers, condition blockers, or artifact drift. Use before discarding a route, manually skipping a future outing, or preserving an old plan unchanged.
Verify access assumptions for Boise Trails Challenge routes. Use when a route starts, ends, parks, shuttles, re-parks, or transitions at a mapped trailhead, pullout, road crossing, residential road, OSM parking feature, private Strava-derived anchor, or informal access point.
Check whether a Boise Trails Challenge route choice, field completion, split-start replacement, closure, access change, or time-window decision preserves the remaining certified menu and future challenge feasibility.
Evaluate Boise Trails Challenge outings by real field cost instead of map cost. Use when ranking, replacing, or recommending best, fastest, shortest, most efficient, or most practical outings, especially when p75 timing, DEM effort, heat, water, bailout, parking, or hard stops matter.
基于 SOC 职业分类
| name | btc-edge-coverage-audit |
| description | Audit Boise Trails Challenge route or activity geometry against official segment-edge requirements. Use when reviewing challenge completion, segment lists, trail-system packages, route optimization, activity proof, GPX coverage, or ascent-direction correctness. |
Core heuristic: BTC is edge coverage under human constraints, not waypoint visitation.
years/2026/inputs/official/api-pull-2026-06-13/official_foot_segments.geojson unless the user requested another year.ascent segments, verify the segment is climbed in the required direction.years/2026/inputs/open-data/special-management-rules-2026.json when applicable.direction=both means the land manager allows both directions or all user modes on that trail.complete, partial, direction_failed, not_covered, or needs_activity_geometry.