work-end
Skill1 starsChanged 50 days agoMITView on GitHub
End-of-day summary — what got done, what carries over, what's new since /work-start. Use when the user says "/work-end", "konec dne", "shrnutí dne", "wrap up the day". Does not stop the time tracking timer — that is tracker-stop.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- anonymize-outputSkill
- cart-fillSkill
- client-questionsSkill
- code-reviewSkill
- conventional-commitSkill
- critical-pathSkill
- debate-replySkill
- decision-analysisSkill
- dependency-diagramsSkill
- dm-catchupSkill
- dm-composeSkill
- dockerizeSkill
- epic-breakdownSkill
- geo-page-auditSkill
- init-projectSkill
- kodexSkill
- launchpad-fixSkill
- mail-catchupSkill
- mcp-server-adoptSkill
- merge-prSkill
- mikrotik-auditSkill
- oponenturaSkill
- pr-rebase-sweepSkill
- raw-source-checkSkill
- resource-busySkill
- retroSkill
- second-opinionSkill
- semver-releaseSkill
- session-recallSkill
- skill-dry-runSkill
- skillifySkill
- skillset-adoptSkill
- task-deliverySkill
- task-estimateSkill
- teammate-checkSkill
- team-standupSkill
- token-auditSkill
- tracker-backfillSkill
- tracker-log-entrySkill
- tracker-setup-trackerSkill
- tracker-startSkill
- tracker-stopSkill
- wireguard-diagnoseSkill
- work-reconcileSkill
- work-setupSkill
- work-standupSkill
- work-startSkill
- work-statusSkill
- worktree-cleanupSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
If missing: stop with this message — in both languages.
- Very specific: line 20
If schema_version is not 1: warn "Snapshot je z jiné verze skillu.
- Very specific: line 26
If age_hours > 24: warn "Snapshot je z předchozího dne (před <X> hodinami).
- Very specific: line 90
If completed_total == 0 and carry_over == 0 and new_unhandled == 0: render "Žádná aktivita dnes.
- Very specific: line 94
Check if the session-log plugin is installed by reading ~/.claude/plugins/session-log/config.json.
- Very specific: line 97
Read the config to find the session log directory (session_log_dir field, or default ~/Documents/claude-sessions/).
- Distinctive: line 98
Ask "Uložit dnešní souhrn do session logu?" and offer the options:
- Distinctive: line 103
Check whether it exists. If it does, append — a plain file write would overwrite the day's earlier entries, so shell out:
- Distinctive: line 107
If the file doesn't exist, create it with just the summary.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Work End
End-of-day retrospective: what closed, what carries over, what arrived during the day.
Steps
Read snapshot:
Read
~/.claude/plugins/work/last-briefing.json.- If missing: stop with this message — in both languages; the config naming one is not read until step 2: "Žádný snapshot. Bez ranního /work-start nelze udělat end-of-day souhrn." / "No snapshot. Without a morning /work-start there is no end-of-day summary to make." Return.
- If
schema_versionis not1: warn "Snapshot je z jiné verze skillu. Pokračuju best-effort." Continue. - Compute age:
Ifdate -u +%s date -u -j -f "%Y-%m-%dT%H:%M:%SZ" "<snapshot.timestamp>" +%s # macOSage_hours > 24: warn "Snapshot je z předchozího dne (před<X>hodinami). Souhrn může být zavádějící."
- Read effective config — same as
/work-startstep 1. Stop if missing. Re-fetch all enabled sources:
Same as
/work-startstep 3 (parallel fetch of all enabled and available sources), BUT also include completed items for the "completed today" computation:- Todoist (in addition to open tasks): call
mcp_Todoist__find-completed-taskswith{ "since": "<midnight today UTC>" }. Get midnight via:date -u -j -v0H -v0M -v0S +%Y-%m-%dT%H:%M:%SZ # macOS, today UTC midnight # Linux: date -u -d 'today 00:00' +%Y-%m-%dT%H:%M:%SZ - GitHub: in addition to open queries, run:
mcp__github__search_issueswith{ "q": "is:closed is:issue assignee:<username> closed:>=<today UTC>" }mcp__github__search_pull_requestswith{ "q": "is:closed author:<username> closed:>=<today UTC>" }
- ClickUp: ClickUp
clickup_filter_taskscan also filter by status — call once withstatus=closed, date_updated_gt=<midnight epoch ms>. (Refer to the MCP tool's schema for exact arg names.) - Calendar: skip (events don't have a "completed today" sense).
Build:
current_open— normalized open items (same as /work-start)completed_today— normalized completed items closed/completed today
- Todoist (in addition to open tasks): call
Compute completed / carry-over / new-unhandled:
completed_total=completed_today(all items that finished today, regardless of whether they were in the morning briefing)completed_from_briefing= subset ofcompleted_todaywhoseidmatches a snapshot itemcarry_over= snapshot items whoseidis incurrent_open(still open at end of day)new_unhandled= items incurrent_openwhoseidis NOT in snapshot AND NOT incompleted_today
Sort each list by score descending (re-score
carry_overandnew_unhandledusing current data via/work-startstep 5 scoring; forcompleted_todayuse the score they had in the snapshot if available, else 0).Render summary in the configured language. Every quoted user-facing string in this skill is an example written in
cs— render it ineffective_config.language, keeping proper nouns, IDs, paths and durations unchanged. The step-1 message above is the exception: it carries both languages because it fires before the config is read.## 📊 Souhrn dne — <today's date> Doba od /work-start: **<X>h <Y>min** ### ✅ Dokončeno: <N> celkem (<M> z ranního briefingu) 1. **<title>** — <source> ... ### 📝 Přechází na zítra: <N> 1. **<title>** — <source>, score <N> ... ### ⚠️ Nové během dne, neřešeno: <N> 1. **<title>** — <source>, score <N>, dorazilo <H>h zpět ... <Warnings if any>If
completed_total == 0andcarry_over == 0andnew_unhandled == 0: render "Žádná aktivita dnes. Vše uzavřeno před snapshotem."Optionally save to session log:
Check if the
session-logplugin is installed by reading~/.claude/plugins/session-log/config.json. If it doesn't exist, skip this step silently.If it exists:
- Read the config to find the session log directory (
session_log_dirfield, or default~/Documents/claude-sessions/). - Ask "Uložit dnešní souhrn do session logu?" and offer the options:
- "Ano (append k dnešnímu logu)"
- "Ne, jen vypsat"
- If "Ano":
- Determine today's log file name (convention:
<dir>/YYYY-MM-DD.md). - Check whether it exists. If it does, append — a plain file write would overwrite the day's earlier entries, so shell out:
printf '\n\n## work-end summary\n\n%s\n' '<rendered summary above>' >> '<path>' - If the file doesn't exist, create it with just the summary.
- Determine today's log file name (convention:
Confirm: "Uloženo do
<path>."- Read the config to find the session log directory (
Edge cases
- No sources fetched successfully: render only "Žádný zdroj nedostupný. Souhrn dne nelze sestavit. Zkontroluj MCP servery." Skip lists.
- All snapshot items still open, nothing completed today: render with
completed_total = 0section saying "(žádné položky dokončeny dnes)", and fullcarry_overlist. - Snapshot from prior day: render but with warning about age. Don't try to "extend" the snapshot range — be honest that the comparison baseline is stale.
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
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.

