Guide · Agent skill
How to use the Session History Timeline agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The session-history skill is a set of instructions for an AI agent that shows what happened in recent past sessions on a project as a reverse-chronological timeline. It is part of the agentmemory project and relies on that project's memory tool to read the records. After this guide you will know what the skill does, how to install it, how to ask for it in plain language, and what to expect from its output.
Session History Timelinerohitg00/agentmemory · Apache-2.0 Download the skill Quick start
- 1Confirm the memory tool is available. Check that the agentmemory memory_sessions function is available to your agent. Without it the skill cannot produce a history.
- 2Download the ZIP. Download the session-history ZIP from this page.
- 3Unzip into a skills folder. Unzip into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder for one project.
- 4Or upload in the Claude apps. In the Claude apps, open Settings → Capabilities → Skills and upload the ZIP.
- 5Ask in plain language. Ask "What did we do last time?" or "Show me the session history."
- 6Read the timeline. Check each session's id, start time, status and observation count against the output.
What the session-history skill makes the agent do
When you ask an agent what happened in previous sessions, this skill tells it to call the memory_sessions tool for the current project. The agent then presents the sessions the tool returns as a timeline, newest first. Each entry shows the session id, project, start time, status, observation count and key highlights.
The skill also sets a firm rule: the agent may only report past work that appears in the tool output. If the history is empty, the agent should say so rather than fill the gap from the conversation. If the list is only one page, the agent should say that the history is partial.
- Calls memory_sessions for the current project
- Shows sessions newest first with id, start time, status and observation count
- Lists key highlights (type and title) for sessions that have observations
- Surfaces a session summary and key decisions when one exists
- Never invents or merges sessions or highlights
Install the session-history skill
The skill is distributed as a ZIP file from this page. Download it and unzip it into one of two places. For a personal skill available across your projects, unzip it into ~/.claude/skills/. For a skill that only applies to one project, unzip it into that project's .claude/skills/ folder.
If you use the Claude apps instead, open Settings, then Capabilities, then Skills, and upload the ZIP there.
The skill folder includes SKILL.md (the instructions), EXAMPLES.md (worked examples) and TROUBLESHOOTING.md (recovery steps).
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside the project
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Check the requirements before you start
The skill cannot produce a history without the agentmemory memory tool. The agent needs the memory_sessions function available to it. The skill also needs a recorded project identifier or a working directory path so it can match the current project.
If memory_sessions is missing, the skill points you to TROUBLESHOOTING.md, which asks you to check the host's MCP connection and restart or reload it after configuration changes.
- agentmemory memory tool with the memory_sessions function available to the agent
- A recorded project identifier or a working directory path for scope matching
How to trigger the skill with natural requests
You do not need to type a command. The skill's description lists phrases that should activate it, so ask in plain language. The skill is user-invocable, so you can also request it directly by name.
Requests that match the skill include the phrases below. Other wordings that clearly ask for an overview of previous work should also work.
- "What did we do last time?"
- "Show me the session history."
- "Past sessions on this project, please."
- "Give me an overview of previous work."
Example: a standard timeline
Asking for the session history makes the agent call memory_sessions with the project identifier and a limit of 20. The result is shown as one line per session, with observation highlights beneath it. The worked example in EXAMPLES.md shows two completed sessions, one with 14 observations and one with 9.
- 7f3a9c2 · app · 2026-06-07 09:00 · completed · 14 obs, with decision: Rotate refresh tokens on every use
- b21d004 · app · 2026-06-05 14:00 · completed · 9 obs, with code: limit.ts counts per-IP
memory_sessions { "project": "app", "limit": 20 }Tips for reliable results
Expect the timeline to be exactly what the memory store recorded. If you need older work, ask for the full history and note that the skill works through pages of results, so very large histories may show only a partial window. For a topic search across all sessions, the skill's related recall skill is the better fit; for a grouped-by-date view, use recap.
- Ask for a specific project by name if the agent picks the wrong one
- When a window is partial, request the next page rather than assuming nothing else exists
- Use handoff to jump straight into the most recent session
- Use recall to search across all sessions by topic
What people use it for
- Picking up a project after a break and seeing what was worked on last time
- Reviewing key decisions recorded in earlier sessions on the same project
- Checking that an agent's recollection of past work matches the stored records
- Scanning recent sessions for code changes recorded as highlights
Frequently asked questions
How do I install the session-history agent skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps you can instead upload the ZIP under Settings → Capabilities → Skills.
What does the session-history skill require?
It requires the agentmemory memory tool with the memory_sessions function available to the agent, plus a recorded project identifier or a working directory path for scope matching. Without the memory tool it cannot produce a history.
Is the session-history skill free?
The skill is licensed under Apache-2.0. The source does not state pricing, so check the project's licence terms for details of use.
Does the session-history skill run scripts or use the network?
According to the listing, it runs no scripts and uses no network. It works by calling the memory_sessions tool.
Why does the skill show only some of my sessions?
The skill works on paged results. If there are very large histories it may show only a partial window, and it will say so. Request the next page to see more.
What should I do if the agent says memory_sessions is not available?
Follow TROUBLESHOOTING.md. Check the host's MCP connection, such as /mcp in Claude Code, and restart or reload the connection after configuration changes.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you work with agentmemory on a project and want an accurate, reviewable record of earlier sessions that never includes invented work. Pick something else if you need a general-purpose diary or guaranteed completeness across very large histories, or if you do not have the agentmemory memory tool running.
Download the skill