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

evening

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

End-of-day wrap-up — archives completed tasks from memory, rolls over recurring obligations, surfaces tomorrow's items, and optionally writes a daily log to the user's Obsidian vault. Use this whenever the user types /evening, says "wrap up the day" / "close out" / "let's call it", finishes a substantive day of work, or wants to commit memory updates before stopping.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. thatmike1/claude-skills★ 10same name
    2. latuconsinafr/claude-code-config★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

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

    When the user runs /evening, do the following:

    line 12
  2. Very specific:

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

    line 16
  3. Very specific:

    Update the *Updated:* timestamp at the top of the file.

    line 28
  4. Very specific:

    Look at memory/tasks.md for items due tomorrow or carrying over.

    line 39
  5. Very specific:

    If vault_dir is set in config.yaml, call /obsidian daily-log to append today's wrap entry to ${vault_dir}/${vault_daily}/YYYY-MM-DD.md.

    line 43
  6. Very specific:

    If vault_dir is unset, skip silently — Iantha doesn't keep in-repo daily logs by default.

    line 45
  7. Very specific:

    If yes: propose adding to memory/decisions.md (with date + Why) or as a standing rule in CLAUDE.md.

    line 51
  8. Distinctive:

    Wait for user confirmation before writing.

    line 52
  9. Distinctive:

    Don't push unless the user asks.

    line 62
  10. Distinctive:

    Keep the wrap conversational — this isn't a status report, it's a quick close-out

    line 82
  11. Very specific:

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

    line 83
  12. Distinctive:

    If nothing was done today, that's fine — just close cleanly.

    line 84

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

/evening — Daily Wrap

Archive what got done, plan tomorrow, commit.

Instructions

When the user runs /evening, 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 step 6.

2. Identify what got done

Walk through what was discussed and worked on this session/day. Ask the user if anything is unclear ("Did X get finished?").

3. Archive completed tasks

For each task confirmed done:

  1. Move from its active section (Urgent / Work / Personal) in memory/tasks.md to the Archive section under the current month header.
  2. Format: - [x] [YYYY-MM-DD] Task description — outcome
  3. Update the *Updated:* timestamp at the top of the file.

4. Roll over recurring tasks

For each item in the Recurring section that was completed today:

  1. Auto-advance the "Next due" date based on cadence (daily / weekly / monthly / etc.)
  2. Mark the prior occurrence in the Archive with date

5. Note tomorrow's top items

Look at memory/tasks.md for items due tomorrow or carrying over. Surface them briefly to the user. Adjust priorities if the user wants.

6. Daily log (if vault_dir configured)

If vault_dir is set in config.yaml, call /obsidian daily-log to append today's wrap entry to ${vault_dir}/${vault_daily}/YYYY-MM-DD.md. Use a ## Wrap section. Keep to 5-15 lines: what got done, what's carrying over, anything notable.

If vault_dir is unset, skip silently — Iantha doesn't keep in-repo daily logs by default.

7. Distillation check (Rule E)

Did any pattern repeat 3+ times this session/week? Did any decision get made that should be logged?

  • If yes: propose adding to memory/decisions.md (with date + Why) or as a standing rule in CLAUDE.md.
  • Wait for user confirmation before writing.

8. Commit

Stage updated memory files and commit:

evening: YYYY-MM-DD wrap — N tasks archived, M recurring rolled

Don't push unless the user asks.

Example wrap output (chat)

## Wrap — 2026-05-01

Done:
- Iantha v0.1.0 PR opened (#4)
- Franchise tax paid

Carrying over:
- Renew passport (now 6 days overdue — escalate?)

Tomorrow:
- /morning will surface the LLC RA renewal due 2026-05-02

Notes

  • Keep the wrap conversational — this isn't a status report, it's a quick close-out
  • Use the user's local timezone for "today" / "tomorrow" (config.yaml: timezone overrides system TZ)
  • If nothing was done today, that's fine — just close cleanly. Don't fabricate.
  • Vault daily logs 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.