agentleFS
kiloloopkiloloop/iantha/.claude/skills/morning/SKILL.md

morning

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Daily start-of-day briefing — reads memory, surfaces today's tasks, overdue items, recurring obligations, and personal-life reminders. Use this whenever the user types /morning, asks "what's on my plate today" / "what should I focus on" / "kick off the day", starts a new day's session and hasn't been briefed yet, or wants a daily standup-style rundown of personal life. If a vault is configured, can also write the briefing to today's daily note.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use import-memory, pptx and 4 more.

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

    import-memory

    Import a memory export from another AI assistant into Claude's memory — conversationally, additively, and with the content treated as data.

    Also in 4 projects that use this

  • AnthropicSkill

    pptx

    Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

    Also in 5 projects that use this

  • AnthropicSkill

    pdf

    Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

    Also in 6 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 6 projects that use this

  • +2 more from anthropics

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 4

    Distinctive

    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. Distinctive:

    Read memory, surface what matters today.

    line 8
  2. Very specific:

    When the user runs /morning, do the following:

    line 12
  3. Very specific:

    Read config.yaml (and config.local.yaml if present, with local overriding).

    line 16
  4. Very specific:

    If vault_dir is set, also read yesterday's daily note (${vault_dir}/${vault_daily}/YYYY-MM-DD.md) — specifically look for a ## Wrap section …

    line 27
  5. Distinctive:

    If nothing is due today and nothing overdue, say so plainly: "Nothing on the calendar today.

    line 61
  6. Very specific:

    If the user reacts to anything in the briefing ("that's done", "move that to tomorrow", "drop that"), update memory/tasks.md accordingly.

    line 69
  7. Very specific:

    Use the user's local timezone for "today" (config.yaml: timezone overrides system TZ)

    line 96
  8. Distinctive:

    Keep the briefing under 20 lines unless there's genuinely a lot

    line 97
  9. Distinctive:

    Don't read all memory files — just what's listed in step 2

    line 98
  10. Very specific:

    If priorities.md or personal.md is empty (fresh repo), skip those sections silently

    line 99

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

/morning — Daily Briefing

Read memory, surface what matters today.

Instructions

When the user runs /morning, do the following:

1. Load config

Read config.yaml (and config.local.yaml if present, with local overriding). Note whether vault_dir is set — controls steps 6 and 7 below.

2. Read memory

  • memory/tasks.md — all sections
  • memory/priorities.md — current top focus
  • memory/personal.md — routines and life context (only what's relevant to today)
  • memory/decisions.md — recent entries (last 7 days)

Fresh-clone demo: if the live memory files are still blank templates and memory/*.md.example sample seeds exist, build the briefing from the seeds instead — label it plainly ("demo from sample data — your memory is still blank") and invite the user to seed it for real: "this was sample data — run /setup and I'll ask a few quick questions to make it yours, or just start telling me about your day." Never copy seed content into the live files. See CLAUDE.md First-Run Notes.

If vault_dir is set, also read yesterday's daily note (${vault_dir}/${vault_daily}/YYYY-MM-DD.md) — specifically look for a ## Wrap section (carry-over from /evening) or any "tomorrow" / "carrying over" notes. If the file doesn't exist or has no carry-over content, skip silently.

3. Identify today's items

From tasks.md:

  • Due today: items with today's date
  • Overdue: items with a date earlier than today, not archived
  • Recurring due today: items in the Recurring section whose "Next due" matches today
  • Time-sensitive: anything in Urgent / Time-sensitive section

4. Build the briefing

Output a short, scannable briefing:

## Morning Briefing — YYYY-MM-DD

### Today
- [item 1]
- [item 2]

### Overdue
- [item with original due date]

### Watch
- [priorities or things to keep in mind]

### Reminders
- [anything from personal.md routines for today, e.g., "Tuesday gym day"]

Sections that are empty: omit them entirely. Don't pad.

If nothing is due today and nothing overdue, say so plainly: "Nothing on the calendar today. Want to plan something?"

5. Surface, don't dispatch

This is a briefing, not a work session. Don't start executing tasks unless the user asks.

6. Offer task updates

If the user reacts to anything in the briefing ("that's done", "move that to tomorrow", "drop that"), update memory/tasks.md accordingly. Confirm and commit.

7. Optional vault write (only if vault_dir configured)

Offer to write the briefing to ${vault_dir}/${vault_daily}/YYYY-MM-DD.md via /obsidian daily-log with section name Briefing. Default to "yes" if the user has confirmed once before; otherwise ask. Skip silently if vault_dir is unset.

Example output

## Morning Briefing — 2026-05-01

### Today
- Submit LLC franchise tax payment (due today)
- Coffee with Mei — 2pm, Sightglass

### Overdue
- Renew passport (was due 2026-04-25)

### Watch
- Quitting coffee experiment, day 4 — track headache severity

### Reminders
- Friday gym day

Notes

  • Use the user's local timezone for "today" (config.yaml: timezone overrides system TZ)
  • Keep the briefing under 20 lines unless there's genuinely a lot
  • Don't read all memory files — just what's listed in step 2
  • If priorities.md or personal.md is empty (fresh repo), skip those sections silently
  • Vault writes are optional — only happen when vault_dir is configured

Learned from runs

(empty — populated as the skill is used)

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.