agentleFS
jaredhhawkjaredhhawk/claude-skills/skills/day/SKILL.md

day

Skill0 starsChanged 8 months agoMITView on GitHub

Daily productivity check-in. Logs your top 3, sleep, energy, mood, and activity for the day.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. alxyrgin/health-os★ 38same name
    2. ksdisch/claude-config★ 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 repository14 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

31 rules. About 0 are common, 20 are distinctive, and 11 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.

  • 11

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If it doesn't exist, create it using the template below

    line 13
  2. Very specific:

    Check yesterday's unfinished items: Read yesterday's daily note (YYYY-MM-DD.md for the previous day)

    line 17
  3. Very specific:

    If any exist, show them and ask: "You left X things unfinished yesterday — carry any forward?

    line 19
  4. Very specific:

    Read 99_System/Weekly Reviews/YYYY-WXX-Plan.md (e.g., 2026-W10-Plan.md)

    line 26
  5. Distinctive:

    If file not found: skip silently

    line 30
  6. Distinctive:

    Ask: "What's your top 3 for today?" (append to any carried-forward items)

    line 31
  7. Distinctive:

    Ask: "How'd you sleep? (hours)"

    line 32
  8. Very specific:

    Check task inbox: Read 01_Inbox/01_TASKS.md and look for unformatted items

    line 40
  9. Distinctive:

    If found (max 5 items):

    line 42
  10. Very specific:

    If yes, show first 3-5 items and for each ask: "Add to today?

    line 46
  11. Distinctive:

    Keep it fast: if user says "no" to triage, skip entirely

    line 51
  12. Very specific:

    Check explore queue: Read 01_Inbox/00_EXPLORE.md and count unprocessed items

    line 52
  13. Distinctive:

    If items exist: "You have X items in your explore queue.

    line 53
  14. Very specific:

    If yes: Process 1-2 items using /explore skill behavior (fetch, summarize, categorize, append)

    line 54
  15. Very specific:

    Check universal inbox: Read 01_Inbox/00_INBOX.md and count items in Inbox section

    line 56
  16. Distinctive:

    If items exist: "You have X items in inbox.

    line 57
  17. Very specific:

    If yes: Process 2-3 items using /triage skill behavior

    line 58
  18. Distinctive:

    Keep it fast - if user says no, skip entirely

    line 59
  19. Distinctive:

    Ask: "What moved today?"

    line 62
  20. Very specific:

    Ask: "Energy level? (1-3: low/med/high)"

    line 64
  21. Distinctive:

    Ask: "Any vices to log?"

    line 66
  22. Distinctive:

    Update the "What Happened" section

    line 67
  23. Distinctive:

    Check off completed Top 3 items based on what they report

    line 72
  24. Distinctive:

    Read last 7 daily notes to check patterns

    line 75
  25. Distinctive:

    If job outreach count is low, mention it: "You're X/15 on outreach this week"

    line 77
  26. Distinctive:

    If energy has been consistently low, note it

    line 78
  27. Distinctive:

    When creating or updating daily notes:

    line 119
  28. Very specific:

    Related line: Always link to [[Active Workstreams]]

    line 122
  29. Distinctive:

    Project links: When user mentions projects in Top 3 or What Happened, link to them:

    line 123
  30. Distinctive:

    Don't ask unnecessary questions

    line 146
  31. Distinctive:

    If they give terse answers, work with them

    line 147

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

/day - Daily Check-in

You are helping the user with their daily productivity check-in. This command works differently based on time of day.

Behavior

  1. Check if today's daily note exists at 99_System/Daily Notes/YYYY-MM-DD.md
  2. If it doesn't exist, create it using the template below
  3. Based on time of day, ask appropriate questions:

Morning (before 12pm)

  • Check yesterday's unfinished items: Read yesterday's daily note (YYYY-MM-DD.md for the previous day)
    • Find any Top 3 items still unchecked (- [ ])
    • If any exist, show them and ask: "You left X things unfinished yesterday — carry any forward? (y/n/pick)"
      • y → add all to today's Top 3
      • pick → show list, user selects which ones
      • n → skip
    • Pre-populate today's Top 3 with any carried-forward items before asking what else to add
  • Show week plan context:
    • Calculate current ISO week number from today's date (e.g., Mar 2 = W10)
    • Read 99_System/Weekly Reviews/YYYY-WXX-Plan.md (e.g., 2026-W10-Plan.md)
    • Find today's day section by matching day name (e.g., ### Tue Mar 3)
    • Show one line: Week plan: [Day — Theme] | Anchor: [anchor text]
    • Scan the ## Non-Negotiables section for unchecked - [ ] items; if any are unrelated to today's carry-forwards and it's Wed or later, flag: "Non-negotiable still open: [item]"
    • If file not found: skip silently
  • Ask: "What's your top 3 for today?" (append to any carried-forward items)
  • Ask: "How'd you sleep? (hours)"
  • Ask: "Exercise yesterday? (y/n)"
  • Ask: "Drinks last night? (y/n)"
  • Fill in the Top 3 section and sleep frontmatter
  • Update habit tracking in Goals.md and daily note frontmatter
  • If drinks on Mon-Thu, remind: "Week challenge: No drinks Mon-Thu"
  • Remind them of any active project priorities from [[00_Dashboard/Active Workstreams]]
  • Flag active optimization suggestions if relevant (e.g., "Reminder: Pair apps with outreach today")
  • Check task inbox: Read 01_Inbox/01_TASKS.md and look for unformatted items
    • Find lines without checkboxes that look like tasks (not URLs, headers, or dataview)
    • If found (max 5 items):
      "You have X items in your task inbox. Quick triage?"
    • If yes, show first 3-5 items and for each ask: "Add to today? (y/n/skip)"
      • y → Add #today tag, ensure checkbox formatted
      • n → Just ensure checkbox formatted, leave in inbox
      • skip → Leave as-is
    • Auto-save formatted file after triage
    • Keep it fast: if user says "no" to triage, skip entirely
  • Check explore queue: Read 01_Inbox/00_EXPLORE.md and count unprocessed items
    • If items exist: "You have X items in your explore queue. Process 1-2 now? (y/n)"
    • If yes: Process 1-2 items using /explore skill behavior (fetch, summarize, categorize, append)
    • Output brief verbal summary of what was learned
  • Check universal inbox: Read 01_Inbox/00_INBOX.md and count items in Inbox section
    • If items exist: "You have X items in inbox. Triage now? (y/n)"
    • If yes: Process 2-3 items using /triage skill behavior
    • Keep it fast - if user says no, skip entirely

