4 skills that give your work with Claude memory
Did you know that after every session Claude Code forgets where you left off? That leaves you as the only memory of your projects! And that can be a problem - keeping ten things in your head at once and tracking exactly where each one stands is simply a lot. Download this free pack of 4 skills and let Claude keep things in memory instead of you.
Four small skills. Each answers one question most employees ask themselves every day anyway, and each keeps one file right in the project - so the memory doesn't live in your head.
How does a skill know when to run? From its frontmatter - a few lines at the top of the skill file - that tell Claude the skill's name and when to use it. We show it for each skill below.
1. summary - What's the next step now?
When it helps: You jump between three projects and over time you notice that each return costs you a few minutes remembering where you left off. Or you come back to unfinished work after the weekend. With summary you open the project and immediately see what the next step is.
How to use it
You wrap up a chunk of work and type /summary. A summary.md is created with the next steps right at the top. A week later you open the project and within ten seconds you know where to go next - you and the agent. No need to “remember” anything.
---
name: summary
description: Use when /summary or a chunk of work
wraps up. Writes a lightweight, next-steps-first
summary.md to the project root.
---It's a lightweight daily landing, not a decision archive. Claude often offers summary on its own when it senses you've finished something - so you don't always have to think about it.
2. daily-log - What moved this week?
When it helps: The Friday status comes around, or someone asks “what got done this week?” The daily-log skill writes it up for you, day by day.
How to use it
You tell Claude /daily-log and the skill records what moved that day into daily-log.md - by day and grouped by area. Nothing to piece together from memory, you just open the file.
---
name: daily-log
description: Use when /daily-log or you want a summary
of what changed today. Creates or updates
daily-log.md in the working directory.
---A quick overview for you and for management. It also works great as a record of how much time actually went where.
3. log-session - Where did I leave that unfinished thing?
When it helps: A week ago you started something and now you have no idea which session it was in or how to pick it up. In sessions.md you find the right line and one command takes you right back to where you stopped.
How to use it
The skill adds one line per session: the date, what it was about, and a ready-made command to reopen it (claude --resume …). In the sessions.md file you keep your whole work history together - find the session by its description and run its command.
---
name: log-session
description: Use when /log-session or you want a resume
reference to this session. Appends a dated entry
(date, time, label, resume command) to sessions.md.
---Claude Code can bring you back with --resume alone too, but that only shows a bare list of sessions with no descriptions - you can't tell which was about what. sessions.md adds that context.
4. save-status - How do I hand off my work quickly?
When it helps: You're onboarding someone to the project, or going on holiday and handing your work to a colleague. Instead of a long briefing you send STATUS.md - what's done, what was decided and why, what's next.
How to use it
You tell Claude /save-status at the end of a big stage and a STATUS.md is created - a heavy, complete snapshot of the whole project in one place.
---
name: save-status
description: Use when /save-status or you want to capture
current project state for future sessions.
Creates STATUS.md in the working directory.
---A new person (or you in a month) gets oriented on their own, without a long briefing. The difference from summary: summary is a lightweight daily landing, save-status is a heavy full snapshot for handover.
How to start using them
None of these skills is rocket science. Together they mean one thing: you stop being the only memory of your projects - less kept in your head, more actually moving forward.
Grab the pack above, unzip the four folders into ~/.claude/skills/, restart Claude Code and you have them. The full guide is in the README inside. Set them up your own way - this is just one way to do it.