daily-log
Skill19 starsChanged 8 months agoMITView on GitHub
Daily 5-minute energy-mood-focus journal. Creates structured daily logs in notes/ folder. Run this every day to build your personal data foundation for Week 2's Knowledge OS.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Bishal-Raj-Parajuli/work-loggertheir own version, first seen Nov 1, 2026
- wesen/skillstheir own version, first seen Oct 25, 2026
- aidvgg/operator-ostheir own version, first seen Oct 17, 2026
- kingluminance/claude-skillstheir own version, first seen Oct 11, 2026
- JAEKWON0316/cosmos-flywheeltheir own version, first seen Jul 22, 2026
- Dqz00116/skill-libtheir own version, first seen Apr 19, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Dqz00116/skill-lib★ 22same name
- aidvgg/operator-os★ 4same name
- wesen/skills★ 4same name
- Bishal-Raj-Parajuli/work-logger★ 0same name
- JAEKWON0316/cosmos-flywheel★ 0same name
- kingluminance/claude-skills★ 0same name
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.
In this repository5 other files it gives its agents.
- atomizeSkill
- cos-reviewSkill
- linkedin-research-postSkill
- ai-personal-os-onboardingSkill
- slide-inspectorSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 8 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run a quick 5-minute daily check-in.
- Very specific: line 16
Ask each question one at a time using AskUserQuestion.
- Very specific: line 51
Create the notes/ directory in the current working directory if it does not exist.
- Very specific: line 52
Write the file to notes/daily-log-YYYY-MM-DD.md with this format:
- Very specific: line 81
If an achievements.md file exists in the current directory, update it:
- Distinctive: line 83
Add an entry to the Activity Log table.
- Very specific: line 87
After saving, count all notes/daily-log-*.md files.
- Very specific: line 89
Read ALL daily-log files in notes/
- Very specific: line 90
Read user-profile.md (if it exists)
- Very specific: line 96
Add or update a ## Patterns From Daily Logs section at the end of user-profile.md
- Distinctive: line 97
Keep it concise — 5-8 bullet points max.
- Distinctive: line 113
After everything is saved, ask ONE final question:
- Distinctive: line 118
If they choose to share:
- Distinctive: line 123
If MCP is not connected or drafting fails, just print the message and say "Copy this to the group chat when you're ready"
- Distinctive: line 125
If they skip, move on silently.
- Distinctive: line 127
Do NOT turn this into a long conversation.
“Common” is measured: kept by at least 6 in 10 of the 4 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
/daily-log — Daily Journal
Run a quick 5-minute daily check-in. Ask 6 questions, save a structured note.
Interview Flow
Ask each question one at a time using AskUserQuestion. Keep it brisk and friendly.
Question 1: Energy
- Question: "How's your energy today?"
- Options:
["1-3 (Low)", "4-5 (Below average)", "6-7 (Good)", "8-10 (Great)"] - Map the answer to a number: Low=2, Below average=5, Good=7, Great=9
Question 2: Focus
- Question: "How well could you concentrate today?"
- Options:
["1-3 (Low)", "4-5 (Below average)", "6-7 (Good)", "8-10 (Great)"] - Map the answer to a number: Low=2, Below average=5, Good=7, Great=9
Question 3: Mood
- Question: "Overall mood?"
- Options:
["1-3 (Low)", "4-5 (Below average)", "6-7 (Good)", "8-10 (Great)"] - Map the answer to a number: Low=2, Below average=5, Good=7, Great=9
Question 4: Highlight
- Question: "What was the highlight of your day?"
- Options:
["Got something important done", "Had a great conversation", "Learned something new", "Other"] - Accept whatever they type — the options are just prompts.
Question 5: Blocker
- Question: "What slowed you down or frustrated you?"
- Options:
["Too many meetings", "Couldn't focus", "Stuck on a problem", "Nothing major", "Other"] - Accept whatever they type.
Question 6: Tomorrow
- Question: "What's the one thing you want to accomplish tomorrow?"
- Options:
["Finish a key task", "Start something new", "Clear my backlog", "Other"] - Accept whatever they type.
Save the Log
- Get today's date in YYYY-MM-DD format (run
date +%Y-%m-%dvia Bash). - Create the
notes/directory in the current working directory if it does not exist. - Write the file to
notes/daily-log-YYYY-MM-DD.mdwith this format:
# Daily Log — YYYY-MM-DD
## Vitals
- Energy: X/10
- Focus: X/10
- Mood: X/10
## Highlight
[their answer]
## Blocker
[their answer]
## Tomorrow
[their answer]
---
*Logged via /daily-log*After Saving
Print a one-line confirmation:
Logged! Energy X, Focus X, Mood X. See you tomorrow.
If an achievements.md file exists in the current directory, update it:
- Count
notes/daily-log-*.mdfiles to update streak and check achievement unlocks (First Log, Consistency, Week Warrior, Fortnight Force). - Add an entry to the Activity Log table.
Auto-Enrich: Pattern Analysis (every 3rd log)
After saving, count all notes/daily-log-*.md files. If the count is divisible by 3 (3, 6, 9, 12...):
- Read ALL daily-log files in
notes/ - Read
user-profile.md(if it exists) - Analyze patterns across all logs:
- Energy/focus/mood trends (which days are high/low?)
- Recurring blockers (what themes keep appearing?)
- Correlations (does high energy correlate with certain activities?)
- Productivity windows (any time-of-week patterns?)
- Add or update a
## Patterns From Daily Logssection at the end ofuser-profile.md - Keep it concise — 5-8 bullet points max. Replace the previous version, don't append.
- Tell the user: "Updated user-profile.md with patterns from X logs."
Example patterns section:
## Patterns From Daily Logs
*Auto-updated from 9 daily logs*
- Energy peaks mid-week (Tue-Thu avg 8, Mon avg 5)
- Most common blocker: context-switching between projects
- Focus improves on days with a clear "one thing" from previous log
- Mood correlates strongly with getting the highlight task done
- Best productivity window: mornings before first meetingOptional: Group Share
After everything is saved, ask ONE final question:
- Question: "Share something with the course group?"
- Options:
["Share streak + vibe (e.g. 'Day 5. Energy 8.')", "Write a custom message", "Skip — keep it private"]
If they choose to share:
- Compose a short one-liner (streak count + vitals, or their custom text)
- Show the exact message to the user
- Save it as a draft in the course Telegram group "edu-ai-productivity-s2" using
save_draftvia MCP (do NOT send — draft only) - Tell them: "Draft saved to the group chat. Open it in Telegram to review and send."
- If MCP is not connected or drafting fails, just print the message and say "Copy this to the group chat when you're ready"
If they skip, move on silently.
Do NOT turn this into a long conversation. The whole interaction should take under 5 minutes.
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.

