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.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/oma-recap/SKILL.md

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a clear, validated multi-step workflow and good structure, losing points only to minor repetition and a referenced output-formats file that is absent from the bundle. Providing the missing reference file and deduplicating the rolling-window caveat would raise it further.

Suggestions

Add the missing resources/output-formats.md (or move it into references/) so the signaled output-template reference resolves to a real file.

Deduplicate the rolling-24h-window caveat and the date-resolution rules, stating each once in its canonical location.

Inline a minimal daily-format markdown template so the output shape is copy-paste ready without needing the external file.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational with no concept-tutorial padding, but repeats the rolling-window caveat three times (lines 66, 102, 145) and restates date-resolution rules in both Transitions and Process §1, fitting anchor 4's 'minor instances of over-explanation that could be trimmed' rather than anchor 5's flawless leanness.	4 / 5
Actionability	Provides concrete executable guidance—real oma recap invocations, a complete copy-paste jq fallback with macOS/Linux date variants, and exact output paths—but the actual output templates live in resources/output-formats.md which is not in the bundle, leaving the output shape described rather than copy-paste ready; this matches anchor 4's 'concrete code or commands with minor gaps' below anchor 5.	4 / 5
Workflow Clarity	Clear sequenced workflow (Entry → Scenes PREPARE/ACQUIRE/REASON/ACT/VERIFY/FINALIZE → numbered Process) with an explicit VERIFY validation checkpoint, a Failure-and-recovery feedback section, preconditions, and partial-success exit criteria, matching anchor 5's explicit validation steps plus error-recovery feedback loops.	5 / 5
Progressive Disclosure	Well-organized top-level structure with a clearly signaled one-level reference to resources/output-formats.md (lines 216, 235), but no references/scripts/assets/resources directories exist in the bundle so the referenced file is missing—a navigation gap that places it at anchor 4 rather than anchor 5's verified easy navigation.	4 / 5
	Total	17 / 20 Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and action-oriented with a clear niche, but it omits any explicit 'Use when...' trigger clause, which caps its completeness. Adding concrete trigger phrases would lift the completeness and trigger-term scores.

Suggestions

Append an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user asks for a daily recap, weekly/monthly summary, standup notes, work log, or AI conversation-history analysis').

Add common user-facing synonyms such as 'standup', 'work log', 'retro', and 'sprint report' to broaden trigger-term coverage.

Clarify the 'when' by noting it groups by work content rather than raw chronology, reinforcing distinction from generic summarization skills.

Dimension	Reasoning	Score
Specificity	Names the domain (AI tool conversation histories) and lists several concrete actions—analyze, generate themed summaries, filter by date/window—plus an enumerated tool list, fitting anchor 4; not the comprehensive multi-action coverage of anchor 5.	4 / 5
Completeness	The 'what' is clearly stated but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3 (anchor 3: clear 'what', 'when' missing).	3 / 5
Trigger Term Quality	Good natural-term coverage ('conversation histories', 'work summaries', 'date or time window') plus enumerated tool names, but misses common variations like 'standup', 'work log', or 'retro', so it sits at anchor 4 rather than the comprehensive synonym coverage of 5.	4 / 5
Distinctiveness Conflict Risk	The enumerated multi-tool list and 'themed work summaries' carve a distinct niche with only minor overlap risk against a generic summarization skill, matching anchor 4 rather than the minimal-conflict niche of anchor 5.	4 / 5
	Total	15 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: first-fluke/oh-my-agent
Path: .agents/skills/oma-recap/SKILL.md
Commit: 032c988

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.