session-history
This skill provides a clear timeline of recent project sessions, enabling users to quickly review past work. It's particularly useful when a user asks 'what did we do last time', 'session history', or wants an overview of previous work. By presenting concise session records, this Skill significantly enhances work efficiency and improves contextual understanding for ongoing projects.
npx skills add https://github.com/rohitg00/agentmemory --skill session-historyBefore / After Comparison
1 组Without this skill, users had to manually review extensive logs or chat histories, spending significant time recalling or searching for past session content and key decisions. This often resulted in lost context and reduced productivity.
This Skill automatically organizes and presents a clear session timeline, allowing users to quickly access key information and decision points. This significantly reduces review time and ensures consistent project context.
The user wants an overview of recent sessions on this project.
Quick start
memory_sessions { "limit": 20 }
Expected output:
7f3a9c2 · app · 2026-06-07 09:00 · completed · 14 obs
- decision: Rotate refresh tokens on every use
b21d004 · app · 2026-06-05 14:00 · completed · 9 obs
- code: limit.ts counts per-IP
Why
Only show sessions and observations the tool returned. An empty history is a real answer, never a cue to invent past work.
Workflow
- Call
memory_sessionswithlimit: 20for a meaningful window. - Present in reverse chronological order: session id (first 8), project, start time, status.
- For sessions with observations, show the key highlights (type plus title).
- Note the total observation count per session.
- When a session summary exists, surface its title and the key decisions.
Anti-patterns
WRONG: the tool returns two sessions, you describe "several sessions of steady progress" and add ones you remember from the conversation.
RIGHT: show exactly the two sessions returned, each with its real id, status, and observation count.
Checklist
- Every session shown came from the tool response.
- Order is reverse-chronological.
- Per-session observation counts match the response.
- No session or highlight was invented or merged.
See also
recap: same data grouped by date with highlights.handoff: jump straight into the most recent session.recall: search across all sessions by topic.
Troubleshooting
See ../_shared/TROUBLESHOOTING.md if memory_sessions is not available.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill