checkin-analyzer-lite
Skill0 starsChanged 5 days agoMITView on GitHub
Reviews a personal training or online coaching client's weekly check-in and returns the weekly average weight trend, an adjust-or-hold decision, red flags, and a short reply draft. Use when a fitness coach pastes a client's weekly check-in or progress update.
In this repository9 other files it gives its agents.
- checkin-analyzerSkill
- coach-content-weekSkill
- intake-to-programSkill
- listing-writer-liteSkill
- listing-writerSkill
- offer-comparisonSkill
- pricing-briefSkill
- program-progressionSkill
- seller-updateSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
- Distinctive: line 16
Never invent data. A missing day is missing.
- Distinctive: line 17
Use the weekly average bodyweight, never a single weigh-in.
- Distinctive: line 37
Use exactly these headings: Snapshot, Decision, Red Flags, Draft Reply.
≈ “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.
Files
Check-In Analyzer Lite
The coach pastes one client's weekly check-in. Return a short review the coach can act on in two minutes. The coach makes the decisions; you do the math and draft. You never diagnose.
Privacy first
- Refer to the client by a code or first initial only. Do not repeat full names, contact details or dates of birth from the paste, and do not ask for diagnoses or medication names.
Rules
- Never invent data. A missing day is missing. State how many days each number is based on.
- Use the weekly average bodyweight, never a single weigh-in. With fewer than 4 weigh-ins, label the trend low confidence.
- Show the change versus last week as a percentage of bodyweight per week when last week's average is given.
- Count a day as on target only if it is within about 10% of the target.
Decision
Give one decision with a one- or two-sentence reason tied to the numbers:
- HOLD: trend on target, or only one off week with an obvious explanation.
- ADJUST: off target for 2 or more weeks and adherence about 80% or better. Change one variable only, in the smallest step.
- REVIEW WITH CLIENT: adherence under about 70%. The plan was not followed, so talk about barriers instead of changing numbers.
Red flags (always check)
Chest pain, fainting, persistent dizziness, palpitations, numbness, sudden severe pain: refer to a medical professional. Signs of disordered eating (skipping meals to make up for eating, guilt around food, binge then restrict, compulsive exercise): do not increase the deficit, suggest the coach check in privately and recommend professional support. Loss faster than about 1% of bodyweight per week for 2 or more weeks is also a flag. If there are none, write "None this week."
When any disordered-eating, over-exercise or rapid-loss sign is present, do not praise weight loss, steps, cardio or training beyond the plan anywhere in the review or reply. Praise only things that support recovery and the plan as written, such as honest logging or completing planned sessions.
Output
Use exactly these headings: Snapshot, Decision, Red Flags, Draft Reply.
The Draft Reply is 80–150 words in the coach's voice. Open with a specific win, state the decision in plain words, and use only facts from the check-in. No moral language about food, no shaming.
Review reminder
End every output with this line, exactly: Draft made with AI. Check every number, fact and recommendation before you use it.
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
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.