skills.rest
Acosmi
AcosmiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sessions-history

Retrieve conversation history from other sessions using a sessionKey and optional limit.

6|Updated Feb 26, 2026
Search Tags:#logging#audit#agent#debug#conversations#session-history#retrieve
One-click install
npx skills add https://github.com/Acosmi/CrabClaw --skill sessions-history
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sessions-history
Source: https://github.com/Acosmi/CrabClaw/tree/main/docs/skills/tools/sessions/sessions-history
Command: npx skills add https://github.com/Acosmi/CrabClaw --skill sessions-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables auditors and developers to retrieve conversation history from other sessions or sub-agents, facilitating review and debugging of AI behavior.

Core Features & Use Cases

  • Retrieve conversation history across multiple sessions for audit, debugging, and compliance.
  • Provide bounded results with an optional limit to maintain performance.
  • Use Case: Imagine investigating a misbehaving sub-agent; you fetch its recent messages to trace decisions and verify context continuity.

Quick Start

Provide a target session key via the tool to fetch its recent messages (with an optional limit).

Frequently Asked Questions about sessions-history

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve conversation history from another agent session for auditing?▼

You can retrieve agent conversation history by providing a target session key. This fetches prior interactions from another session or sub-agent, enabling you to trace decisions and verify context continuity for debugging.

What is the best way to debug a misbehaving sub-agent's prior interactions?▼

Fetching cross-session conversation history is the best way to debug a misbehaving sub-agent. By retrieving its recent messages with a session key, you can verify behavior and trace its decision paths across interactions.

Can I cap the number of messages returned when retrieving session history?▼

Yes, you can cap the number of messages returned by applying an optional limit parameter. This ensures bounded results, maintaining performance when you retrieve large cross-session conversation histories.

Does retrieving cross-session history require any specific environment setup?▼

Retrieving cross-session history requires no specific environment setup, but you must supply a valid sessionKey. This identifier targets the specific session or sub-agent whose conversation logs you need to audit.

Why do I need a session key to trace agent decision paths across multiple sessions?▼

A session key is required to trace decision paths because it uniquely identifies the target session. Without this key, the system cannot locate the specific conversation history needed for your audit or debugging task.

Related Skills

Explore More Software Engineering Skills→
wangqianCAIwangqianCAI

session-logs

Search and analyze JSONL conversation logs with jq and ripgrep.

Community
Intermediate
hongmaple0820hongmaple0820
9

session-logs

Parse JSONL session logs to extract messages by role with jq.

Community
Intermediate
riethmayerriethmayer
2

trace

Visualize chronological event timelines of hooks, keywords, skills, agents, and tools.

Community
Intermediate
portermetricsampleportermetricsample
17

conversion-tracking-audit

Audit Google Ads conversion action configurations for tracking and bidding gaps.

Community
Advanced