New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Session History Timeline

by rohitg00 in rohitg00/agentmemory

Shows a clean, reverse-chronological timeline of recent sessions on a project, using only the data a memory tool actually returned, never a remembered summary.

Apache-2.0Auto-check passedAgent Workflows

Install Session History Timeline

skills CLI
$ npx skills add rohitg00/agentmemory --skill session-history -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rohitg00/agentmemory session-history --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rohitg00/agentmemory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugin/skills/session-history .claude/skills/session-history && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
session-history
GitHub stars
29k
Token cost
~465 tokens
SKILL.md length
193 words
Files
2
Skills in repo
17
Repo updated
First seen
Licence
Apache-2.0

At a glance

Shows a clean, reverse-chronological timeline of recent sessions on a project, using only the data a memory tool actually returned, never a remembered summary.

  • Works in 5 steps: Call memory_sessions with limit: 20 for… → Present in reverse chronological order:… → For sessions with observations, show the… → …
  • Asking what happened in previous sessions on this project
  • SKILL.md covers Quick start, Why, Workflow and Anti-patterns, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

A single call to memory_sessions with a limit of 20 gives a meaningful window of recent work, which the skill then presents in reverse chronological order: each session's short ID, project, start time and status, followed by key highlights for any session that has observations, and the total observation count for that session. When a stored session summary exists, its title and key decisions are surfaced too.

The explicit anti-pattern is inventing continuity: if the tool returns only two sessions, the right answer describes exactly those two sessions with their real IDs, statuses and counts, not a vague gloss like several sessions of steady progress padded out with details remembered from the conversation. An empty history is treated as a real, valid answer rather than a cue to make something up.

A short checklist enforces this before responding: every session shown came from the tool's actual response, the order is reverse-chronological, per-session counts match what came back, and nothing was invented or merged. Related skills cover the same data differently: recap groups it by date, handoff jumps straight into the most recent session, and recall searches across all sessions by topic.

When your agent uses it

  • Asking what happened in previous sessions on this project
  • Getting a quick timeline of recent work before resuming it
  • Checking exactly how many sessions and observations exist, with no guessing

Example prompts

  • “What did we do last time on this project?”
  • “Show me the session history for the last 20 sessions.”
  • “Give me an overview of previous work on the billing module.”

Requirements

  • A memory_sessions tool backed by stored session data

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Call memory_sessions with limit: 20 for a meaningful window.
  2. Present in reverse chronological order: session id (first 8), project, start
  3. For sessions with observations, show the key highlights (type plus title).
  4. Note the total observation count per session.
  5. When a session summary exists, surface its title and the key decisions.

What it can do on your machine

Read from SKILL.md and the folder at commit 9caace6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Session History Timeline loads about 465 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 193 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~465

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rohitg00/agentmemory at commit 9caace6, republished under its Apache-2.0 licence (© rohitg00). 193 words, ~465 tokens.

Download SKILL.mdSave it as .claude/skills/session-history/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
session-history
description
Show what happened in recent past sessions on this project as a clean timeline. Use when the user asks "what did we do last time", "session history", "past sessions", or wants an overview of previous work.
user-invocable
true

The user wants an overview of recent sessions on this project.

Quick start

json
memory_sessions { "limit": 20 }

Expected output:

text
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

  1. Call memory_sessions with limit: 20 for a meaningful window.
  2. Present in reverse chronological order: session id (first 8), project, start time, status.
  3. For sessions with observations, show the key highlights (type plus title).
  4. Note the total observation count per session.
  5. 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.

© rohitg00, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugin/skills/session-history of rohitg00/agentmemory.

  • SKILL.md
  • EXAMPLES.md

Open the folder on GitHubat commit 9caace6

Compare with similar skills

Session History Timeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Session History Timeline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Session History Timeline this skillrohitg00/agentmemory29k—~465Automated safety check: PassApache-2.0
Beads Task Memorygastownhall/beads28k—~1.2kAutomated safety check: PassMIT
Session History Searchslopus/happy24k—~3.1kAutomated safety check: PassMIT
Memori Long-Term MemoryMemoriLabs/Memori17k—~2kAutomated safety check: NotesCustom licence
Coding Agent Session Findercode-yeongyu/oh-my-openagent70k—~2.8kAutomated safety check: PassCustom licence
Memori MCP Memory UsageMemoriLabs/Memori17k—~3.8kAutomated safety check: PassMIT

