race-strategy
Provides tactical race-day guidance for ultra runners, focusing on pacing, logistics, and contingency planning.
Install
mkdir -p .claude/skills/race-strategy && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15165" && unzip -o skill.zip -d .claude/skills/race-strategy && rm skill.zipInstalls to .claude/skills/race-strategy
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Race day tactics and strategy for trail/ultra running. Covers pacing protocols, aid station efficiency, mental strategies for managing dark moments, gear setup, drop bag planning, and contingency protocols for common race-day issues.Key capabilities
- →Plan race-day pacing strategy for upcoming events
- →Develop aid station tactics and efficiency protocols
- →Formulate mental strategies for managing ultra-distance challenges
- →Plan gear setup and drop bags for races
- →Design contingency plans for issues like blisters, GI problems, or getting lost
- →Conduct post-race debriefing and tactical analysis
How it works
This skill provides structured advice on pacing protocols, aid station efficiency, mental strategies, gear setup, and contingency planning based on ultrarunning principles.
Inputs & outputs
When to use race-strategy
- →Creating a race-day pacing strategy
- →Planning drop bag contents
- →Developing mental coping strategies for late-race fatigue
- →Designing contingency protocols for common race issues
About this skill
Race Strategy
When to use this skill
Use this skill when the request involves:
- Planning race-day pacing strategy for upcoming events
- Aid station tactics and efficiency protocols
- Mental strategies for managing ultra-distance challenges
- Gear setup and drop bag planning for races
- Contingency planning (blisters, GI issues, getting lost, DNF decisions)
- Pre-race logistics (race week protocol, course reconnaissance)
- Post-race debriefing and tactical analysis
Core principle: "Train hard, race smart"
Philosophy: Tactical errors cost more races than fitness limitations. A well-prepared athlete with poor tactics will underperform; an adequately prepared athlete with excellent tactics often exceeds expectations.
Evidence base: Ultrarunning Training Essentials (Koop, 2nd Ed.), Training for Uphill Athlete (House, Jornet, Johnston)
Pacing Protocols
Fundamental pacing strategies
Even pacing (recommended for most ultra runners):
- Maintain consistent effort (not speed!) throughout race
- Measured by HR or RPE, not pace/speed
- Best for: First-time distance attempts, conservative goal setting
- Evidence: Minimizes glycogen depletion, reduces risk of bonking
Positive split (start faster, slow down):
- Banking time early when fresh
- Risk: Depleting glycogen too early, "blowing up"
- Use cases: Very experienced, known course, aggressive time goals
- Warning: 80% of ultra runners who positive split regret it at mile 60+
Negative split (start slower, speed up):
- Conservative early, aggressive late
- Lower risk of bonking
- Best for: New to distance, challenging course, hot conditions
- Challenge: Requires discipline to hold back when feeling good
HR-based vs RPE-based pacing
Heart Rate (HR) based:
- Early race (first 25-30%): Stay below AeT (e.g., if AeT=160 bpm, cap at 155-158 bpm)
- Mid race (30-70%): Allow drift to AeT+5 bpm on climbs, return to AeT on flats/descents
- Late race (70%+): HR often decouples; switch to RPE
- Advantages: Objective, prevents over-exertion early
- Limitations: Heat/altitude/fatigue cause HR drift; less reliable late race
Rate of Perceived Exertion (RPE) based:
- Early race: RPE 3-4/10 ("could talk in full sentences easily")
- Mid race: RPE 4-6/10 ("conversational but requires focus")
- Late race: RPE 6-8/10 ("can speak 3-5 words at a time")
- Advantages: Works throughout race, accounts for fatigue/conditions
- Limitations: Requires experience to calibrate
Hybrid approach (recommended):
- Early race: Use HR to prevent overexertion
- Late race: Switch to RPE when HR decouples
- Crosscheck: If RPE feels much higher than HR suggests, slow down (fatigue/heat/altitude)
Terrain-based pacing adjustments
Uphills:
- Steep (>10% grade): Power hike if hiking pace = running pace
- Moderate (5-10% grade): Run if you can maintain conversational breathing
- Gentle (<5% grade): Run, but don't force pace
- Rule: If breathing becomes labored on uphill, slow down or hike
- Poles: Use on sustained climbs >5% grade to reduce quad load
Downhills:
- Steep (>10% grade): Control speed, use short steps, land midfoot
- Moderate (5-10% grade): Let gravity assist, but don't overstride
- Gentle (<5% grade): Run naturally, slight increase in pace acceptable
- Warning: Quad damage accumulates; downhill speed in first 30% of race = quad death in last 30%
- Eccentric loading: If quads burn on downhill, slow immediately (damage is progressive)
Flats:
- Opportunity to "bank time" without excessive cost
- Keep effort steady (RPE 4-6/10)
- Focus on efficiency: cadence 160-180 spm, relaxed shoulders
Distance-specific pacing
50K (3-6 hours):
- First 25K: Conservative (HR <AeT, RPE 3-4/10)
- Middle 15K: Steady (HR ~AeT, RPE 4-6/10)
- Final 10K: Push if feeling good (RPE 6-8/10)
- Aid station time: 1-2 min max per stop
100K (8-14 hours):
- First 40K: Very conservative (HR <AeT, RPE 3-4/10)
- Middle 40K: Steady (HR ~AeT, RPE 4-6/10), allow HR drift on climbs
- Final 20K: Survival mode (RPE varies, focus on forward progress)
- Aid station time: 2-5 min per stop, longer if needed for recovery
100 miles (20-30 hours):
- First 50 miles: Extremely conservative (HR well below AeT, RPE 2-4/10), "this feels too easy"
- Mile 50-80: Steady grind (HR often decoupled, RPE 5-7/10), manage fatigue
- Mile 80-100: Mental game (RPE 7-9/10), celebrate each mile
- Aid station time: 5-10 min acceptable if needed, efficiency still matters
- Night sections: Slow down 10-15% (reduced visibility, fatigue)
Aid Station Strategy
Time management protocol
Efficiency rule: Every minute at aid station = ~3 minutes of moving time to make up
- Example: 5-min stop vs 2-min stop = 9 minutes lost on course
Target times by distance:
- 50K: 1-2 min per stop (quick fuel, water, go)
- 100K: 2-5 min per stop (fuel, check feet if needed, recover slightly)
- 100 miles: 3-10 min per stop (fuel, recover, address issues), longer at crew-accessible points
In/out protocol:
- Approach (100m before): Decide what you need (water? food? gear change?)
- Arrival: State needs clearly to volunteers ("Fill both bottles, 3 gels, pretzels")
- Execute: While bottles fill, grab food, eat immediately
- Depart: Check you have everything, thank volunteers, GO
What to do at each aid station
Standard stops (no crew):
- Refill hydration (both bottles/bladder)
- Grab quick CHO (gels, bars, real food if tolerated)
- Eat/drink WHILE at station (don't leave with food in hand to "eat later")
- Quick body scan: feet ok? Chafing? Blisters forming?
Crew-accessible stops:
- All of above PLUS:
- Change socks if wet/hot spots detected
- Apply lube to chafing areas
- Change layers if weather changed
- Restock personal nutrition from drop bag
- Crew protocol: Crew should have gear ready, minimize talking, 5-min max
Major stops (e.g., halfway, mile 60):
- More time acceptable (5-10 min)
- Sit if needed (but set timer!)
- Address issues: blisters, tape hot spots, change clothes
- Eat real food if appetite allows (soup, potatoes, broth)
- Mental reset: "I'm starting a new race from here"
Drop bag planning
What to include in drop bags:
- Nutrition: Extra gels/bars you like (aid station may run out)
- Hydration: Electrolyte tablets, spare bottle if worried about loss
- Clothing: Extra layers (jacket, gloves, hat) + rain gear
- Foot care: Spare socks, blister kit (tape, needle, lube)
- Lighting: Spare batteries/headlamp, vest light
- Emergency: Ibuprofen (use sparingly!), duct tape, safety pins
- Mental: Motivational note to yourself, photo of family/goal
Drop bag locations (prioritize):
- Halfway point (critical for gear swap, nutrition restock)
- Before night section (lighting check, warm clothes)
- Before final push (mental reset items, fresh socks)
Label clearly: "Your Name - Drop Bag Mile X - [Race Name] 2026"
Mental Strategies
Race segmentation
Break race into manageable chunks:
- 50K: Think in 10K segments (5 segments)
- 100K: Think in 20K segments (5 segments) or aid-station-to-aid-station
- 100 miles: Think in 25-mile segments (quarters) or "sunrise to sunset"
Psychological trick: "I'm just running to the next aid station" (not "I have 60 miles to go")
Managing dark moments
Expect dark moments at predictable times:
- Mile 30-40 (50K): Post-glycogen-depletion dip, often around 4-5h mark
- Mile 50-65 (100K/100mi): Physical fatigue accumulating, night approaching
- Mile 80-90 (100mi): Sleep deprivation, accumulated damage, "why am I doing this?"
Dark moment protocol:
- Acknowledge: "This is normal, expected, temporary"
- Physical check: Eat, drink, check pace (am I going too hard?)
- Mental reset: Break race into smaller segment ("just get to next aid station")
- Positive self-talk: "I've trained for this, I can handle this"
- Time limit: Give it 20-30 minutes; if still dark, reassess
When dark moment lifts (it usually does): Celebrate mentally, but don't surge pace
Positive self-talk protocols
Mantras to use:
- "Relentless forward progress" (common ultra mantra)
- "One step at a time" (when feeling overwhelmed)
- "I've done harder things" (reference training or life challenges)
- "This is temporary" (pain is transient)
- Custom mantra (choose in training, use in race)
Avoid negative self-talk:
- ❌ "I'm not good enough" → ✅ "I'm doing my best"
- ❌ "I can't do this" → ✅ "I'm still moving forward"
- ❌ "This is too hard" → ✅ "This is supposed to be hard"
DNF (Did Not Finish) decision framework
When to DNF (prioritize safety):
- Medical emergency: Severe dehydration, hyponatremia, heat stroke, injury requiring medical attention
- Time cutoffs: If mathematically impossible to finish within cutoff, save yourself for another day
- Severe injury: Continuing would cause long-term damage (stress fracture, severe sprain)
When NOT to DNF (push through):
- General discomfort (this is ultra running!)
- Dark moment (these pass)
- Blisters (manageable with tape)
- Fatigue (if you can still move forward, keep going)
- "I'm slower than I wanted" (adjust goals, finish the race)
Decision protocol:
- Sit at aid station, eat/drink, address immediate issue
- Give yourself 10-20 minutes to reassess
- Ask: "Is this dangerous to my long-term health?" If yes → DNF. If no → continue.
- If DNF: Accept decision, don't dwell, learn for next time
Gear Setup
Mandatory gear (check race requirements)
Typical mandatory items:
- Hydration (minimum capacity specified, e.g., 1L)
- Nutrition (minimum calories, e.g., 500 cal)
- Lighting (headlamp + backup, specific lumens)
- Emergency (whistle, space blanket, first aid)
- Navigation (map, GPS, phone)
- Clothing (jacket, extra layer)
Content truncated.
When not to use it
- →When the request does not involve trail/ultra running tactics
- →When the user is not planning for a race day
- →When the user is not dealing with common race-day issues
Limitations
- →The skill recommends even pacing for most ultra runners to minimize glycogen depletion
- →The skill warns that 80% of ultra runners who positive split regret it at mile 60+
- →The skill advises slowing down 10-15% during night sections due to reduced visibility and fatigue
How it compares
This workflow offers a complete, evidence-based framework for race strategy, integrating pacing, nutrition, mental, and logistical aspects, which is more structured than general training advice.
Compared to similar skills
race-strategy side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| race-strategy (this skill) | 0 | 2mo | No flags | Advanced |
| travel-planner | 84 | 9mo | Review | Beginner |
| ultrathink | 28 | 2mo | No flags | Advanced |
| openspec-explore | 4 | 6mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
travel-planner
ailabs-393
This skill should be used whenever users need help planning trips, creating travel itineraries, managing travel budgets, or seeking destination advice. On first use, collects comprehensive travel preferences including budget level, travel style, interests, and dietary restrictions. Generates detailed travel plans with day-by-day itineraries, budget breakdowns, packing checklists, cultural do's and don'ts, and region-specific schedules. Maintains database of preferences and past trips for personalized recommendations.
ultrathink
dashed
Invoke deep sequential thinking for complex problem-solving. Use when the user says 'use ultrathink', 'ultrathink', or when tackling problems that require careful step-by-step reasoning, planning, hypothesis generation, or multi-step analysis.
openspec-explore
studyzy
进入探索模式 - 一个用于探索想法、调查问题和澄清需求的思考伙伴。当用户想要在进行更改之前或期间深入思考某事时使用。
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
thought-patterns
markpitt
Orchestrates comprehensive cognitive thinking patterns including sequential, systems, lateral, divergent/convergent, abductive, analogical, first-principles, double-loop learning, gestalt, metacognitive, and neurodivergent patterns (ADHD hyperfocus, autistic detail-orientation, dyslexic spatial reasoning). Analyzes tasks to select optimal pattern(s), chains multiple patterns when needed, and validates outputs before responding. Use for complex problem-solving, creative tasks, analytical challenges, or when diverse cognitive approaches enhance solution quality.
task-analyzer
shinpr
Metacognitive task analysis and skill selection. Analyzes task essence, estimates scale, and returns appropriate skills with metadata.