Ccsinfo

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,...

Security Scan

The skill is internally coherent: it wraps a ccsinfo CLI to query a remote ccsinfo server (pointed to by CCSINFO_SERVER_URL) and does not request unrelated credentials or hidden capabilities — but running the server as recommended can expose sensitive Claude Code session data if not properly secured.

Purpose & Capability

The name/description, required binary (ccsinfo), and required environment variable (CCSINFO_SERVER_URL) align with the declared purpose of querying a remote ccsinfo server. The included wrapper and install scripts are consistent with providing a CLI client.

Instruction Scope

SKILL.md instructs the agent to invoke the ccsinfo CLI against the server URL and does not ask the agent to read unrelated local files or credentials. However, the documentation instructs running the server with access to ~/.claude/projects/ and suggests binding to 0.0.0.0, which would expose local Claude Code session data on the LAN; that is a privacy/security concern even though it is consistent with the skill's purpose.

Install Mechanism

No remote download-from-arbitrary-URL occurs in the skill bundle itself. The provided install script uses the 'uv' tool manager to install the ccsinfo package (uv tool install ccsinfo), which is a standard package-install approach (PyPI/git are referenced in docs). This is a moderate-risk but expected install mechanism; it requires trusting the ccsinfo package source and the 'uv' tool.

Credentials

Only CCSINFO_SERVER_URL is required and matches the skill's need to know where to contact the server. No unrelated secret environment variables or config paths are requested. Note: examples use http (not https) which may expose data in transit unless the server is configured for TLS.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or system-wide settings. It requires a CLI binary and an env var but does not demand elevated privileges or permanent forced inclusion.

Assessment

This skill appears to do what it says, but before installing: 1) Verify the ccsinfo server code (GitHub/PyPI package) yourself — it will read ~/.claude/projects/ and therefore has access to your conversation history. 2) Avoid running the server bound to 0.0.0.0 on untrusted networks; prefer localhost or use firewall rules, TLS, and authentication. 3) Confirm the CCSINFO_SERVER_URL points to a trusted, private endpoint and does not embed credentials. 4) Ensure you trust the 'uv' package manager and the ccsinfo package source before running scripts/install.sh. If you cannot review the server code or cannot secure the server endpoint, treat the data exposure risk as significant.

ccsinfo - Claude Code Session Info

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

Requirements

1. Server Setup (on the machine with Claude Code data)

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

2. Client Setup (where this skill runs)

The ccsinfo CLI tool must be installed. Check if installed:

which ccsinfo

If not installed, run the installation script:

bash scripts/install.sh

3. Configuration

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.

Quick Start

All commands automatically connect to the remote server via $CCSINFO_SERVER_URL.

List recent sessions

ccsinfo sessions list

Show session details (supports partial ID matching)

ccsinfo sessions show <session-id>

View conversation messages

ccsinfo sessions messages <session-id>

Search sessions by content

ccsinfo search sessions "search term"

View global statistics

ccsinfo stats global

Common Workflows

Inspect a specific session

1. List sessions to find the ID:

   ccsinfo sessions list
   

2. Show session details:

   ccsinfo sessions show <id>
   

3. View messages:

   ccsinfo sessions messages <id>
   

4. Check tool calls:

   ccsinfo sessions tools <id>
   

Find sessions by content

# Search across all sessions
ccsinfo search sessions "refactor"

# Search message content
ccsinfo search messages "fix bug"

# Search prompt history
ccsinfo search history "implement feature"

Track tasks

# 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>

View statistics and trends

# Overall usage stats
ccsinfo stats global

# Daily activity breakdown
ccsinfo stats daily

# Analyze trends over time
ccsinfo stats trends

Work with projects

# List all projects
ccsinfo projects list

# Show project details
ccsinfo projects show <project-id>

# Project statistics
ccsinfo projects stats <project-id>

Output Formats

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 ID Matching

Session IDs support partial matching - use the first few characters:

ccsinfo sessions show a1b2c3  # matches a1b2c3d4-e5f6-7890-abcd-ef1234567890

Reference

For complete command reference, see cli-commands.md.

Troubleshooting

Check server connectivity

# Verify server URL is set
echo $CCSINFO_SERVER_URL

# Test connection (list sessions)
ccsinfo sessions list

Verify installation

# Check if ccsinfo is installed
which ccsinfo

# Check version
ccsinfo --version

Reinstall if needed

bash scripts/install.sh