oliverv/caro / .agents/skills/oma-recap
oma-recap
VerifiedSummarize AI conversation histories for a specified date or period. Use for daily work recaps and cross-tool activity summaries.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.9 KB |
| resources/output-formats.md | markdown | 2.6 KB |
resources/output-formats.md
View on GitHub# Recap Output Format Templates
Markdown templates for the recap files written to `.agents/results/recap/`.
Response language follows the `language` setting in `.agents/oma-config.yaml`.
## Daily format (1d or specific date)
```markdown
## {date} Recap
> **TL;DR**
> - {Completed outcome, only with completion evidence}
> - {In-progress or requested work, labelled with its status when completion is unproven}
> - {Another supported outcome or status}
### Overview
2-3 sentence summary of the day. Written from "I did X" perspective.
Distinguish requested, in-progress, and completed work. A prompt by itself is a request; an
explicit result, receipt, or artifact supports completion. Focus on outcomes and progress, not
tool ratios or technical details.
### {Theme 1} (AM 09:36~11:30)
- Core work performed
- Key decisions
- 2-4 bullets per theme
### {Theme 2} (PM 13:33~15:21)
- Core work performed
- Key decisions
### Miscellaneous
- Brief summary of sub-15-minute tasks
### Tool Usage Patterns
- Tool usage ratios and primary purposes
- Notable tool-switching patterns
```
## Multi-day format (3d, 7d, 2w, 30d)
For any multi-day window, use a **project-driven structure** like a sprint report.
Focus on what was accomplished per project, not day-by-day chronology.
```markdown
## {start} ~ {end} Recap
> **TL;DR**
> - {Completed outcome, only with completion evidence}
> - {In-progress or requested work, labelled with its status when completion is unproven}
> - {Another supported outcome or status}
### Overview
3-5 sentence narrative of the period. Major focus shifts across the window,
key milestones achieved, and overall direction. Written from "I did X" perspective.
### {Project A}
What this project is, with requested, in-progress, and completed work distinguished by evidence.
- Key milestone or deliverable 1
- Key milestone or deliverable 2
- Key decision made
- Current status (shipped / in progress / blocked)
### {Project B}
- ...
### Side Projects
Projects with <30 prompts, summarized briefly.
- {project}: one-line summary
- {project}: one-line summary
### Tool Usage Patterns
- Tool usage ratios and how they evolved over the period
- Notable shifts (e.g., "started using Codex midway through the period")
```
## Multi-day grouping rules
- Group by **project**, not by date
- Order projects by activity volume (most active first)
- Each project section: what it is, supported outcomes, key decisions, and current status
- Do NOT include prompt counts or date ranges in project headers (those are internal metrics)
- Small projects (<30 prompts) go into "Side Projects" as one-liners
- Overview should read like a sprint report narrative, not a log
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |