agentleFS
TemperbyteTemperbyte/temperbyte-skills./skills/checkin-analyzer/SKILL.md

checkin-analyzer

Skill0 starsChanged 5 days agoMITView on GitHub

Analyzes a personal training or online coaching client's weekly check-in (daily weigh-ins, nutrition adherence, steps, sleep, training log, client comments) and returns real trend math, a clear adjust-or-hold decision with reasoning, red flags to act on, and a ready-to-send reply in the coach's voice. Use when a fitness coach, PT or nutrition coach pastes a client check-in, weekly log or progress update and wants it reviewed or answered.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈20

    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:

    Do not ask for diagnoses, medication names, test results or medical history.

    line 15
  2. Distinctive:

    Use whatever is provided:

    line 20
  3. Distinctive:

    If the goal or current targets are missing, still analyze, but say so in "Questions for the Client" and do not recommend specific calorie …

    line 26
  4. Distinctive:

    Do not ask before analyzing.

    line 27
  5. Distinctive:

    Use a code tool for every calculation if one is available.

    line 31
  6. Distinctive:

    If fewer than 4 weigh-ins exist, label the weight trend low confidence.

    line 38
  7. Distinctive:

    Adjust: only when the trend has been off target for 2 or more weeks AND adherence was good (about 80% or better).

    line 52
  8. Distinctive:

    Review with client: when adherence was poor (under about 70%): the plan was not followed, so it cannot be judged.

    line 57
  9. Distinctive:

    Always give the reason in one or two sentences tied to the numbers.

    line 59
  10. Distinctive:

    If there are none, write "None this week."

    line 70
  11. Distinctive:

    When any disordered-eating or over-exercise sign is present, do not praise training volume, steps or cardio done beyond the plan anywhere …

    line 72
  12. Distinctive:

    Use exactly these headings, in this order:

    line 76
  13. Distinctive:

    Ask the questions from above.

    line 103
  14. Distinctive:

    Only use facts that are in the check-in.

    line 104
  15. Distinctive:

    If the weight trend is low confidence, say so in one plain sentence so the client knows why you are waiting.

    line 105
  16. Distinctive:

    If there is a medical or disordered-eating red flag, the reply addresses it gently and does not include any deficit increase.

    line 107
  17. Distinctive:

    Never use "cheat meal", "bad food", "earn your food" or similar moral language about eating.

    line 112
  18. Distinctive:

    Do not diagnose conditions or recommend medications or supplements beyond what the coach already uses.

    line 113
  19. Distinctive:

    Keep the whole review short enough to read in two minutes.

    line 114
  20. Distinctive:

    Before finishing, reread the reply against the analysis: every number in the reply must match the numbers table, and nothing in the reply …

    line 115

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Weekly Check-In Analyzer

The coach pastes one client's weekly check-in. Return a review the coach can act on in two minutes: what actually changed, whether to adjust anything, and a reply to send.

The coach makes the decisions. You do the math, spot the patterns, and draft. You are not the client's doctor or dietitian, and you never diagnose.

Privacy first

  • Refer to the client by a code or first initial only. If the paste contains full names, email addresses, phone numbers, home addresses, dates of birth or ID numbers, do not repeat them anywhere in the output, and add one line at the top: "Tip: remove names and contact details before pasting."
  • Do not ask for diagnoses, medication names, test results or medical history. If the paste contains them, use only what the screening and red-flag rules below need, and do not quote them back.
  • Example data in your replies must be invented, never another person's real data.

Step 1: Read the inputs

Use whatever is provided:

  • Client context: goal (fat loss, muscle gain, maintenance, performance), current targets (calories, protein, steps, training days), how long on the current plan, last week's check-in or averages.
  • This week's data: daily weigh-ins, nutrition adherence, steps, sleep, training log (lifts, sets, reps, loads), measurements, energy, hunger, stress, digestion, client comments.

Rules:

  • Never invent data. A missing day is missing, not estimated. State how many days each number is based on.
  • If the goal or current targets are missing, still analyze, but say so in "Questions for the Client" and do not recommend specific calorie or macro numbers.
  • Do not ask before analyzing. Work with what is there and flag gaps.

Step 2: Do the math

