AGENT SKILL

digest

Print AI coding sessions for a calendar day as Obsidian-compatible markdown with the full Q&A content of every session. Intended for daily-note workflows: paste the output into a daily journal to preserve a searchable record of what was discussed with which AI tool. Use this skill when asked to dump today's sessions as markdown, prepare a daily-note entry, archive Q&A for Obsidian, or export a calendar-day's coding conversations. Trigger phrases: "digest today's sessions", "dump sessions as markdown", "obsidian daily note", "archive my coding chats", "export today's Q&A", "session log for daily note".

License 许可
MIT
所属仓库
psacc/omnisess
最近更新
2026-11-12
Stars
★ 1
Forks
1

01 前言 Front Matter

name
digest
license
MIT
metadata
{ "version": "0.13.0" }
description
Print AI coding sessions for a calendar day as Obsidian-compatible markdown with the full Q&A content of every session. Intended for daily-note workflows: paste the output into a daily journal to preserve a searchable record of what was discussed with which AI tool. Use this skill when asked to dump today's sessions as markdown, prepare a daily-note entry, archive Q&A for Obsidian, or export a calendar-day's coding conversations. Trigger phrases: "digest today's sessions", "dump sessions as markdown", "obsidian daily note", "archive my coding chats", "export today's Q&A", "session log for daily note".
allowed-tools
Bash
argument-hint
[--date YYYY-MM-DD] [--tool <name>] [--limit N]

02 资源文件 4

03 SKILL.md 正文

omnisess digest

Print sessions for a calendar day with full Q&A content as Obsidian-compatible markdown.

Usage

omnisess digest [--date YYYY-MM-DD] [--tool <name>] [--limit N]
  • Defaults to today when no --date is given (daily-note helper).
  • Honors all standard filters: --tool, --project, --exclude-project, --limit.
  • Output is rune-safe UTF-8 (Italian accents, emoji, CJK render correctly).

Output format

## AI sessions — 2026-05-09  (3 sessions)

### First user message (truncated to 80 chars)
_project: `~/dev/myproject` · tool: claude_

**Q [09:00]:** user question...

_[tools: Bash, Read]_

**A [09:01]:**
assistant response...

---

### Next session title
...

Features:

  • Sessions separated by --- and sorted by start time.
  • Tool-call-only assistant turns collapsed to _[tools: Name, …]_.
  • Turns truncated at 2000 runes with a _(truncated)_ marker.
  • $HOME substituted with ~ (only when project equals or sits below $HOME).

Instructions

  1. Check that the omnisess binary 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
  1. Run the command, passing through all arguments:
omnisess digest "$@"

Examples

# Today's sessions across all tools (default)
omnisess digest

# A specific day
omnisess digest --date 2026-05-09

# One tool only
omnisess digest --tool claude

# Cap to the most recent N sessions of the day
omnisess digest --date 2026-05-09 --limit 5

04 同仓库更多 Skills

psacc
psacc/omnisess

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

★ 1
psacc
psacc/omnisess

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.

★ 1
psacc
psacc/omnisess

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

★ 1
psacc
psacc/omnisess

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

★ 1
psacc
psacc/omnisess

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.

★ 1
psacc
psacc/omnisess

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.

★ 1