AlvaroLaraFF/weather-correlation
.claude/skills/weather-correlation/SKILL.md
Cross-reference recent runs/rides with historical weather (temperature, humidity, wind) from Open-Meteo to find correlations with performance. Use when the user asks "do I run worse in the heat", "weather impact", "temperature vs pace".
tools
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add AlvaroLaraFF/strava-coach weather-correlationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:42 PM37.4s3 files scanned
SKILL.md
- name:
- weather-correlation
- description:
- >
- allowed-tools:
- Bash(python3 *), Read
weather-correlation
For each recent activity, queries the free Open-Meteo Archive API (no key required) using the activity's start coordinates and timestamp, then computes correlation between temperature and pace/HR.
Run
python3 .claude/skills/weather-correlation/scripts/weather.py --days 60 --sport Run
Present
Per-activity table: date, temp (°C), pace, HR. Then a one-line correlation verdict ("each +5°C costs ~10s/km", or "no clear correlation").
On error: auto-recovery chain
| Error contains | Action |
|---|---|
| No token | Invoke strava-setup, retry |
| No <Sport> activities / No data | Invoke strava-sync --level summary, retry |
| anything else | Surface |
After presenting: persist to memory (MANDATORY)
Save a qualitative observation to memory — opinions, patterns, coaching notes. Never store raw numeric values (those are recomputable from the DB). Only write if the observation is NEW or CHANGED vs existing memory. See CLAUDE.md → Memory protocol.
Related Skills
AlvaroLaraFF/weekly-log
data-ai
VerifiedTrustedCommunity
Show a weekly training log: activities grouped by ISO week and sport, with totals for distance, time and elevation. Use when the user asks "what did I do this week", "weekly summary", "training log".
SKILL.mdUpdated Apr 16, 2026
AlvaroLaraFF/tri-discipline-balance
testing
VerifiedTrustedCommunity
Show how the user's training time and volume distribute across run, ride and swim, and flag underweighted disciplines. Use when the user asks "am I balanced", "discipline balance", "which sport am I neglecting".
SKILL.mdUpdated Apr 16, 2026
AlvaroLaraFF/tri-combined-load
data-ai
VerifiedTrustedCommunity
Compute a combined CTL/ATL/TSB across run, ride and swim for triathletes. Use when the user asks "my combined load", "triathlon training load", "total TSS across sports".
SKILL.mdUpdated Apr 16, 2026
AlvaroLaraFF/training-plan
data-ai
VerifiedTrustedCommunity
Persist a confirmed weekly training plan (one row per session with target HR range and pace range) and measure adherence against actual activities. Use when the user says "my plan this week", "what's on today", "save this plan", "how am I doing vs plan", "plan adherence", "did I complete this week", or any equivalent in Spanish.
SKILL.mdUpdated Apr 16, 2026