Analyze conversation histories from multiple AI tools (Grok, Claude, Codex, Gemini, Qwen, Cursor, Antigravity) and generate themed daily/period work summaries. Filter by date or time window.
SkillScore55Maintained
Automatic
◆Project Management pack
Last verified 8/17/2026
What it changes
Passed 9 of 16 test cases with the skill, and 4 of 16 without it.
Without skill27%
With skill55%
Checks it passed that the model alone missed
restricts the top TL;DR section to a maximum of 3 lines
suggests productivity metric analysis commands such as oma stats
uses the file path .agents/results/recap/2026-04-01~2026-04-07.md
and 4 more in the full report
7 fixed5 passed either way9 still failing1 broke
Pass-rate lift
+27 pp
Tokens
+127%
Agent turns
0%
Response time
-53%
Model gemini-3.6-flashMeasured 8/17/2026v312 of 22 cases passed with skill · 16 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 7
Prompt
Generate the TL;DR section for my daily recap. How many lines should it contain at the top of the report?
What was checked, without and with the skill
Checked
Without skill
With skill
restricts the top TL;DR section to a maximum of 3 lines
Missed
Passed
case-16 · gemini-3.6-flash · 8/17/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md234 linessingle file
AI Tool Conversation History Summary
Analyze AI tool conversation histories for a given period and generate themed work summaries.
Scheduling
Goal
Collect AI tool conversation history for a date or window and synthesize it into a themed, project-oriented recap with saved Markdown output.
Intent signature
User asks for daily recap, weekly/monthly summary, standup notes, work log, tool usage pattern, or AI conversation history analysis.
User wants conversation histories grouped by work content rather than raw chronological logs.
When to use
Summarizing a day or period of work activity
Understanding the overall flow of work across multiple AI tools
Analyzing tool-switching patterns between sessions
Preparing daily standups, weekly retros, or work logs
When NOT to use
Git commit-based code change retrospective -> use oma retro
Real-time agent monitoring -> use oma dashboard
Productivity metrics -> use oma stats
Expected inputs
Date, relative date, time window, or tool filter
Conversation history available through oma recap --json or fallback sources
Desired daily or multi-day recap scope
Expected outputs
Markdown recap saved to .agents/results/recap/{date}.md or range filename
TL;DR, overview, themes/projects, miscellaneous or side projects, and tool usage patterns
User-facing summary in configured response language
Dependencies
oma recap --json
Optional Claude fallback history at ~/.claude/history.jsonl