ifandisalim/end-of-day
cowork-starter-pack/skills/end-of-day/SKILL.md
End-of-day shutdown that logs what was worked on so the next Claude session can pick up where things left off. Trigger this skill whenever the user says "end of day", "wrap up", "we're done", "that's it for today", "log today", "done for the day", "goodnight", "shutdown", or anything that signals they're finishing a work session. If the user seems to be wrapping up, suggest running this before they go.
development
Updated Apr 22, 2026
$ install --global
skillsauthnpx skillsauth add ifandisalim/JTI-BrivAI end-of-dayInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 10:38 PM115.2s1 file scanned
SKILL.md
- name:
- end-of-day
- description:
- End-of-day shutdown that logs what was worked on so the next Claude session can pick up where things left off. Trigger this skill whenever the user says "end of day", "wrap up", "we're done", "that's it for today", "log today", "done for the day", "goodnight", "shutdown", or anything that signals they're finishing a work session. If the user seems to be wrapping up, suggest running this before they go.
End of Day
This skill writes a handoff note from the current session — something Claude can read at the start of the next session to quickly understand what happened and where to pick up.
Why this matters
Without this log, the next Claude session starts with no memory of what you did today. This note is what bridges sessions together and keeps momentum going.
Step 1 — Review the session
Look back through the conversation and pull out what matters:
- What we worked on — which projects, which tasks (3–6 bullets, keep it tight)
- What was built or changed — specific files created or edited, decisions made
- Still open — anything mid-flight, unresolved, or left for later
- Start here tomorrow — 1–2 sentences on the best place to pick up next session
Write it like a note to a colleague taking over the shift — enough to orient them fast, not so much they have to read an essay. If nothing is clearly "still open," skip that section. Don't pad.
Step 2 — Save the log
Save to:
01 Daily Logs/[C] YYYY-MM-DD.md
Use this format:
---
author: claude
type: daily
date: YYYY-MM-DD
---
# Session Log — [Weekday, Month DD YYYY]
## What We Worked On
- [project — what was done]
- [project — what was done]
## What Was Built or Changed
- [specific file or decision]
- [specific file or decision]
## Still Open
- [thing that's mid-flight or unresolved]
## Start Here Tomorrow
[1–2 sentences on the best place to pick up next session]
Only include "Still Open" if there's actually something unresolved. Don't invent open items.
Step 3 — Update CLAUDE.md folder structure
Open CLAUDE.md and update the ## Folder Structure section to reflect any new folders or files created during the session. This keeps the context file accurate over time so future sessions don't work from stale information.
Only update what actually changed — don't rewrite the whole section if one folder was added.
Step 4 — Confirm
Tell the user where the file was saved and give them the "Start Here Tomorrow" line so they know the handoff is solid. Keep it to one or two lines — they're done for the day.
Related Skills
ifandisalim/new-project
tools
VerifiedTrustedCommunity
Creates a new project in the workspace with a pre-filled project overview. Trigger this skill whenever the user says "new project", "start a project", "create a project", "I want to work on something new", "add a project", or anything that signals they want to kick off a new project. Always interview the user before creating any files.
SKILL.mdUpdated Apr 22, 2026
ifandisalim/help
testing
VerifiedTrustedCommunity
Shows the user everything Claude can help with in this workspace. Trigger this skill whenever the user says "help", "what can you do?", "what can I say?", "how does this work?", "what are my options?", "I'm lost", "what now?", or seems confused about what to do next. This is especially useful right after setup when a new user doesn't know what's possible.
SKILL.mdUpdated Apr 22, 2026
ifandisalim/good-morning
development
VerifiedTrustedCommunity
Morning orientation that recaps recent work and helps decide what to work on. Trigger this skill whenever the user says "good morning", "morning", "let's get to work", "ready to start", "start my day", "what should I work on?", or anything that signals they're beginning a new work session. Use it proactively — if a user opens with a greeting at the start of a session, run this skill before doing anything else.
SKILL.mdUpdated Apr 22, 2026
openclaw/openclaw-secret-scanning-maintainer
development
VerifiedTrustedCommunity
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
357,764SKILL.mdUpdated Apr 15, 2026