log
Skill0 starsChanged 6 months agoMITView on GitHub
Record anything that happens. Meals (text or photo), weight, body measurements (waist/hip/thigh/neck/arm), workouts (sets/reps/weight/duration/RPE), symptoms (headache, gut issues, energy crash, mood, skin, sleep quality), beverages (chai, coffee, water, alcohol), supplements taken or skipped. Invoke when the user says "had X", "ate X", "for breakfast/lunch/dinner I had", "weighed X", "weight is X", "did X workout", "feeling Y", "headache", "tired", "energy crashed", "had 3 chais", "had 2 cups coffee", "took my B12", "skipped omega-3", "log this", "log X", "/log X", drops a food photo, drops a body composition photo, or otherwise reports something to record. Updates today's wiki/logs/YYYY/MM/DD.md, grows wiki/food-library/ when a new food appears, and returns remaining macros for the day after meal logs.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- jsuchet/jonathan-skills-labtheir own version, first seen Nov 16, 2026
- thensls/nsls-personal-toolkittheir own version, first seen Nov 12, 2026
- mehboobali98/rmine-skillstheir own version, first seen Nov 6, 2026
- myowinthein/claude-helmtheir own version, first seen Nov 1, 2026
- tjmode/koovitheir own version, first seen Nov 1, 2026
- rmarji/chiron-counciltheir own version, first seen Nov 1, 2026
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- regent-vcs/re_gent★ 809same name
- dtiger1889-ops/claude-harness-toolbox★ 33same name
- swastij/claude-log-skill★ 16same name
- gyroid-eth/orrery-telemetry★ 12same name
- foxrun-ai/foxrun★ 6same name
- bonez-io/re_gent★ 4same name
- Valmor-R-Reichel/SGM★ 4same name
- aniklavida/agent-assemble★ 1same name
- jsuchet/jonathan-skills-lab★ 1same name
- llewellynvz/claude-code-timestamps★ 1same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 12 are distinctive, and 12 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
If today's daily log file wiki/logs/YYYY/MM/DD.md does not exist, create it from the template in CLAUDE.md.
- Very specific: line 16
If wiki/profile/identity.md is empty, the user is not onboarded.
- Very specific: line 25
Look up macros in this order: a.
- Very specific: line 33
If a new dish appeared (not in food-library), create or extend wiki/food-library/home/<slug>.md with: macros, typical portion, source …
- Distinctive: line 43
Ask ONE calibration question only:
- Distinctive: line 46
After user answers, compute macros with explicit confidence band.
- Very specific: line 60
Update hot.md with current weight + MA.
- Very specific: line 69
If tape measurements are provided, also append [date, waist_cm, hip_cm, whr] tuple to the waist_log array in wiki/profile/anthropometry.md …
- Very specific: line 70
If photo: file as raw/photos/body/YYYY-MM-{front,side,back}.jpg.
- Distinctive: line 71
If both tape + photo provided, store together in same row.
- Very specific: line 79
If resistance training: log to wiki/plans/current-week-workouts.md (or to a dedicated workout log if user prefers detailed PR tracking.
- Distinctive: line 81
If recovery context known (Oura), reflect whether the planned intensity matched recovery.
- Very specific: line 89
If recurring (3+ times in 14 days), note in wiki/reviews/correlations/ and consider invoking review correlation sub-flow on next session.
- Distinctive: line 96
Update Beverages section of today's log.
- Distinctive: line 98
Add to Daily Totals if material.
- Distinctive: line 105
Update Supplements section of today's log (or add the section if not yet in template).
- Distinctive: line 107
If skipped, note. If pattern emerges (skipped >3x/week), surface in next monthly checkin.
- Very specific: line 108
If new supplement: prompt to add to wiki/profile/supplements.md with brand/dose/timing.
- Distinctive: line 113
When the user signals end of day ("done eating", "closing out the day", evening reflection complete, or at midnight on the next session), …
- Distinctive: line 115
Write the "Daily totals" section with kcal_actual / kcal_target, protein_actual / target, fiber, sodium estimate.
- Distinctive: line 116
Write the YAML frontmatter block at the top of the file per the Frontmatter contract in CLAUDE.md:
- Distinctive: line 135
After every log event:
- Very specific: line 138
If a new food was added to food-library, update index.md.
- Very specific: line 141
If the event is a weigh-in or body-comp measurement, the relevant frontmatter block in wiki/profile/anthropometry.md was updated in the …
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Log skill
Record any user event into the right wiki location.
Pre-flight
If today's daily log file wiki/logs/YYYY/MM/DD.md does not exist, create it from the template in CLAUDE.md.
Compute today's date in IST (Asia/Kolkata).
If wiki/profile/identity.md is empty, the user is not onboarded. Run checkin first (onboarding mode) before any log.
Sub-flows
Meal log (text)
User: "had 2 phulkas, dal, bhindi, 1 cup curd"
- Parse items + portions.
- Look up macros in this order:
a.
wiki/food-library/home/<dish>.md(your stored portion-aware entry, if exists) b. IFCT 2017 (decompose composite dishes into raw ingredients) c. INDB recipes for cooked dishes d. Restaurant official PDF for branded items (link in food-library entry) - Compute kcal + P/C/F + fiber + sodium estimate.
- Append to today's log under appropriate meal section. Infer slot from current time IST or user statement.
- Update Daily Totals.
- If a new dish appeared (not in food-library), create or extend
wiki/food-library/home/<slug>.mdwith: macros, typical portion, source citation, when first seen. - Return: "Logged. ~XXX kcal, Yg protein. Remaining today: ZZZ kcal, Wg protein."
- Append to
log.md:## [DATE TIME] meal-log | <slot>: <summary>, ~XXX kcal.
Meal log (photo)
User drops a photo (in chat or to raw/photos/).
- Identify dishes from the image. Be specific (not "rice" but "looks like jeera rice or basmati, ~1.5 cups").
- Estimate portions. Look for plate diameter, bowl size, hand if visible.
- Ask ONE calibration question only:
- Best: "Can you tell me the weight in grams of [item]?" if a kitchen scale is plausible.
- Else: "Plate looks ~25cm. Was the dal a half-cup or full cup?"
- After user answers, compute macros with explicit confidence band.
- Save photo to
raw/photos/YYYY-MM-DD-HHMM-<slot>.jpgif not already there. - Append to log with confidence: "logged ~480 kcal (range 380 to 580), 18g P, photo at raw/photos/..."
- On the first photo of any session, remind: "Single-meal photos are ±35 to 40% on calories; trends matter more than precision."
- Append to
log.md:## [DATE TIME] meal-log | <slot> from photo: ~XXX kcal (range YY-ZZ).
Weight log
User: "weighed 78.4 this morning" or "weight is 78.4"
- Append timestamped row to
wiki/profile/anthropometry.mdbody table. - Also append
[date, kg, note]tuple to theweight_logarray in that file's YAML frontmatter (per Frontmatter contract in CLAUDE.md). Body table and frontmatter must stay in lockstep. - Recompute 7-day moving average.
- Compare to last week's MA, flag direction (down / flat / up) vs goal.
- Update
hot.mdwith current weight + MA. - Append to
log.md:## [DATE TIME] weigh | 78.4 kg, 7d MA: X.X (↓/→/↑). - Return: "Logged. 7-day MA is X.X kg, trending [↓/→/↑] vs last week."
Body measurements
User: "waist 92cm, hip 102cm" or drops a body comp photo to raw/photos/body/
- Append timestamped row to
wiki/biomarkers/body-composition.md. - If tape measurements are provided, also append
[date, waist_cm, hip_cm, whr]tuple to thewaist_logarray inwiki/profile/anthropometry.mdfrontmatter (per Frontmatter contract). - If photo: file as
raw/photos/body/YYYY-MM-{front,side,back}.jpg; reference in body-composition.md. - If both tape + photo provided, store together in same row.
- Append to
log.md:## [DATE TIME] body-comp | waist X, hip Y, photo Z.
Workout log
User: "did 3x8 squats at 60kg, 3x10 bench at 40kg, 3x12 rows at 30kg" or "walked 5km in 50 min" or "30 min Surya Namaskar"
- Append to today's log under Movement section.
- If resistance training: log to
wiki/plans/current-week-workouts.md(or to a dedicated workout log if user prefers detailed PR tracking; ask once, save preference inwiki/profile/preferences.md). - Compare to previous session of same exercise. Note PR or stall.
- If recovery context known (Oura), reflect whether the planned intensity matched recovery.
- Append to
log.md:## [DATE TIME] workout-log | <type>: <summary>.
Symptom log
User: "headache since lunch" or "energy crashed at 3pm" or "bloated after dal" or "great mood today"
- Append to today's log under Symptoms section. Include time of day if relevant.
- If recurring (3+ times in 14 days), note in
wiki/reviews/correlations/and consider invokingreviewcorrelation sub-flow on next session. - Append to
log.md:## [DATE TIME] symptom | <text>.
Beverage log
User: "had 4 chais today" or "2 cups coffee" or "3 glasses water" or "2 pegs whisky"
- Update Beverages section of today's log.
- Compute hidden calories (sugar chai ~60 kcal each with 2 tsp sugar, +30 with milk; black coffee ~5; alcohol per peg ~80).
- Add to Daily Totals if material.
- Append to
log.md:## [DATE TIME] beverage | <summary>.
Supplement log
User: "took my B12 and Vit D" or "skipped omega-3" or "started new magnesium"
- Update Supplements section of today's log (or add the section if not yet in template).
- Cross-reference
wiki/profile/supplements.mdfor what's expected. - If skipped, note. If pattern emerges (skipped >3x/week), surface in next monthly checkin.
- If new supplement: prompt to add to
wiki/profile/supplements.mdwith brand/dose/timing. - Append to
log.md:## [DATE TIME] supplement | <taken/skipped/added>.
End-of-day close
When the user signals end of day ("done eating", "closing out the day", evening reflection complete, or at midnight on the next session), finalize today's daily log:
- Write the "Daily totals" section with kcal_actual / kcal_target, protein_actual / target, fiber, sodium estimate.
- Write the YAML frontmatter block at the top of the file per the Frontmatter contract in CLAUDE.md:
This block is what powers the Obsidian dashboard's "Today" panel and 30-day adherence view. Without it, the day shows as "no data."--- date: YYYY-MM-DD kcal_actual: <int> protein_g_actual: <int> fiber_g_actual: <int> weight_kg: <float> # only if weighed today energy_score: <1-10> # if logged sleep_hours: <float> # if logged sleep_score: <1-10> # if logged workout: <true|false> --- - Append to
log.md:## [DATE TIME] note | day closed, <one-line summary>.
Bookkeeping (always)
After every log event:
- Today's daily log file is updated (or created from template).
- Append to
log.mdwith the rightkind. - If a new food was added to food-library, update
index.md. - Refresh
hot.mdonly if event is materially recent context (new weight, new PR, recurring symptom, biomarker-relevant beverage pattern). - Cross-link related wiki pages (e.g., a Saoji entry → vidarbha-cuisine.md when that exists).
- If the event is a weigh-in or body-comp measurement, the relevant frontmatter block in
wiki/profile/anthropometry.mdwas updated in the same edit (see Weight log / Body measurements sub-flows).
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.

