agentsclimarketplace

Strength training plan

Skill SkillMedev/skills/skills/strength-training-plan

Use when someone starts lifting, hits a strength or hypertrophy plateau, restructures a lifting program, or wants to build strength or muscle - designing a progressive resistance program with splits, compound movement patterns, sets/reps, progressive overload, and deloads from barbells and dumbbells. General fitness guidance, not medical advice. Owns resistance/strength training only. Do NOT use to program high-intensity interval conditioning or circuits (use fitness-program), a steady-state aerobic-base or Zone 2 block (use zone-2-cardio-plan), or a mobility/flexibility routine (use mobility-routine).From its SKILL.md

Install
npx -y skills add SkillMedev/skills --skill strength-training-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.1 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

Strength Training Plan

Design a structured, progressive strength program based on training age, available days, and equipment. Default to a barbell-and-dumbbells gym environment; note escapes for home and minimal equipment. This is general fitness guidance, not medical advice - consult a qualified coach or sports medicine professional for injuries or complex needs.

Establish Training Age and Frequency

Beginners (under 12 months consistent training) respond best to full-body sessions 3 days per week. Intermediates (1-3 years) benefit from 3-4 days using an upper/lower or push/pull/legs split. Advanced trainees (3+ years) typically need 4-5 days to drive progress. Match frequency to recovery capacity - more is not always better.

Core Movement Patterns

Every program should include all five patterns: hip hinge (deadlift, Romanian deadlift), squat (back squat, goblet squat), horizontal push (bench press, push-up), horizontal pull (row), and vertical pull (pull-up, lat pulldown). Vertical push (overhead press) is the sixth and should be included when shoulder health allows. These are the pillars; accessories are optional.

Progressive Overload Protocol

The default progression scheme for beginners: add weight every session (linear progression). For intermediates: add weight every week or every other week. Track every working set. When the prescribed reps are hit across all sets with good form, add 2.5-5 kg to upper body lifts and 5 kg to lower body lifts next session. If progression stalls for 2 consecutive weeks, deload (reduce load by 10-15% for one week) before pushing again.

Rep and Set Ranges

For strength (1RM focus): 3-5 sets of 3-5 reps at 80-90% effort. For hypertrophy (size focus): 3-5 sets of 6-12 reps. For endurance or work capacity: 2-4 sets of 12-20 reps. Mixing ranges across a program is normal - compound lifts heavier, accessories lighter.

Warm-Up and Session Structure

Start every session with 5 minutes of light cardio or general movement, then 2-3 warm-up sets of the first compound lift (50% and 70% of working weight). Keep sessions to 45-75 minutes. Compound lifts first when fresh, isolation accessories last.

Recovery and Deload

Schedule a deload week every 4-8 weeks of hard training: reduce volume by 40-50% while keeping intensity moderate. Sleep 7-9 hours per night - it is the single most effective recovery tool available. Protein timing matters less than total daily protein; focus there first.

Deliverable

Produce a written program document the trainee can log against session by session, containing: (1) the weekly split with named training days matched to training age; (2) each session's exercise list mapped to the five (or six) movement patterns; (3) explicit sets × reps × effort per lift tied to the goal; (4) the progression rule - exact increments and the two-week stall trigger with its deload response; (5) the scheduled deload weeks; and (6) the warm-up protocol. Include equipment substitutions where the default barbell setup is unavailable.

Quality Bar

A finished program must:

  • Match weekly frequency and split to the trainee's training age and stated recovery capacity, not to ambition.
  • Cover all five core movement patterns across the week (add vertical push when shoulders allow).
  • Specify a concrete progression rule and a stall trigger - what to add, when, and what to do when it stops working.
  • Assign explicit sets, reps, and effort per lift, tied to the trainee's goal (strength, hypertrophy, or work capacity).
  • Schedule deloads up front, not reactively.
  • Fit each session inside 45-75 minutes with compounds before isolation.

What NOT to Do

  • Do not prescribe a 5-6 day advanced split to a beginner - frequency outruns recovery and progress stalls.
  • Do not write open-ended progression ("just add weight when you can"). Name the increment and the stall rule.
  • Do not skip the hinge or vertical pull because they are uncomfortable; rebalanced programs build imbalances.
  • Do not swap the exercise list every week ("program hopping") - progressive overload requires repeating the same lifts long enough to measure and beat them.
  • Do not take every working set to failure; chronic failure training inflates fatigue faster than it drives adaptation and wrecks the next session's quality. Leave 1-3 reps in reserve on most sets.
  • Do not bolt conditioning intervals, an aerobic base, or a mobility flow into this program - hand those off to fitness-program, zone-2-cardio-plan, and mobility-routine.
  • Do not give injury rehab or medical advice. Refer out.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most plan spec skills give in ~1.0k tokens

Counted across 1,099 of the 1,860 authors here whose files we hold, read 2026-08-07

  • Ask one question at a timein 51 of 1099
  • Break plans into vertical slicesin 29 of 1099, across 11 files
  • Publish issues in dependency orderin 27 of 1099, across 9 files
  • Iterate until user approves the breakdownin 25 of 1099, across 7 files
  • Explore the repository to understand the codebase statein 24 of 1099, across 7 files
  • Use domain glossary vocabularyin 23 of 1099, across 5 files
  • Apply correct triage labels to published issuesin 23 of 1099, across 5 files
  • Prefer AFK slices over HITLin 22 of 1099, across 7 files
  • Write a specification before writing any codein 22 of 1099, across 14 files
  • Write failing tests before implementation codein 22 of 1099, across 20 files
  • Ask clarifying questions until requirements are concretein 21 of 1099, across 13 files
  • Respect existing architecture decision recordsin 20 of 1099, across 5 files

Said here and by no other author read

  • target seven to nine hours of sleep nightly
  • design a progressive strength program
  • match frequency and split to training age
  • include all five core movement patterns
  • track every working set
  • add weight when rep targets are met

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,861. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.