Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Query and analyze Claude Code session data from a remote server. Use when asked to inspect Claude Code sessions, view conversation history, check tool calls,...
Query and analyze Claude Code session data from a remote server. Use when asked to inspect Claude Code sessions, view conversation history, check tool calls,...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Access and analyze Claude Code session data from a remote ccsinfo server running on the user's machine. Server Repository: https://github.com/myk-org/ccsinfo
The ccsinfo server must be running on the machine that has Claude Code session data. Install and run the server: # Install ccsinfo uv tool install git+https://github.com/myk-org/ccsinfo.git # Start the server (accessible on LAN) ccsinfo serve --host 0.0.0.0 --port 9999 The server reads Claude Code session data from ~/.claude/projects/ and exposes it via REST API. For full server documentation, see: https://github.com/myk-org/ccsinfo
The ccsinfo CLI tool must be installed. Check if installed: which ccsinfo If not installed, run the installation script: bash scripts/install.sh
Set the CCSINFO_SERVER_URL environment variable to point to your server: export CCSINFO_SERVER_URL=http://192.168.1.100:9999 Add this to your shell profile (.bashrc, .zshrc, etc.) to persist across sessions.
All commands automatically connect to the remote server via $CCSINFO_SERVER_URL.
ccsinfo sessions list
ccsinfo sessions show <session-id>
ccsinfo sessions messages <session-id>
ccsinfo search sessions "search term"
ccsinfo stats global
List sessions to find the ID: ccsinfo sessions list Show session details: ccsinfo sessions show <id> View messages: ccsinfo sessions messages <id> Check tool calls: ccsinfo sessions tools <id>
# Search across all sessions ccsinfo search sessions "refactor" # Search message content ccsinfo search messages "fix bug" # Search prompt history ccsinfo search history "implement feature"
# Show all pending tasks ccsinfo tasks pending # List tasks for a session ccsinfo tasks list -s <session-id> # Show specific task details ccsinfo tasks show <task-id> -s <session-id>
# Overall usage stats ccsinfo stats global # Daily activity breakdown ccsinfo stats daily # Analyze trends over time ccsinfo stats trends
# List all projects ccsinfo projects list # Show project details ccsinfo projects show <project-id> # Project statistics ccsinfo projects stats <project-id>
Most commands support --json for machine-readable output: ccsinfo sessions list --json ccsinfo stats global --json This is useful for parsing results programmatically or filtering with jq.
Session IDs support partial matching - use the first few characters: ccsinfo sessions show a1b2c3 # matches a1b2c3d4-e5f6-7890-abcd-ef1234567890
For complete command reference, see cli-commands.md.
# Verify server URL is set echo $CCSINFO_SERVER_URL # Test connection (list sessions) ccsinfo sessions list
# Check if ccsinfo is installed which ccsinfo # Check version ccsinfo --version
bash scripts/install.sh
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.