agentleFS
noahcostakesnoahcostakes/claudebrain-template/.claude/skills/daily-catchup/SKILL.md

daily-catchup

Skill0 starsChanged 5 months agoMITView on GitHub

Use when catching up on daily notes you missed — backfilling past daily journals, reconstructing days you skipped or forgot, or filling gaps in 50-daily/. Triggers on "catch up on my dailies", "I missed some days", "backfill last week". For PAST days only; today's note belongs to /daily.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user to pick which ones to fill.

    line 56
  2. Distinctive:

    Ask one combined recall question:

    line 69
  3. Very specific:

    Unfinished: ask /daily's three Evening questions (wins / log / carry-forward).

    line 72
  4. Distinctive:

    Wait for the answer before moving to the next day.

    line 74
  5. Very specific:

    Absent / Stub: create the note from templates/daily.md (create YYYY/MM/ folders if missing), substitute {{date}} and {{day-of-week}}.

    line 80
  6. Very specific:

    Both: add backfilled: <today's date> to the note's YAML frontmatter so it's honest that the note was reconstructed later, not written that …

    line 87
  7. Very specific:

    Use [[wikilinks]] whenever the answer names a project, person, or concept that has a vault note.

    line 89
  8. Very specific:

    Today is never in scope: Run /daily for today.

    line 93
  9. Distinctive:

    One day at a time: Don't collapse multiple days into one fuzzy answer — each date gets its own note from its own recollection.

    line 94
  10. Distinctive:

    Calendar is optional: If no Calendar MCP is connected, the per-day memory-jog step is simply skipped — nothing else changes.

    line 100

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Daily Catch-up Skill

What this does

Backfills the daily notes you missed. It's the past-days sibling of /daily: where /daily owns today, /daily-catchup reconstructs days you never wrote (or started and never finished). It scans a look-back window, shows you the gaps, lets you pick which to fill, then interviews you one day at a time and writes each note.

Relationship to /daily

This skill reuses /daily's machinery — read .claude/skills/daily/SKILL.md for the shared rules and don't restate them here:

  • Same path scheme: 50-daily/YYYY/MM/YYYY-MM-DD.md
  • Same note template: templates/daily.md
  • Same frontmatter, same [[wikilink]] rule, same never-fabricate rule
  • For Unfinished days (below), run /daily's Evening wrap-up verbatim.

Window & detection

Compute today's date. The window is the last N days (default 7), ending yesterday — today is never in scope; that's /daily's job. Override N at runtime ("catch up the last 14 days" → N=14).

For each date in the window, resolve 50-daily/YYYY/MM/YYYY-MM-DD.md and classify it by checking these conditions in order — the first match wins:

#ConditionCategoryAction
1File does not existAbsentCreate from template, retro-fill (below).
2File exists, Wins filledDoneSkip — don't show it.
3File exists, Top 3 emptyStub (morning never done)Treat like Absent — retro-fill.
4File exists, Top 3 filled, Wins emptyUnfinished (evening never done)Run /daily's Evening wrap-up.

The Wins-filled check comes before the Top 3 check on purpose: a note that already has Wins content is Done and must never be re-touched — even if it has no Top 3 section at all (e.g. an older backfilled recap). Checking Top 3 first would misread such a note as a Stub and destructively overwrite content you already wrote.

"Empty" vs "filled": a section is empty if it is absent, blank, or holds only the template placeholder (Top 3's bare 1./2./3., or whitespace). It is filled if it has any real content. When in doubt, treat the note as Done and leave it alone.

Present & select

List every Absent / Stub / Unfinished day, each with its weekday and category, e.g.:

Found 3 days to catch up in the last 7:

  • Sat 05-30 — absent
  • Sun 05-31 — absent
  • Wed 06-03 — unfinished (evening)

Ask the user to pick which ones to fill. Weekends and intentional skips just go unselected — never nag about a day the user leaves unchecked. If nothing is flagged, say the window is clear and stop.

Per-day interview

Walk the selected days one at a time (oldest first). For each day, in a single message:

  1. State the date + weekday.
  2. If a Google Calendar MCP is connected, fetch that day's events and show them as a memory jog. Otherwise skip this step — Calendar is an optional nudge, not a requirement; the catch-up works without it.
  3. Ask one combined recall question:
    • Absent / Stub: "What did you work on or get done that day? Any wins? Anything worth logging?"
    • Unfinished: ask /daily's three Evening questions (wins / log / carry-forward).

Wait for the answer before moving to the next day. If the user doesn't remember a day or says skip, skip it — no invented content (Absent → no note created; Unfinished → left as-is).

Filing the answer

  • Absent / Stub: create the note from templates/daily.md (create YYYY/MM/ folders if missing), substitute {{date}} and {{day-of-week}}. File Wins → Wins, everything else → Notes / log. Leave the forward-planning sections (Top 3, Week's focus, Carried-from-yesterday, Carry-forward) as blank template placeholders — you can't retro-plan a past day.
  • Unfinished: fill only the empty Wins / Notes-log / Carry-forward sections (never overwrite existing content).
  • Both: add backfilled: <today's date> to the note's YAML frontmatter so it's honest that the note was reconstructed later, not written that day.
  • Use [[wikilinks]] whenever the answer names a project, person, or concept that has a vault note.

Rules

  • Today is never in scope. Run /daily for today.
  • One day at a time. Don't collapse multiple days into one fuzzy answer — each date gets its own note from its own recollection.
  • Never overwrite existing content (inherited from /daily).
  • Never invent tasks, wins, or log entries. Every line comes from the user; an unremembered day is skipped, not fabricated.
  • Every backfilled note carries backfilled: <date> in frontmatter.
  • Calendar is optional. If no Calendar MCP is connected, the per-day memory-jog step is simply skipped — nothing else changes.

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.