Similar skills

  • Beads Task Memory

    gastownhall/beads

    Tracks multi-session work with dependencies in the bd issue tracker so the agent can find ready tasks and recover its context after conversation compaction.

    28k GitHub stars~1.2k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Session History Search

    slopus/happy

    Searches past Claude Code, Codex and Cursor sessions and summarizes what was worked on, tried or decided, using extraction scripts instead of reading raw logs.

    24k GitHub stars~3.1k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Memori Long-Term Memory

    MemoriLabs/Memori

    Connects Claude Code to Memori Cloud for long-term memory, recalling stored context before substantive replies and saving new context afterward.

    17k GitHub stars~2k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check: notes

  • Coding Agent Session Finder

    code-yeongyu/oh-my-openagent

    Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.

    70k GitHub stars~2.8k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Memori MCP Memory Usage

    MemoriLabs/Memori

    Teaches an MCP-connected agent when and how to call Memori's recall, summary, compaction, augmentation, feedback and quota tools to keep context across sessions.

    17k GitHub stars~3.8k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed

  • Ourmem

    ourmem/omem

    Shared memory that never forgets. An agent skill from ourmem/omem.

    174 GitHub starsUsed in 1 repo~3.4k tokens
    Agent WorkflowsAuto-check passed

More from rohitg00/agentmemory

All 17 skills in this repo

  • agentmemory Setup and Diagnostics

    rohitg00/agentmemory

    Sets up and troubleshoots a local agentmemory install, covering the MCP connection, environment variables, ports, authentication and optional feature flags.

    29k GitHub stars~1k tokensUpdated today
    Auto-check: notes

  • Commit Context Lookup

    rohitg00/agentmemory

    Traces a file, function or line back to the agent session behind its current commit, using git blame and a memory lookup, and reports only what the records show.

    29k GitHub stars~522 tokensUpdated today
    Auto-check passed

  • Agent Commit History

    rohitg00/agentmemory

    Lists recent git commits linked to agent sessions, filterable by branch, repository or a result limit, showing the session id and observation count behind each one.

    29k GitHub stars~524 tokensUpdated today
    Auto-check passed

  • Agentmemory Forget

    rohitg00/agentmemory

    Deletes chosen memories from agentmemory only after showing the matches and getting an explicit yes, for privacy requests and cleanup of outdated notes.

    29k GitHub stars~612 tokensUpdated today
    Auto-check passed

  • Session Handoff Resume

    rohitg00/agentmemory

    Resumes the most recent agent session for the current directory, leading with any question left unanswered and ending with a concrete next step.

    29k GitHub stars~678 tokensUpdated today
    Auto-check passed

  • Lesson Memory Recorder

    rohitg00/agentmemory

    Distills a user correction or hard-won rule into a confidence-weighted lesson that resurfaces automatically before similar future work.

    29k GitHub stars~721 tokensUpdated today
    Auto-check passed

Categories

Questions about Session History Timeline

What does Session History Timeline do?

Shows a clean, reverse-chronological timeline of recent sessions on a project, using only the data a memory tool actually returned, never a remembered summary. A single call to memory_sessions with a limit of 20 gives a meaningful window of recent work, which the skill then presents in reverse chronological order: each session's short ID, project, start time and status, followed by key highlights for any session that has observations, and the total observation count for that session. When a stored session summary exists, its title and key decisions are surfaced too.

When should I use Session History Timeline?

Session History Timeline fits situations like: asking what happened in previous sessions on this project; getting a quick timeline of recent work before resuming it; checking exactly how many sessions and observations exist, with no guessing.

How do I install Session History Timeline in Claude Code?

Run `npx skills add rohitg00/agentmemory --skill session-history -a claude-code`. Or copy the skill folder (plugin/skills/session-history in rohitg00/agentmemory) into .claude/skills/session-history in your project. Claude Code loads it when a task matches its description.

How do I install Session History Timeline in Codex?

Run `npx skills add rohitg00/agentmemory --skill session-history -a codex`. Or copy the skill folder (plugin/skills/session-history in rohitg00/agentmemory) into .agents/skills/session-history in your project. Codex loads it when a task matches its description.

Can I use Session History Timeline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rohitg00/agentmemory --skill session-history -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/session-history, .gemini/skills/session-history, .github/skills/session-history and .opencode/skills/session-history in your project.

What does Session History Timeline need to run?

SKILL.md names no scripts, command-line tools or credentials: Session History Timeline is instructions for the agent only. Our summary lists: A memory_sessions tool backed by stored session data.

Does Session History Timeline access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Session History Timeline safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Session History Timeline use?

Session History Timeline is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Session History Timeline use?

About 465 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Session History Timeline?

Skills that share tags, products or a category with Session History Timeline: Beads Task Memory (gastownhall/beads, 28k stars), Session History Search (slopus/happy, 24k stars), Memori Long-Term Memory (MemoriLabs/Memori, 17k stars) and Coding Agent Session Finder (code-yeongyu/oh-my-openagent, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Session History Timeline?

rohitg00 (a GitHub user) maintains it in rohitg00/agentmemory, which has 29,272 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 10, 2026.

Source: rohitg00/agentmemory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.