Afternoon/Evening (after 12pm)

  • Ask: "What moved today?"
  • Detect goal-aligned actions: Count applications, outreach, PM interviews, gig outreach, MVP hours
  • Ask: "Energy level? (1-3: low/med/high)"
  • Ask: "Mood? (1-3)"
  • Ask: "Any vices to log?"
  • Update the "What Happened" section
  • Fill in energy/mood/vices frontmatter
  • Update daily note frontmatter with goal_actions field
  • Calculate energy allocation: "Today: PM 60%, Gig 20%, SaaS 20%" (vs targets)
  • Flag if energy allocation is off: "PM got 30% energy today (target: 60%)"
  • Check off completed Top 3 items based on what they report

Pattern Checks (always)

  • Read last 7 daily notes to check patterns
  • Read Goals.md to check weekly targets vs actuals
  • If job outreach count is low, mention it: "You're X/15 on outreach this week"
  • If energy has been consistently low, note it
  • If 2+ goals are off-track, flag: "2 goals behind this week. Run /goals for details"
  • If habit streaks broken, remind: "No drinks Mon-Thu streak: 0 days (target: 4)"

Daily Note Template

---
date: YYYY-MM-DD
energy:
mood:
sleep:
vices:
habits:
  exercise: false
  drinks_last_night: false
goal_actions:
  applications: 0
  outreach: 0
  pm_interviews: 0
  mvp_hours: 0
---
Nav: [[YYYY-MM-DD|< Prev]] | [[YYYY-MM-DD|Next >]]
Related: [[Active Workstreams]]

# Day Name, Month D

## Top 3 Today
- [ ]
- [ ]
- [ ]

## What Happened
-

## Notes

Linking Rules

When creating or updating daily notes:

  1. Nav links: Include prev/next day links (only if those files exist)
  2. Related line: Always link to [[Active Workstreams]]
  3. Project links: When user mentions projects in Top 3 or What Happened, link to them:
    • "Legata prep" → "[[Legata Index|Legata]] prep"
    • "Job search outreach" → "[[P - Job Search Strategic Project (Full Version)|Job Search]] outreach"
    • "College scholarships" → "[[P - College Scholarships|College Scholarships]]"
  4. Domain links: Link to relevant domains when appropriate:
    • Health/exercise → [[D - Health and Fitness]]
    • Family items → [[D - Family]]
    • AI/tech learning → [[D - Tech & AI]]

Frontmatter Values

  • energy: 1-5 scale (1=crashed, 2=low, 3=medium, 4=good, 5=peak)
  • mood: 1-5 scale (1=bad, 2=low, 3=neutral, 4=good, 5=great)
  • sleep: decimal hours (e.g., 6.5, 7, 8)
  • vices: shorthand notation (e.g., "none", "beer1", "weed1", "beer2 weed1")

File Location

Daily notes go in: 99_System/Daily Notes/YYYY-MM-DD.md

Conversation Style

  • Brief, no fluff
  • Don't ask unnecessary questions
  • If they give terse answers, work with them
  • End with a quick summary of what was logged

Example Interactions

Morning:

Claude: Morning. Yesterday you left 1 item unfinished: "Check in on College Scholarships". Carry forward? (y/n)
User: y
Claude: Added. What else for today's top 3?
User: /scout automation, 2 outreaches
Claude: How'd you sleep?
User: 7 hours
Claude: Exercise yesterday?
User: n
Claude: Drinks last night?
User: n
Claude: Logged. Top 3: scout automation, 2 outreaches, College Scholarships (carried). Active projects: Job Search, Legata. Check back tonight.

Evening:

Claude: End of day. What moved?
User: Legata call done, 1 outreach, skipped exercise
Claude: Energy today?
User: 2
Claude: Mood?
User: 2
Claude: Any vices?
User: beer last night
Claude: Logged: 2/3 done (Legata, 1 outreach). Energy 2, mood 2, vices: beer1.

Goal tracking: 0 apps, 1 outreach (Legata = PM goal). Energy allocation: PM 80%, other 20%.
This week: 3/15 outreaches, 0/12 apps.

Pattern note: Drinks last night → energy 2 today (consistent pattern).

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.