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

daily

Skill0 starsChanged 5 months agoMITView on GitHub

Create or open today's daily note, then interview the user to fill it in. Morning run = intake (Top 3 + a planning nudge from orient.md and any live deadlines). Later run = evening wrap-up (wins, log, carry-forward). Use at the start of each working day, and again at end of day to close it out.

  • Commits and pushes

22 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use monthly, apply and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • gaiaaiagentSkill

    monthly

    Generate a monthly digest distilling weeklies into trend analysis and narrative arcs

    Also in 3 projects that use this

  • proficientlyjobsSkill

    apply

    Fill out a job application on Greenhouse, Lever, or Workday

    Also in 3 projects that use this

  • anombyte93Skill

    discover

    Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. 0 are common, 5 are distinctive, and 12 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 5

    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
  1. Very specific:

    Read _meta/orient.md and extract the "This week's focus" section.

    line 49
  2. Very specific:

    Create the note from templates/daily.md, substituting:

    line 72
  3. Very specific:

    If parent folders 50-daily/YYYY/MM/ don't exist, create them first.

    line 78
  4. Very specific:

    Read orient.md's "This week's focus" (already loaded during Setup) and scan it for named, time-sensitive deadlines.

    line 86
  5. Very specific:

    If there is NO manifest line at all (the overnight run never happened or left a failure stub) → run /dream as a full catch-up first, then …

    line 133
  6. Very specific:

    After finishing a stage, update its token to ok in the manifest line.

    line 135
  7. Very specific:

    Brief the dream: Read the ## 🌙 Overnight section and tell the user in 2–3 lines what it did: note created, tasks carried, and how many …

    line 138
  8. Very specific:

    Fill Today's Tasks (the part dream couldn't): Run only Setup step 3 — the task manager pull (skip if no task DB is configured) — and …

    line 145
  9. Very specific:

    If it lists items (format: task (Nd)), fold them into the same message as the Top-3 question (step 5) — the stuck list goes before the …

    line 155
  10. Distinctive:

    Ask in a single message (all three at once):

    line 181
  11. Distinctive:

    Wait for the response, then fill the empty sections:

    line 187
  12. Very specific:

    After filling the sections, if a git remote is configured, push the day (so an overnight /dream consolidates it) — run via Bash: git add -A …

    line 193
  13. Very specific:

    Never rewrite the dream's narrative, the Stuck: line, ### Auto-applied, the ### orient.md Applied: line, the ### Flow triage - Stale: …

    line 209
  14. Distinctive:

    Sync is part of the ritual when configured: if a git remote exists, EVERY run starts with git pull --ff-only (Step 0, morning and evening …

    line 213
  15. Distinctive:

    No remote → both git steps are simply skipped.

    line 216
  16. Distinctive:

    Do not invent tasks, wins, or log entries: Every line comes from the user.

    line 217
  17. Very specific:

    Use [[wikilinks]] whenever the user's answer mentions a project, person, or concept that has a note in the vault.

    line 225

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

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

Daily Skill

What this does

Creates or opens today's daily note at 50-daily/YYYY/MM/YYYY-MM-DD.md, then runs a short interactive interview to fill it in. The skill is mode-aware: it picks morning intake or evening wrap-up based on the note's current state — you run the same /daily command morning and evening.

Integrations are optional. Git sync (Step 0 / evening push) and the Notion task-pull both run only if you've configured them; with neither, /daily is a pure-vault journaling loop that needs no external services. The /dream hygiene pass is an optional companion — if you run it (manually or on a nightly scheduler), /daily picks up its work the next morning, but /dream is never required.

Step 0 — Sync first (EVERY run — only if a git remote is configured)

If this vault is wired to a git remote, run git pull --ff-only via Bash before mode detection on every /daily run (morning OR evening). This loads any overnight /dream commit (and work pushed from another machine) so mode detection sees the freshest state — without it, a not-yet-pulled overnight note looks absent and misroutes to plain MORNING instead of MORNING-POST-DREAM. If the pull fails (diverged / offline / merge in progress), or there's no remote, say so and continue with the local state — never block the day on git. Single-machine, no-remote setups skip this step entirely.

Mode detection

Compute today's date (YYYY-MM-DD) and the path 50-daily/{YYYY}/{MM}/{YYYY-MM-DD}.md, then branch:

Note stateMode
File does not existMORNING — create the note (Setup below), then run Morning intake.
Exists with a ## 🌙 Overnight section, Top 3 emptyMORNING-POST-DREAM — a /dream pass already made the note; brief it, then post-dream intake (below). Check this row BEFORE the next one.
Exists, Top 3 empty (no dream section)MORNING — open it, run Morning intake (finish the morning).
Exists, Top 3 filled, Wins emptyEVENING — open it, run Evening wrap-up.
Exists, Wins already filledDONE — open it, report current contents, stop.

Setup (MORNING, when the file does not exist)

  1. Find the most recent prior daily note (search 50-daily/ for the latest YYYY-MM-DD.md before today). Extract:
    • Unchecked tasks (lines starting with - [ ])
    • Items under a "Carry forward to tomorrow" section if present
  2. Read _meta/orient.md and extract the "This week's focus" section.
  3. Pull due-today + overdue tasks from your task manager — only if a Notion task DB is configured (see capture-task's Setup and _meta/notion-bridge.md). If no task DB is configured, write "—" under Today's Tasks and skip to step 4. When configured, run this exact procedure, in order, no improvising and no extra exploratory calls. (This connector has NO date-filter / SQL query tool and CANNOT fetch a view URL, so the steps below are the floor — don't go looking for a cheaper query that doesn't exist.) a. One mcp__claude_ai_Notion__notion-search call: { data_source_url: "collection://<YOUR_TASK_DB_DATA_SOURCE_ID>", query: "incomplete task due date deadline overdue this week", page_size: 25, max_highlight_length: 0 } b. Take the page IDs it returns and mcp__claude_ai_Notion__notion-fetch them in ONE parallel batch (all in a single message). Do not fetch in multiple rounds; do not fetch anything not in (a)'s results. c. Keep a task only if Done == "__NO__" AND date:Due Date:start ≤ today (compare by date; a task due later today still counts; date-only and datetime both count). Drop everything done or due in the future. (Adjust the field names to your schema mapping if yours differ.) d. Sort kept tasks by due date ascending and write each to Today's Tasks as - [ ] {Task} (due M/D[, **overdue**]). If none qualify, write "—".
    • Known limit (state it, don't fix it): search is semantic and capped at 25, so a deep overdue tail can be missed. Acceptable for a daily driver. If Notion is unavailable, write "—" and move on — never block the morning on it.
  4. Create the note from templates/daily.md, substituting:
    • {{date}} → today's YYYY-MM-DD
    • {{day-of-week}} → today's day name
    • Carried-forward section → extracted unchecked tasks (or "—" if none)
    • Week's focus section → content from orient.md
    • Today's Tasks section → tasks due today + overdue (or "—" if no task DB / unavailable)
    • If parent folders 50-daily/YYYY/MM/ don't exist, create them first.

Morning intake

Any overnight /dream pass was already pulled in Step 0 (if git is configured); if that pull reported a dream commit, today's note now exists with a ## 🌙 Overnight section (→ MORNING-POST-DREAM).

Read orient.md's "This week's focus" (already loaded during Setup) and scan it for named, time-sensitive deadlines. Then ask in a single message:

"What are your top 1–3 for today?"

  • a tailored planning nudge that references this week's focus and any live deadline, e.g. "<example focus item> in there? Anything for the <example deadline> (due <date>)?"

Build the nudge from whatever orient.md actually says — the example above is just shape, not content; never hardcode deadlines. Wait for the response, then write the user's priorities into the Top 3 section (slots 1–3, in the order they give them). Leave Wins and Carry-forward blank for the evening. Stop.

Morning intake (post-dream)

A /dream pass already created the note and seeded Week's focus + Carried from yesterday, and wrote a ## 🌙 Overnight section. Do not re-create the note, re-run carry-forward/week-focus, or overwrite the dream section. Steps:

  1. Read the manifest + finish what the dream pass didn't. Find the > 🌙 manifest v1 | line in the ## 🌙 Overnight section. For each stage not marked ok, complete it now (you are interactive, integrations are reachable, the user is present):
    • hygiene-b not ok → walk the ### Needs your OK queue (step 2 below) and resolve each with the user, then flip the token to ok.
    • brief-b not ok → fill the ### Morning Brief Yesterday: and Revisit: placeholders exactly as the /dream skill's Layer-B step specifies (2–3 line recap from the prior note; one revisit note + one prompt).
    • orient-b not ok → in the ### orient.md block, replace the Proposed: placeholder with section-move proposals exactly as the /dream skill's Layer-B orient step specifies (plain bullets, never - [ ]; — none if nothing qualifies) — these are proposals only; do not move any orient.md section or edit _meta/orient.md. Then flip orient-b:ok. (Layer A already refreshed orient's heat/last-touched — or, in the no-manifest full-catch-up case below, /dream runs it — so you never recompute heat here.)
    • flow-b not ok → in the ### Flow triage block, replace each - Inbox: line's _(pending …)_ placeholder with a proposed destination + one-line reason exactly as the /dream skill's Layer-B inbox-triage step specifies (plain prose, never - [ ]). These are proposals only — do not move any file out of 00-inbox/, and leave the - Stale: lines (Layer A's orphan facts) untouched. Then flip flow-b:ok. (If there were no inbox items, just flip flow-b:ok.)
    • connect-b not ok → in the ### Connections block, curate Layer A's candidate feed exactly as the /dream skill's Layer-B connect step specifies: fill each - Link: / - MOC: / - Merge: line's _(… pending …)_ placeholder with the theme / map-note decision / survivor (plain - bullets, never - [ ]), or delete a noise line. These are proposals only — do not add any [[wikilink]], create a MOC note, or merge a note, and leave the > staleness banner untouched. Then flip connect-b:ok. (If the block was - — none, just flip connect-b:ok.)
    • If there is NO manifest line at all (the overnight run never happened or left a failure stub) → run /dream as a full catch-up first, then continue from step 1 below. After finishing a stage, update its token to ok in the manifest line. Only flip a token to ok after that stage's work is verifiably done — never mark a stage ok you did not actually complete. Do not rewrite any other part of the dream section.
  2. Brief the dream. Read the ## 🌙 Overnight section and tell the user in 2–3 lines what it did: note created, tasks carried, and how many items are under Needs your OK.
  3. Walk the approve-queue. For each Needs your OK item (missing frontmatter, markdown-vs-wikilink, unapproved tag, dangling wikilink), ask the user whether to fix it. Apply only the ones they approve, honoring the house rules (never invent frontmatter values silently; never auto-add tags; propose _meta/ edits, don't make them). Leave the dream section text itself in place.
  4. Fill Today's Tasks (the part dream couldn't). Run only Setup step 3 — the task manager pull (skip if no task DB is configured) — and replace the ⏳ pending — /daily will pull from your task manager marker under ## Today's Tasks with the result (or — if no task DB / unavailable). Do NOT redo carry-forward or week-focus. If you pulled tasks, also append the due-today + overdue tasks from that same fetched set to the ### Morning Brief Deadlines: line (dream only had vault-dated items; this adds the task-manager tasks you just fetched — same filter). If Deadlines: was — none, replace it; otherwise append with ; .
  5. Stuck-list decision (batched into the single morning message). Read the ### Morning Brief Stuck: line. If it is — none or blank, skip silently. If it lists items (format: task (Nd)), fold them into the same message as the Top-3 question (step 5) — the stuck list goes before the Top-3 ask, so the whole morning is one outgoing message and one incoming reply:

    "These tasks have been carried for 5+ days — want to act on any of them?

    • [task A] (7d)
    • [task B] (5d) For each: reschedule, break into smaller next-actions, mark done, or archive — or say nothing and they stay carried as-is.

    What are your top 1–3 for today? [planning nudge here]"

    Parse the user's single reply for both: apply their explicit per-item stuck choices, and write their Top 3. Only follow up if a chosen action needs a missing detail (e.g., "reschedule — to when?"). Actions:

    • Reschedule → update the task's due date or carry note as they specify.
    • Break down → help them draft 2–3 smaller next-actions (captured as tasks or vault notes per their direction).
    • Done → mark the task complete (check it off / update the task manager as appropriate).
    • Archive → move the note or task to 40-archive/ (never delete; see house rule #4).
    • No instruction for an item → leave it carried exactly as-is. Do NOT remove, hide, check off, or archive any stuck item that was not explicitly addressed by the user.
  6. Top-3 intake. Already included in the single morning message (step 4). Write the user's priorities into Top 3 (slots 1–3, in the order given). Leave Wins and Carry-forward blank for the evening. Stop.

Evening wrap-up

Ask in a single message (all three at once):

  1. "What got done / any wins today?"
  2. "Anything worth logging from today?"
  3. "What didn't finish — carry to tomorrow?"

Wait for the response, then fill the empty sections:

  • Wins → Wins
  • Log items → Notes / log
  • Unfinished items → Carry forward to tomorrow, each as a - [ ] checkbox task (tomorrow's Setup auto-pulls these into "Carried from yesterday").

After filling the sections, if a git remote is configured, push the day (so an overnight /dream consolidates it) — run via Bash: git add -A && git commit -m "daily {{date}}: evening wrap-up" && git push (substitute today's date). If the commit/push fails, or there's no remote, tell the user and continue — never block the wrap-up on git.

Rules

  • Never overwrite existing content. Morning fills Top 3; evening fills only the empty Wins / Notes / Carry-forward sections. If a section already has content, leave it alone.
  • Only touch the ## 🌙 Overnight section to finish unfinished dream stages — fill the Yesterday:/Revisit: placeholders, enrich Deadlines:, fill the ### orient.md Proposed: placeholder with section-move proposals, fill each ### Flow triage - Inbox: destination placeholder (propose-only — never move the file), curate the ### Connections candidate placeholders into worded Link/MOC/Merge proposals (propose-only — never add a link, create a MOC, or merge a note), and update manifest tokens to ok. Never rewrite the dream's narrative, the Stuck: line, ### Auto-applied, the ### orient.md Applied: line, the ### Flow triage - Stale: lines, or the ### Connections > staleness banner (Layer A owns the heat/last-touched facts, the orphan list, and the graph-staleness facts).
  • Sync is part of the ritual when configured: if a git remote exists, EVERY run starts with git pull --ff-only (Step 0, morning and evening alike) and every EVENING wrap-up also ends by committing + pushing. This keeps an overnight /dream on the freshest state. No remote → both git steps are simply skipped.
  • Do not invent tasks, wins, or log entries. Every line comes from the user.
  • Never drop a stuck task without explicit per-item consent. The Stuck: items in ### Morning Brief must be surfaced and may only be removed, archived, checked off, or rescheduled when the user explicitly says so for that specific item. Silence = carry it forward untouched. Archive always means move to 40-archive/, never delete (house rule #4).
  • Batch questions per mode — one message for morning, one for evening. Don't drag it into a slow back-and-forth; this is a daily driver and should be fast.
  • Use [[wikilinks]] whenever the user's answer mentions a project, person, or concept that has a note in the vault.

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.