Agent skill · AI & Agents

oma-recap

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.

first-flukegithub.com/first-flukeGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add first-fluke/oh-my-agent --skill oma-recap --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: .agents/skills/oma-recap/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,204
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 save

What's inside
Steps it walks through
  1. Scheduling
  2. Goal
  3. Intent signature
  4. When to use
  5. When NOT to use
  6. Expected inputs
  7. Expected outputs
  8. Dependencies
  9. Control-flow features
  10. Structural Flow
  11. Entry
  12. Scenes
  13. Transitions
  14. Failure and recovery
Ships with 1 file
  • resources/output-formats.md
Commands it runs
oma recap --date YYYY-MM-DD --json
oma recap --window 7d --json
oma recap --json  # rolling last 24h, not "today"
Today (calendar day, all tools)
oma recap --date $(date +%F) --json
Last 24 hours (rolling window ending now)
oma recap --json
Time window (rolling, ends now; capped at 30d)
Specific date
oma recap --date 2026-04-10 --json
More from oh-my-agent
All skills →
oma-mobileMobile specialist for Flutter, React Native, and Swift native iOS development. Use for mobile app…Frontendoma-slideHTML presentation deck generator and multi-format exporter. Generates distinctive, animation-rich…Design & Presentationoma-backendBackend specialist for APIs, databases, authentication with clean architecture…Securityoma-hwpConvert HWP / HWPX / HWPML files to Markdown using kordoc. Extracts text, headings, tables, lists…Data & Analyticsoma-orchestratorAutomated multi-agent orchestrator that spawns CLI subagents in parallel, coordinates via MCP…AI & Agentsoma-videoShort-form, explainer, and demo video generation via a key-optional 3-tier router. Composes…Data & Analytics
About this skill
What does the oma-recap skill do?

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.

How do I install it?

Run `npx skills add first-fluke/oh-my-agent --skill oma-recap --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From first-fluke/oh-my-agent, a repository with 1,204 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.