agentleFS
matteo-strategamatteo-stratega/claude-cortex/.claude/skills/daily-wrap/SKILL.md

daily-wrap

Skill8 starsChanged 5 months agoMITView on GitHub

End-of-day consolidation. Merges the day's sessions into one closing report, updates context, and preps tomorrow. Use at the end of a working day, or when the user says "wrap up the day" or "daily wrap".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. derrekyoung/ai-chief-of-staff★ 2same 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 repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check notes/daily-summaries/closing-DDMMYYYY.md (standard format).

    line 13
  2. Very specific:

    Check for split files: closing-DDMMYYYY-session2.md, closing-DDMMYYYY-*.md.

    line 14
  3. Very specific:

    If you find files in a non-standard format, rename them to closing-DDMMYYYY.md.

    line 18
  4. Very specific:

    If there are multiple sessions, write one unified TL;DR at the top of the file (Done / Pending / Next).

    line 22
  5. Distinctive:

    Remove completed items; add new pending tasks.

    line 31
  6. Very specific:

    If tomorrow is a working day, create notes/daily-summaries/prep-DDMMYYYY.md:

    line 40
  7. Distinctive:

    If tomorrow is a weekend, skip the prep file and note in the closing: "Weekend ahead — priorities resume Monday."

    line 65
  8. Very specific:

    If the user says "daily wrap quick": skip Step 4 (prep) and Step 5 (memory), write a minimal TL;DR, update only the essential context.md …

    line 88

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

Consolidate all of today's sessions and prepare for the next day. This is the heavier end-of-day pass; /close handles a single session.

Step 1: Find all of today's sessions

  1. Check notes/daily-summaries/closing-DDMMYYYY.md (standard format).
  2. Check for split files: closing-DDMMYYYY-session2.md, closing-DDMMYYYY-*.md.
  3. In a team workspace, also check the current user's folder: notes/daily-summaries/<user>/closing-DDMMYYYY*.md.

If you find files in a non-standard format, rename them to closing-DDMMYYYY.md.

Step 2: Consolidate sessions

If there are multiple sessions, write one unified TL;DR at the top of the file (Done / Pending / Next). Merge separate session files into the single closing-DDMMYYYY.md and move the originals to _archive/. Never delete — archive.

Step 3: Update context

Update brain/context.md:

  • New key decisions and status changes.
  • Remove completed items; add new pending tasks.
  • context.md is a snapshot of current state, not a log.

Then sweep brain/contexts/: for any file whose updated: is older than 7 days, reconcile it against the matching section of context.md and refresh it. This is the safety net for quick sessions where /close didn't propagate.

Step 4: Prepare tomorrow (workdays only)

If tomorrow is a working day, create notes/daily-summaries/prep-DDMMYYYY.md:

# Prep DD/MM/YYYY

## Start Here
**First thing to do:** [one concrete, executable action]

## Top 3 Priorities
1. **[Priority]** — Why: [reason] — First action: [what to do]
2. **[Priority]** — Why: [reason] — First action: [what to do]
3. **[Priority]** — Why: [reason] — First action: [what to do]

## Carryover
- Done: [quick wins]
- In progress: [active threads]
- Decisions: [to remember]

## Watch Out
- [Blockers, external dependencies, deadlines]

---
*Generated by Daily Wrap*

If tomorrow is a weekend, skip the prep file and note in the closing: "Weekend ahead — priorities resume Monday."

Step 5: Persist to memory

Save the day's durable facts to auto memory following the memory skill's house style: key decisions (with absolute dates), lessons learned, recurring patterns, strategy changes. Save only what stays useful in future sessions — the closing report already holds the full history.

Step 6: Confirm

Report: sessions consolidated, files updated, and tomorrow's first action.

Rules

  1. One file per day — consolidate, no fragments.
  2. Archive, never delete.
  3. context.md is the source of truth — keep it current.
  4. Date format DDMMYYYY — 8 digits, always.

Quick mode

If the user says "daily wrap quick": skip Step 4 (prep) and Step 5 (memory), write a minimal TL;DR, update only the essential context.md lines.

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.