agentleFS
BayramAnnakovBayramAnnakov/ai-personal-os-skills/skills/daily-log/SKILL.md

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

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
  1. Distinctive:

    Run a quick 5-minute daily check-in.

    line 12
  2. Very specific:

    Ask each question one at a time using AskUserQuestion.

    line 16
  3. Very specific:

    Create the notes/ directory in the current working directory if it does not exist.

    line 51
  4. Very specific:

    Write the file to notes/daily-log-YYYY-MM-DD.md with this format:

    line 52
  5. Very specific:

    If an achievements.md file exists in the current directory, update it:

    line 81
  6. Distinctive:

    Add an entry to the Activity Log table.

    line 83
  7. Very specific:

    After saving, count all notes/daily-log-*.md files.

    line 87
  8. Very specific:

    Read ALL daily-log files in notes/

    line 89
  9. Very specific:

    Read user-profile.md (if it exists)

    line 90
  10. Very specific:

    Add or update a ## Patterns From Daily Logs section at the end of user-profile.md

    line 96
  11. Distinctive:

    Keep it concise — 5-8 bullet points max.

    line 97
  12. Distinctive:

    After everything is saved, ask ONE final question:

    line 113
  13. Distinctive:

    If they choose to share:

    line 118
  14. Distinctive:

    If MCP is not connected or drafting fails, just print the message and say "Copy this to the group chat when you're ready"

    line 123
  15. Distinctive:

    If they skip, move on silently.

    line 125
  16. Distinctive:

    Do NOT turn this into a long conversation.

    line 127

“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.

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

/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

  1. Get today's date in YYYY-MM-DD format (run date +%Y-%m-%d via Bash).
  2. Create the notes/ directory in the current working directory if it does not exist.
  3. Write the file to notes/daily-log-YYYY-MM-DD.md with 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-*.md files 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...):

  1. Read ALL daily-log files in notes/
  2. Read user-profile.md (if it exists)
  3. 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?)
  4. Add or update a ## Patterns From Daily Logs section at the end of user-profile.md
  5. Keep it concise — 5-8 bullet points max. Replace the previous version, don't append.
  6. 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 meeting

Optional: 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:

  1. Compose a short one-liner (streak count + vitals, or their custom text)
  2. Show the exact message to the user
  3. Save it as a draft in the course Telegram group "edu-ai-productivity-s2" using save_draft via MCP (do NOT send — draft only)
  4. Tell them: "Draft saved to the group chat. Open it in Telegram to review and send."
  5. 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.

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.