Skill

get-history

Access raw conversation history from Claude Code session storage for analysis

From cat
Install
1
Run in your terminal
$
npx claudepluginhub cowwoc/cat --plugin cat
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Get History Skill

Purpose: Provide direct access to raw conversation history stored by Claude Code for debugging and conversation analysis.

When to Use:

  • When investigating tool call sequences
  • To verify what happened earlier in a session
  • When analyzing agent behavior patterns
  • To debug unexpected outcomes

Skill Capabilities

1. Access Current Session Conversation

Location: /home/node/.config/projects/-workspace/{session-id}.jsonl

Session ID: The session ID is automatically available as ${CLAUDE_SESSION_ID} in this skill.

cat /home/node/.config/projects/-workspace/${CLAUDE_SESSION_ID}.jsonl

2. Parse Conversation Structure

Entry Types:

  • type: "summary" - High-level conversation summary
  • type: "message" - User or assistant messages
  • type: "tool_use" - Tool invocations
  • type: "tool_result" - Tool outputs

Extract Messages:

# Get all user messages
jq 'select(.type == "message" and .role == "user") | .content' conversation.jsonl

# Get all tool uses with names
jq 'select(.type == "tool_use") | {name: .name, input: .input}' conversation.jsonl

3. Agent Sidechain Conversations

Path Pattern: /home/node/.config/projects/-workspace/agent-{agent-id}.jsonl

# Find all agent sidechain logs
ls -lht ~/.config/projects/-workspace/agent-*.jsonl | head -10

Error Handling

If session ID not in context, report error - do NOT guess.

Integration

Complements learn-from-mistakes:

  • get-history: Provides raw conversation data
  • learn-from-mistakes: Analyzes mistakes and recommends fixes
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Parent Repo Stars78
Parent Repo Forks1
Last CommitFeb 13, 2026