agentleFS
Sign inStart free
Layneformalized225Layneformalized225/ai-cofounder/skills/daily-recap/SKILL.md

daily-recap

Skill1 starsChanged 8 months agoMITView on GitHub

End-of-day consolidation — summarize daily log, promote durable facts to MEMORY.md, identify open threads

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If yes — update MEMORY.md:

    line 44
  2. Distinctive:

    Update review timestamp if Constraint or PMF Stage changed

    line 46
  3. Distinctive:

    If the day was empty: "Quiet day.

    line 74
  4. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 76
  5. Distinctive:

    Don't fabricate — only from today's entries

    line 81
  6. Distinctive:

    If MEMORY.md was updated — mention: "MEMORY.md updated: [what exactly]"

    line 83

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

Daily Recap

End-of-day consolidation. Triggered by heartbeat at 21:00-22:00 or manually ("recap the day").

Algorithm

1. Read today's log

Open memory/YYYY-MM-DD.md. If empty or no entries — write "No entries today" and HEARTBEAT_OK.

2. Extract key items

From all entries of the day, compile:

## Daily Recap

**Decisions:** (decisions made today)
- [decision]: [why] -> [what changes]

**New facts:** (new confirmed facts)
- [fact] (source: [where from])

**Belief changes:** (what shifted in understanding)
- [was] -> [became] (evidence: [what showed it])

**Open threads:** (started but not finished)
- [topic]: [what remains to be done]

**Constraint check:** [current constraint] — today [exploit/subordinate/ignore]?

3. Check for promotion to MEMORY.md

For each new fact and belief change, ask:

  • Does this change something in MEMORY.md sections? (Company, Wedge, PMF Stage, Metrics, Constraint)
  • Is it sufficiently confirmed? (not a single data point)

If yes — update MEMORY.md:

  • Replace outdated info (don't duplicate)
  • Update review timestamp if Constraint or PMF Stage changed
  • Keep MEMORY.md < 3KB

4. Write recap to daily log

Append the ## Daily Recap block to the end of memory/YYYY-MM-DD.md.

5. Update heartbeat state

In memory/heartbeat-state.json set "lastRecapDate": "YYYY-MM-DD".

Telegram Output Format

Day recap:

Decisions: X
- brief description of each

New facts: Y
- brief description of each

Open: Z threads
[list if any]

Constraint: [exploit/subordinate/ignore today]

If the day was empty: "Quiet day. No entries."

Follow output preferences from USER.md (language, format, platform constraints).

Rules

  • Max 15 lines for Telegram
  • Don't fabricate — only from today's entries
  • Belief changes > facts > tasks by importance
  • If MEMORY.md was updated — mention: "MEMORY.md updated: [what exactly]"

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.

Check your setup, free