stats
Show tool-call counts and file-I/O activity from the transcript SQLite index. Aggregates Read/Write/Edit file paths, line counts, token usage, and error flags across a time window (default 7d) or for a single session. Use this skill when asked which tools were used most, which files saw the most activity, how many tokens were spent, or to inspect a single session's tool-call summary. Trigger phrases: "session stats", "tool stats", "what tools did I use", "tool usage", "files touched", "token usage", "stats for last week", "summarize tool calls", "session tool breakdown".
- License 许可
- MIT
- 所属仓库
- psacc/omnisess
- 最近更新
- 2026-11-12
- Stars
- ★ 1
- Forks
- 1
01 前言 Front Matter
- name
- stats
- license
- MIT
- metadata
- { "version": "0.13.0" }
- description
- Show tool-call counts and file-I/O activity from the transcript SQLite index. Aggregates Read/Write/Edit file paths, line counts, token usage, and error flags across a time window (default 7d) or for a single session. Use this skill when asked which tools were used most, which files saw the most activity, how many tokens were spent, or to inspect a single session's tool-call summary. Trigger phrases: "session stats", "tool stats", "what tools did I use", "tool usage", "files touched", "token usage", "stats for last week", "summarize tool calls", "session tool breakdown".
- allowed-tools
- Bash
- argument-hint
- [--session <id>] [--window <duration>] [--tool <name>] [--full] [--json]
03 SKILL.md 正文
omnisess stats
Aggregate tool counts and file-I/O activity from the transcript SQLite index.
Usage
omnisess stats [--session <id>] [--window <duration>] [--tool <name>] [--full] [--json]
--sessionand--windoware mutually exclusive.- Without
--session, aggregates over a time window (default7d). --toolfilters to one source (currently onlyclaudeis supported).--fullis required to surface argument/result payloads — and only works if the index was previously populated withomnisess index --all --full.--jsonemits machine-readable output suitable forjq.
Prerequisites
The transcript index is populated lazily on first use, but for bulk runs it is faster to seed it once:
omnisess index --all
The index lives at os.UserCacheDir() + /omnisess/index.sqlite by default;
override via OMNISESS_INDEX_PATH.
Instructions
- Check that the
omnisessbinary is available:
if ! command -v omnisess &>/dev/null; then
echo "omnisess not found. Install it with:"
echo " go install github.com/psacc/omnisess@latest"
exit 1
fi
- Run the command, passing through all arguments:
omnisess stats "$@"
Examples
# Last 7 days, default window
omnisess stats
# Last 30 days
omnisess stats --window 30d
# Single session detail
omnisess stats --session claude:5c3f2742
# JSON for scripting
omnisess stats --window 7d --json | jq .
# Capture full arguments + result payloads (privacy-sensitive)
omnisess index --all --full
omnisess stats --session claude:5c3f2742 --full
04 同仓库更多 Skills
skills-audit
Classify agent skills by usage tier (Keep / Borderline / Archive / Unknown) using Claude Code session JSONL transcripts as the signal source. Read-only — never modifies skills, sessions, or any file on disk. Use this skill when asked to audit skills, find unused skills, classify skills, check which skills get used, produce a skill usage report, or prune skills. Trigger phrases: "audit skills", "find unused skills", "classify skills", "which skills do I use", "skill usage report", "prune skills", "what skills are unused", "skills I can remove", "trim my skill list". Output is a recommendation (Keep / Borderline / Archive) — acting on it is always a manual step.
show
Show the full detail of a single AI coding session by its ID. Session IDs are in the format <tool>:<id> (e.g., claude:5c3f2742, cursor:a1b2c3d4). Use this skill when asked to show a specific session, inspect a session, read a session, or view the messages in a session. Trigger phrases: "show session", "open session", "inspect session", "read session", "show me claude:5c3f2742", "view session details", "what happened in session".
search
Full-text search across all AI coding sessions (Claude Code, Cursor, Codex, GitHub Copilot CLI). Use this skill when asked to search sessions, find a conversation about a topic, look up what was discussed in past sessions, or find sessions mentioning specific code or concepts. Trigger phrases: "search sessions", "find sessions about", "look up in sessions", "what did I discuss about", "find conversation about", "search my history".
recap
Produce a structured markdown briefing of AI coding sessions for a given time window. Groups sessions by project and summarizes each group with intent, outcome, and status. Use this skill when asked to recap recent coding work, summarize today's sessions, show what was worked on, or produce a daily/weekly session summary. Trigger phrases: "recap", "what did I work on", "daily summary", "session summary", "summarize my sessions", "what sessions did I have today", "coding recap". This is the sessions-only public version — no Slack, Jira, or Granola integration.
ps
Show live Claude Code and Codex sessions as a process tree, grouped by shared ancestor chain up to launchd. Covers Claude CLI sessions, Claude Desktop agent mode, and Codex sessions (CLI TUI + Codex.app threads). Use this skill when asked about the process tree, ancestor lineage, which terminal or tmux window a Claude or Codex session is running in, or what's currently running. Trigger phrases: "process tree", "what's running", "lineage", "ancestor chain", "which terminal is my claude in", "tmux tree", "claude process tree", "codex process tree", "session lineage". macOS-only: on other platforms the command prints "unsupported" and exits 0.
list
List AI coding sessions across all sources (Claude Code, Cursor, Codex, GitHub Copilot CLI). Use this skill when asked to list sessions, show recent sessions, filter sessions by tool, or get an overview of coding activity. Trigger phrases: "list sessions", "show sessions", "recent sessions", "sessions from cursor", "sessions today", "how many sessions", "show me my sessions".