agentleFS
jsuchetjsuchet/jonathan-skills-lab/skills/good-morning/SKILL.md

good-morning

Skill1 starsChanged 5 months agoMITView on GitHub

Morning briefing — reads today's daily note, surfaces tasks from yesterday, shows weekly priorities. Run /good-morning first thing every morning before you start work.

7 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 4

    Distinctive

    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: Read it and show current tasks/log entries

    line 18
  2. Distinctive:

    If NO: Create it using the daily note template structure:

    line 19
  3. Distinctive:

    If yesterday's note doesn't exist, skip this step

    line 39
  4. Distinctive:

    If it doesn't exist, note that no weekly plan is set

    line 43

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

/good-morning

Morning briefing that gets you oriented for the day.

Steps

  1. Determine today's date and construct the daily note path: periodic/daily/YYYY-MM-DD.md
  2. Check if today's daily note exists:
    • If YES: Read it and show current tasks/log entries
    • If NO: Create it using the daily note template structure:
      # YYYY-MM-DD, Day-of-Week
      
      ## Tasks
      - [ ]
      
      ## Log
      
      
      ## Notes
      
      
      ## End of Day
      
  3. Read yesterday's daily note (periodic/daily/YYYY-MM-DD.md for yesterday):
    • Surface any incomplete tasks (unchecked - [ ] items)
    • List them as "Carried forward from yesterday" with ⏩ marker
    • If yesterday's note doesn't exist, skip this step
  4. Read current weekly note (periodic/weekly/YYYY-WNN.md):
    • Show this week's focus areas and priorities
    • If it doesn't exist, note that no weekly plan is set
  5. Output the briefing in this format:
    ☀️ Good morning, [YOUR NAME] — it's [Day], [Date]
    
    ## Today's Tasks
    [Tasks from today's daily note, or "No tasks yet"]
    
    ## Carried Forward
    [Incomplete tasks from yesterday with ⏩, or "All clear from yesterday"]
    
    ## This Week's Focus
    [Focus areas from weekly note, or "No weekly plan set — consider running /weekly-review"]
  6. Do NOT modify any files. The only permitted write is creating today's daily note if it doesn't yet exist (Step 2). All other steps are read-only.

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.