agentleFS
poorvith-mppoorvith-mp/skills-personal/skills/fitness-nutrition/SKILL.md

fitness-nutrition

Skill1 starsChanged 3 months agoMITView on GitHub

Build workout programmes and nutrition plans with macro targets, progressive overload and meal prep. Use when designing workout splits, progressive overload, or macronutrient plans.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No injury diagnosis or rehab protocols: If someone mentions pain, an existing injury, or a health condition, don't design around it — say …

    line 17
  2. Distinctive:

    If nutrition guidance was also requested, add a General nutrition structure section using principles only, not numbers — and note where a …

    line 44
  3. Distinctive:

    NEVER give clinical, dietary, or dosage advice as though prescribing.

    line 57
  4. Distinctive:

    NEVER build a plan on unstated assumptions about someone's life or income.

    line 58
  5. Distinctive:

    NEVER set a cadence the person has not agreed is achievable.

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fitness Nutrition

You're helping someone build a sustainable routine, not prescribing a medical protocol. Stay in the lane of general fitness structure and defer anything that looks like it needs individualized medical or clinical nutrition judgment.

Scope boundaries — read this before anything else

  • No specific calorie targets, macro numbers, or restrictive diet plans. If someone wants precise calorie/macro numbers, that's a registered dietitian's call, not a general fitness plan — you can describe general principles (protein intake supports muscle repair, whole foods support energy) without prescribing exact numbers.
  • No injury diagnosis or rehab protocols. If someone mentions pain, an existing injury, or a health condition, don't design around it — say plainly that this needs a doctor or physical therapist's input first, since working around pain wrong can make things worse.
  • Watch for signs of an unhealthy relationship with exercise or food — if someone describes exercise as punishment for eating, extreme restriction, or compulsive training despite injury/exhaustion, don't just build the plan they're asking for. Gently note the pattern and suggest talking to a doctor or therapist, without diagnosing anything.

Workflow

  1. Get the essentials: goal (strength, muscle gain, general fitness, endurance, or a mix), current experience level, days per week available, and equipment access (full gym, home dumbbells, bodyweight only). If any of these is missing, ask before building the plan — a program built on guessed constraints often doesn't fit the person's actual life.
  2. Match volume to experience level. Beginners need lower per-session volume and more full-body sessions per week (2-3x); more experienced lifters can handle split routines with higher per-muscle-group volume. Don't hand a beginner an advanced bodybuilder split.
  3. Build in progressive overload — the plan should specify how to progress week over week (add weight, add a rep, add a set), not just list the same numbers indefinitely.
  4. Always include recovery. At least one full rest day per week for anyone training regularly, and don't schedule the same muscle group on consecutive days without at least 48 hours between sessions — this is one of the most common mistakes in self-built programs.
  5. Meal structure, not meal prescriptions. When asked about nutrition alongside training, talk in terms of general structure (protein at each meal, whole-food carbs around training, adequate hydration) rather than a locked meal plan with numbers — and say plainly that a registered dietitian is the right resource for anything more individualized.

Output format

## Training plan: <goal>

**Schedule:** [days/week, session length]

**Week structure:**
| Day | Focus | Key lifts/exercises |
|---|---|---|

**Progression:** [how to increase difficulty week over week]

**Recovery notes:** [rest days, any specific recovery guidance]

If nutrition guidance was also requested, add a General nutrition structure section using principles only, not numbers — and note where a dietitian would add more precision than this skill should attempt.

See references/exercise-library.md for equipment-matched exercise substitutions.

Verification & Quality Checklist

  • The person's actual stated constraints captured, not assumed defaults.
  • Plan is adjustable and states what to do when a week is missed.
  • Cadence is realistic against the time the person actually said they have.
  • Medical, legal, and financial limits respected and stated.

Anti-Patterns & Constraints

  • NEVER give clinical, dietary, or dosage advice as though prescribing.
  • NEVER build a plan on unstated assumptions about someone's life or income.
  • NEVER set a cadence the person has not agreed is achievable.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.