playbooks

home / skills / yeachan-heo / oh-my-claudecode / learn-about-omc

learn-about-omc skill

/skills/learn-about-omc

This skill analyzes your OMC usage to deliver personalized recommendations for optimizing workflows and feature usage.

npx playbooks add skill yeachan-heo/oh-my-claudecode --skill learn-about-omc

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.0 KB
---
name: learn-about-omc
description: Learn about your OMC usage patterns and get personalized recommendations
---

# Learn About OMC

Analyze your OMC usage patterns and provide personalized recommendations for getting more out of oh-my-claudecode.

## Usage

```
/oh-my-claudecode:learn-about-omc
```

## Behavior

1. **Scan usage data** from:
   - `.omc/sessions/` for session history
   - `.omc/state/` for mode usage patterns
   - `.omc/notepad.md` for working memory
   - `.omc/project-memory.json` for project context
   - Agent flow traces for tool and agent usage
2. **Analyze patterns**:
   - Most-used modes and skills
   - Agent types spawned most frequently
   - Common workflows and task types
   - Session durations and completion rates
3. **Generate recommendations**:
   - Underused features that match your workflow
   - More efficient skill combinations
   - Configuration optimizations
   - Tips based on your usage profile

## Output

A personalized report with usage statistics and actionable recommendations for improving your OMC workflow.

Overview

This skill analyzes your oh-my-claudecode (OMC) usage to surface patterns and deliver personalized recommendations. It turns session history, state, and agent traces into a concise report with actionable steps to improve workflows and productivity.

How this skill works

The skill scans local OMC artifacts such as session logs, state files, project memory, notepad entries, and agent flow traces to build an activity profile. It identifies frequent modes, agent types, workflows, and completion metrics, then maps those insights to targeted recommendations for feature adoption, skill combinations, and configuration tweaks.

When to use it

  • Onboard a new team to understand current OMC habits and weaknesses
  • After a sprint or month to evaluate productivity and session outcomes
  • When adoption stalls and you need targeted, low-friction improvements
  • Before standardizing processes to align agent types and modes
  • When you want to optimize configuration for speed, cost, or accuracy

Best practices

  • Run the analysis periodically (weekly or monthly) to track trends over time
  • Keep .omc session and state files available and unaltered for accurate results
  • Combine report recommendations with a short pilot to validate changes
  • Share the findings with the team and prioritize 1–3 high-impact changes
  • Use the suggested skill combinations in a dedicated test session before broad rollout

Example use cases

  • Discovering that a specific agent type handles bug triage far faster and adjusting workflows accordingly
  • Identifying underused modes (e.g., parallel execution) and enabling them for applicable tasks
  • Reducing session durations by recommending more efficient skill sequences and shortcuts
  • Tuning configuration options to lower resource use while preserving completion rates
  • Creating a training checklist that introduces overlooked features to new teammates

FAQ

What data does the skill read?

It inspects local OMC artifacts such as .omc/sessions/, .omc/state/, .omc/notepad.md, .omc/project-memory.json, and agent flow traces.

Is any data uploaded externally?

No. The analysis runs locally on the available OMC files and produces a local report unless you choose to share it.