tool-usagelisted

Query the tool-monitor database to look up and analyze Claude tool usage. Use when asked about tool usage statistics, which tools have been used most, recent tool activity, bash commands run, files read or edited, grep patterns searched, session analysis, or any question about how Claude has been using its tools.
richardkmichael/claude-rodin · ★ 0 · Data & Documents · score 75

Install: claude install-skill richardkmichael/claude-rodin

# Tool Usage The tool-monitor database records every Claude Code tool invocation. Database: `~/.claude/tool-monitor.sqlite` ## tool_events table | Column | Type | Notes | |-------------------|----------|---------------------------------------------------------------------------| | `id` | INTEGER | Primary key | | `session_id` | TEXT | Groups events by conversation session | | `hook_event_name` | TEXT | `PreToolUse`, `PostToolUse`, `PostToolUseFailure`, or `PermissionRequest` | | `tool_name` | TEXT | e.g. `Bash`, `Read`, `Grep`, `Edit`, `Write`, `Glob`, `Task` | | `cwd` | TEXT | Working directory at time of invocation | | `transcript_path` | TEXT | Path to the session transcript file | | `created_at` | DATETIME | Timestamp | | `payload` | TEXT | Full JSON payload (all fields above, plus `tool_input` and more) | Tool-specific input fields live inside `payload` and are accessed with `json_extract`: ```sql json_extract(payload, '$.tool_input.command') -- Bash: the shell command json_extract(payload, '$.tool_input.file_path') -- Read/Write: file path json_extract(pa