agentleFS
Sign inStart free
mykyta-lytvynenkomykyta-lytvynenko/claude-code-starter-kit/skills/daily-review/SKILL.md

daily-review

Skill0 starsChanged 7 months agoMITView on GitHub

Run a morning check-in: review what's on deck, surface anything blocking progress, and set up for a productive day. Read Workflows to understand how this person organizes their work — their tools, their priorities system, and what a "productive day" means for them. If docs/workflows.md doesn't exist or has placeholder text, tell the user: "Fill in docs/workflows.md first — I need to know how you track work before I can run a useful review." Keep it short. The review should…

17 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

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run a morning check-in: review what's on deck, surface anything blocking progress, and set up for a productive day.

    line 3
  2. Distinctive:

    Read Workflows to understand how this person organizes their work — their tools, their priorities system, and what a "productive day" means …

    line 7
  3. Very specific:

    If docs/workflows.md doesn't exist or has placeholder text, tell the user: "Fill in docs/workflows.md first — I need to know how you track …

    line 9
  4. Distinctive:

    Keep it short. The review should take 2 minutes to read, not 10.

    line 22
  5. Distinctive:

    Don't list everything in their backlog — just the 3-5 that matter today

    line 39
  6. Distinctive:

    Don't ask clarifying questions about each item — surface them, then ask once at the end

    line 40
  7. Distinctive:

    Don't run this without reading workflows.md first

    line 41
  8. Distinctive:

    Notion / Linear / Trello: Ask user to paste in their open items, or use MCP if connected

    line 45
  9. Distinctive:

    Google Sheets: Ask for a quick summary of what's open, or use Sheets MCP if connected

    line 46
  10. Distinctive:

    No tool / mental load: Ask "What's the 3 things you need to get done today?" and work from there

    line 47

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

Skill: Daily Review

Run a morning check-in: review what's on deck, surface anything blocking progress, and set up for a productive day.

Before You Start

Read Workflows to understand how this person organizes their work — their tools, their priorities system, and what a "productive day" means for them.

If docs/workflows.md doesn't exist or has placeholder text, tell the user: "Fill in docs/workflows.md first — I need to know how you track work before I can run a useful review."

Steps

  1. Read workflows.md — understand their task management setup and what to check
  2. Ask what to review — if they didn't specify, ask: "Want me to pull from [their tool], or walk through what's on your mind?"
  3. Surface the short list — identify the 3 most important things to move today, based on urgency and impact
  4. Flag blockers — anything waiting on someone else, overdue, or unclear
  5. Suggest a starting point — recommend which item to tackle first and why
  6. End with a check-in question — "Anything else on your plate I should know about?"

Output Format

Keep it short. The review should take 2 minutes to read, not 10.

## Today's Focus
1. [Most important task] — [why it's first]
2. [Second task]
3. [Third task]

## Blockers / Waiting On
- [Item] — waiting on [person/thing] since [date]

## Suggested Start
[Single sentence: what to open first and why]

What NOT to Do

  • Don't list everything in their backlog — just the 3-5 that matter today
  • Don't ask clarifying questions about each item — surface them, then ask once at the end
  • Don't run this without reading workflows.md first

Adapting to Different Systems

  • Notion / Linear / Trello: Ask user to paste in their open items, or use MCP if connected
  • Google Sheets: Ask for a quick summary of what's open, or use Sheets MCP if connected
  • No tool / mental load: Ask "What's the 3 things you need to get done today?" and work from there

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