Created by
Vekta
Last updated
Categories
Planning
Quick prompt
Made for
Coaches
Runs
Every week
Topics
Load
Scheduling
Planning
Every Sunday it reads each athlete's last four weeks, their availability for next week, any upcoming event and what is already planned, then places sessions from your own training collections on the days they can train, following the planning rules you give it.
Every session is saved hidden: a draft only you can see. Check the week in the Vekta calendar and unhide what you keep; unhiding sends it to the athlete's Garmin, Wahoo, COROS, Zwift or Hammerhead, with targets Vekta works out from their own zones. It never invents a rule of its own. The coaching decisions stay with you.
How to run it
1
Paste the prompt
Open Claude Code, Codex or Gemini CLI and paste it. Fill in anything in square brackets.
2
Or install the file
Unzip it into ~/.claude/skills for Claude Code, or ~/.agents/skills for Codex and Gemini CLI. Then run it as a Skill by name each time.
3
Let it run
A scheduled skill runs on your own computer, so it has to be on. Everything it reads is your data, through your key.
What it touches
Reads from Vekta
Rides, planned sessions, notes, events, your training library
Writes to Vekta
Planned sessions, saved hidden: a draft only you can see until you unhide it
Works in
Claude Code, Codex, Gemini CLI
GET THIS SKILL
The prompt, and the file.
Unlocked on this browser for a year. Paste the prompt into Claude Code, Codex or Gemini CLI, or install the file and run it by name.
THE PROMPT AND FILE
Run this now, then every Sunday at 6pm. First, ask me for my planning rules: hard days a week, rest days, how I build volume, what I do before a race. Save them to a file and follow them exactly; never add rules of your own. Then, for each athlete I coach in Vekta, read their last four weeks of sessions and planned sessions, their availability and rest day notes for next week, and any event in the next eight weeks. Choose sessions only from my training collections and place them on days they are available. Show me every athlete's week as a table before writing anything. Check next week for hidden sessions you created earlier and never add a second copy. On my yes, create each session as a hidden training prescription: a draft only I can see, not sent to their devices. If I coach an athlete in more than one workspace, ask me which one. Tell me what was created. I check the week in the Vekta calendar and unhide what I keep. If my library is missing durations or descriptions, list what is missing instead of guessing. Docs: api.joinvekta.com/openapi.json
Planning
Weekly availability
Paste your athletes' messages about next week and it turns them into availability notes on each athlete's Vekta calendar.
Analysis
Planned versus performed
A check of every session you planned against what each athlete actually rode, interval by interval, and flags where compliance or power is slipping.
Planning
Race training plan
A periodised plan for your target race, built from the course's demands and your power profile, and fitted to the hours you actually train.



