agentleFS
bradautomatesbradautomates/second-brain/.claude/skills/daily-review/SKILL.md

daily-review

Skill217 starsChanged 8 months agoMITView on GitHub

End of day review - compare planned vs actual, update task statuses. Part of chief-of-staff system.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use weekly-review.

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.
  • QuixiAISkill

    weekly-review

    Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    Read daily/YYYY-MM-DD.md for today's plan

    line 13
  2. Very specific:

    Run git log --since="8am" --grep="cos:" for activity

    line 14
  3. Very specific:

    Search for tasks due today: grep -l "due: YYYY-MM-DD" task/*.md

    line 16
  4. Distinctive:

    Read only the relevant task files identified above

    line 18
  5. Very specific:

    Update task statuses (status: done for completed items)

    line 19

“Common” is measured: kept by at least 6 in 10 of the 11 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-review - End of Day Review

Compare planned vs actual for today.

Steps

  1. Read daily/YYYY-MM-DD.md for today's plan
  2. Run git log --since="8am" --grep="cos:" for activity
  3. Find relevant tasks efficiently (don't read all tasks):
    • Search for tasks due today: grep -l "due: YYYY-MM-DD" task/*.md
    • Find task files modified today: git diff --name-only HEAD@{8am}..HEAD -- task/
  4. Read only the relevant task files identified above
  5. Update task statuses (status: done for completed items)
  6. Append review section to daily note
  7. Commit: cos: daily review for YYYY-MM-DD

Append to Daily Note

## Review

### Completed
- ✅ Items that got done

### Incomplete
- ⏳ Items carrying forward

### Observations
- Patterns noticed, suggestions for tomorrow

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.