extracting-session-data

Malicious tool definition detected

Tool: README.md [1/2] Description: # Extracting Session Data Skill Locates, lists, filters, and extracts structured data from Claude Code session logs.

Tool: README.md [2/2] Description: your sessions contained sensitive data: - Session logs are stored locally only - You control access to `~/.claude/projects/` directory - Be cautious when sharing extracted data - Consider project-specific access controls ## Error Handling All scripts exit with non-zero status on errors and output messages to stderr.

Malicious tool definition detected

Tool: SKILL.md [1/2] Description: --- name: extracting-session-data description: Locates, lists, filters, and extracts structured data from Claude Code native session logs. Supports both single and multiple session analysis.

Tool: SKILL.md [2/2] Description: abc123 &>/dev/null; then # Handle: session doesn't exist echo "Session not found" fi ``` Common error messages: - `Error: Logs directory not found: ~/.claude/projects/-path` - `Error: Session file not found: ~/.claude/projects/-path/session-id.jsonl` - `Error: --type is required` - `Error: jq is required but not installed.

Malicious tool definition detected

Tool: scripts/extract-data.sh Description: #!/bin/bash # extract-data.sh - Extract structured data from Claude Code session logs # Usage: ./extract-data.sh --type TYPE [--session SESSION_ID] [options] # # Extracts specific data types from one or more session log files set -e SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" # Check dependencies if !

Malicious tool definition detected

Tool: scripts/filter-sessions.sh [1/2] Description: #!/bin/bash # filter-sessions.sh - Filter Claude Code sessions by various criteria # Usage: ./filter-sessions.sh [options] # # Filters session logs based on date, branch, size, errors, or content set -e SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" # Check dependencies if !

Tool: scripts/filter-sessions.sh [2/2]

Malicious tool definition detected

Tool: scripts/list-sessions.sh Description: #!/bin/bash # list-sessions.sh - List available Claude Code sessions with metadata # Usage: ./list-sessions.sh [project-directory] [options] # # Lists all session log files with metadata (ID, size, date, branch, lines) set -e SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)" # Default options OUTPUT_FORMAT="table" # table, json, csv SORT_BY="date" # date, size, lines # Parse arguments PROJECT_DIR="${PWD}" while [[ $# -gt 0 ]]; do case

Malicious tool definition detected

Tool: scripts/locate-logs.sh Description: #!/bin/bash # locate-logs.sh - Find Claude Code session log paths # Usage: ./locate-logs.sh [project-directory] [session-id] # # Returns the path to session logs directory or specific session log file # If no arguments provided, uses current working directory set -e # Calculate project identifier from working directory calculate_project_dir() { local work_dir="$1" echo "${work_dir}" | sed 's/\//\-/g' } # Get session logs directory get_logs_directory() {