learn-about-omd
Analyze your OMC usage patterns and get personalized recommendations
Best use case
learn-about-omd is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Analyze your OMC usage patterns and get personalized recommendations
Teams using learn-about-omd should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/learn-about-omd/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How learn-about-omd Compares
| Feature / Agent | learn-about-omd | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Analyze your OMC usage patterns and get personalized recommendations
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Learn About OMC Analyzes your oh-my-droid usage and provides tailored recommendations to improve your workflow. ## What It Does 1. Reads token tracking from `~/.omd/state/token-tracking.jsonl` 2. Reads session history from `.omd/state/session-history.json` 3. Analyzes agent usage patterns 4. Identifies underutilized features 5. Recommends configuration changes ## Implementation ### Step 1: Gather Data ```bash # Check for token tracking data TOKEN_FILE="$HOME/.omd/state/token-tracking.jsonl" SESSION_FILE=".omd/state/session-history.json" CONFIG_FILE="$HOME/.factory/.omd-config.json" echo "📊 Analyzing OMC Usage..." echo "" # Check what data is available HAS_TOKENS=false HAS_SESSIONS=false HAS_CONFIG=false if [[ -f "$TOKEN_FILE" ]]; then HAS_TOKENS=true TOKEN_COUNT=$(wc -l < "$TOKEN_FILE") echo "Token records found: $TOKEN_COUNT" fi if [[ -f "$SESSION_FILE" ]]; then HAS_SESSIONS=true SESSION_COUNT=$(cat "$SESSION_FILE" | jq '.sessions | length' 2>/dev/null || echo "0") echo "Sessions found: $SESSION_COUNT" fi if [[ -f "$CONFIG_FILE" ]]; then HAS_CONFIG=true DEFAULT_MODE=$(cat "$CONFIG_FILE" | jq -r '.defaultExecutionMode // "not set"') echo "Default execution mode: $DEFAULT_MODE" fi ``` ### Step 2: Analyze Agent Usage (if token data exists) ```bash if [[ "$HAS_TOKENS" == "true" ]]; then echo "" echo "TOP AGENTS BY USAGE:" cat "$TOKEN_FILE" | jq -r '.agentName // "main"' | sort | uniq -c | sort -rn | head -10 echo "" echo "MODEL DISTRIBUTION:" cat "$TOKEN_FILE" | jq -r '.modelName' | sort | uniq -c | sort -rn fi ``` ### Step 3: Generate Recommendations Based on patterns found, output recommendations: **If high Opus usage (>40%) and no ecomode:** - "Consider using ecomode for routine tasks to save tokens" **If no pipeline usage:** - "Try /pipeline for code review workflows" **If no security-reviewer usage:** - "Use security-reviewer after auth/API changes" **If defaultExecutionMode not set:** - "Set defaultExecutionMode in /omd-setup for consistent behavior" ### Step 4: Output Report Format a nice summary with: - Token summary (total, by model) - Top agents used - Underutilized features - Personalized recommendations ### Graceful Degradation If no data found: ``` 📊 Limited Usage Data Available No token tracking found. To enable tracking: 1. Ensure ~/.omd/state/ directory exists 2. Run any OMC command to start tracking Tip: Run /omd-setup to configure OMC properly. ``` ## Example Output ``` 📊 Your OMC Usage Analysis TOKEN SUMMARY: - Total records: 1,234 - By Model: opus 45%, sonnet 40%, haiku 15% TOP AGENTS: 1. executor (234 uses) 2. architect (89 uses) 3. explore (67 uses) UNDERUTILIZED FEATURES: - ecomode: 0 uses (could save ~30% on routine tasks) - pipeline: 0 uses (great for review workflows) RECOMMENDATIONS: 1. Set defaultExecutionMode: "ecomode" to save tokens 2. Try /pipeline review for PR reviews 3. Use explore agent before architect to save context ```
Related Skills
learner
Extract a learned skill from the current conversation
writer-memory
Agentic memory system for writers - track characters, relationships, scenes, and themes
ultrawork
Decompose multi-step tasks into parallel sub-agent workloads, route each sub-task to the cheapest capable model tier (Haiku/Sonnet/Opus), run long-running commands in the background, and verify all deliverables before stopping. Use when the user asks to 'go fast', 'parallelize', 'ultrawork', or when a request contains 3+ independent sub-tasks that benefit from concurrent execution.
team
Coordinate named agents as a team with inter-agent communication
tdd
Enforce strict Test-Driven Development (TDD) using the red-green-refactor cycle. Use when writing unit tests, practicing test-first development, applying TDD discipline, or implementing features via red-green-refactor workflows.
swarm
N coordinated agents on shared task list with SQLite-based atomic claiming
skill
Manage local skills - list, add, remove, search, edit
security-review
Run a comprehensive security review on code
review
Review a plan with Critic
research
Orchestrate parallel scientist agents for comprehensive research with AUTO mode
release
Automated release workflow for oh-my-droid
ralplan
Iterative planning with Planner, Architect, and Critic until consensus