← ClaudeAtlas

agent-insightslisted

Generate a cross-tool usage insights report from locally stored AI coding agent sessions (Claude Code, Claude Cowork, GitHub Copilot for VS Code/CLI/JetBrains, Cursor, Codex, Kiro, Antigravity, OpenCode) over the last N days, default 30. Use when the user invokes /agent-insights, asks for insights, analytics, or a report on their agent sessions, asks how they're using their coding agents or what's working or causing friction, wants to compare their coding agent tools, or asks what their AI coding patterns look like, even when they don't say "report".
kevinlin/skills · ★ 3 · AI & Automation · score 74
Install: claude install-skill kevinlin/skills
# agent-insights Cross-tool version of Claude Code's builtin `/insights`. Everything runs locally; no session data leaves the machine. `SKILL_DIR` below means this skill's directory; `SCRIPT` means `python3 <SKILL_DIR>/scripts/agent_insights.py`. All intermediate files live in `~/.agent-insights/` (override with `--data-dir` on every subcommand, e.g. for tests). ## Arguments One optional argument: number of days to analyze. Default 30, clamp to 1..365. Non-numeric input: tell the user, then proceed with 30. ## Pipeline ### Step 0 — Detect runtime ```bash SCRIPT detect ``` Detects whether this skill is running on the host machine (where the user's agent logs live) or inside a **sandboxed runtime** such as Claude Cowork, whose Bubblewrap container does not mount the host filesystem. Reads the JSON result: - If `sandboxed` is `false`, continue to Step 1. - If `sandboxed` is `true`, the host machine's agent log directories are **not reachable** from this runtime. Do **not** run a full report from here: it would be empty or cover only the sandbox's own session. Instead, tell the user: - the detected `runtime` and `confidence`, and the `signals` that fired; - the `recommendation` verbatim (run `/agent-insights` from a non-sandboxed agent with direct host access, e.g. Claude Code in the terminal); - `reachable_sources` (what little, if anything, is visible from inside the sandbox). Then stop, unless the user explicitly asks to analyze only what is reachable