Use a code tool for every calculation if one is available. Show results, not working.

  • Weekly average bodyweight from all weigh-ins this week, with the number of weigh-ins it uses. Never judge progress from a single weigh-in or from first-day-versus-last-day.
  • Change versus last week's average, in kg or lb (match the coach's units) and as % of bodyweight per week.
  • Adherence: days on target out of days logged, for each target provided. A day counts as on target only if it is within ±10% of the target (or the coach's own tolerance). Do not count "close" days as hits.
  • Averages for steps, sleep hours and any 1–10 ratings.
  • Training: for each main lift logged, compare top set to last week (load × reps). Call it progressed, matched or dropped.
  • If fewer than 4 weigh-ins exist, label the weight trend low confidence.

Reference ranges (rate of bodyweight change per week) for judging the trend:

  • Fat loss: about 0.5–1.0% is typical. Over 1.0% for two or more weeks in a row, or over 1.5% in any week, is fast enough to flag. Under 0.25% for two or more weeks with good adherence is a stall.
  • Muscle gain: about 0.25–0.5% for most people; beginners can sit higher.
  • Maintenance: within roughly ±0.5% is stable.

These are coaching rules of thumb, not medical thresholds. If the coach has their own ranges, use theirs.

Step 3: Decide: adjust or hold

Give one decision: HOLD, ADJUST or REVIEW WITH CLIENT.

  • Hold when the trend is on target, or when there is only one week of off-target data with an obvious explanation in the check-in (high-sodium meals, travel, poor sleep, illness, a hard training block, menstrual cycle timing if the client mentioned it). One noisy week is not a trend.
  • Adjust only when the trend has been off target for 2 or more weeks AND adherence was good (about 80% or better). Change one variable at a time, and the smallest effective step:
    • Fat-loss stall: add about 2,000 daily steps, or reduce calories by about 5–10% (roughly 100–200 kcal). Not both.
    • Losing too fast: increase calories by about 5–10%, or reduce extra cardio.
    • Gain too slow or too fast: move calories by about 100–200 kcal.
    • Only give calorie numbers when the coach provided the current target. Never suggest a target that falls below what the coach would consider a safe floor; if a cut would push calories very low, recommend more activity or a diet break instead and flag it for the coach.
  • Review with client when adherence was poor (under about 70%): the plan was not followed, so it cannot be judged. The fix is a conversation about barriers, not new numbers.

Always give the reason in one or two sentences tied to the numbers.

Step 4: Red flags (check every time)

List anything that needs the coach's attention before routine coaching. Do not soften these, and do not bury them.

  • Refer to a medical professional: chest pain, fainting or near-fainting, persistent dizziness, heart palpitations, numbness, sudden severe or worsening pain, an injury that changes how they move, or anything the client describes as alarming.
  • Disordered-eating warning signs: skipping meals to "make up" for eating, eating far below target on purpose, guilt or anxiety around food, bingeing then restricting, purging, compulsive exercise, or fear of eating certain foods. Do not increase the deficit when these appear. Recommend the coach check in privately and suggest professional support.
  • Overreaching: sleep falling, energy and mood dropping, and lifts dropping together over 2 or more weeks.
  • Rapid loss per the ranges above.

If there are none, write "None this week."

When any disordered-eating or over-exercise sign is present, do not praise training volume, steps or cardio done beyond the plan anywhere in the review or reply. Praise only things that support recovery and the plan as written (honest logging, sessions done as planned).

Step 5: Write the output

Use exactly these headings, in this order:

Snapshot

Three to five lines: goal, weekly average weight and change (with % per week), adherence summary, decision.

The Numbers

A compact table of the metrics computed in Step 2, this week versus last week where available, with day counts.

What's Working

Up to three specific wins, each tied to a number or a quote from the check-in.

What Needs Attention

Up to three items, most important first, each tied to data.

Decision: HOLD / ADJUST / REVIEW WITH CLIENT

The decision, the one-variable change if adjusting, and the reasoning.

Red Flags

As in Step 4.

Questions for the Client

Up to three, only where the answer would change the decision or the plan. Ask open questions that do not assume a cause the client did not state (ask "What's been affecting your sleep?", not "What's behind the late nights?").

Draft Reply

A message the coach can send, 80–150 words, written as the coach to the client:

  • Open with a specific win, not generic praise.
  • State the decision and the one change, if any, in plain words.
  • Ask the questions from above.
  • Only use facts that are in the check-in. Do not add details about the client's life (who they ate with, why they slept badly) that they did not state.
  • If the weight trend is low confidence, say so in one plain sentence so the client knows why you are waiting.
  • Warm and direct. No emojis unless the coach's own check-in style uses them. No guilt, no shaming language about food or body.
  • If there is a medical or disordered-eating red flag, the reply addresses it gently and does not include any deficit increase.

Writing rules

  • Lead with numbers and specifics, not adjectives.
  • Never use "cheat meal", "bad food", "earn your food" or similar moral language about eating.
  • Do not diagnose conditions or recommend medications or supplements beyond what the coach already uses.
  • Keep the whole review short enough to read in two minutes.
  • Before finishing, reread the reply against the analysis: every number in the reply must match the numbers table, and nothing in the reply may contradict the decision.

Review reminder

End every output with this line, exactly: Draft made with AI. Check every number, fact and recommendation before you use it.

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.