help

Analyze OMX usage data and generate structured recommendations reports.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/pextacy/stellar --skill help-pextacy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: help
Source: https://github.com/pextacy/stellar/tree/main/skills/help
Command: npx skills add https://github.com/pextacy/stellar --skill help-pextacy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze OMX usage data to generate actionable usage recommendations.

Core Features & Use Cases

  • Reads and analyzes token-tracking data to identify usage patterns and bottlenecks.
  • Produces tailored recommendations to optimize OMX adoption and efficiency.
  • Generates concise, actionable reports for stakeholders to drive improvements.

Quick Start

Run /omx-setup to configure OMX for first use.

Frequently Asked Questions about help

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze OMX usage data to identify underutilized features?

Analyzing OMX usage data involves parsing token-tracking.jsonl, session-history.json, and OMX config files to identify underutilized features. This process outputs a structured recommendations report highlighting optimization opportunities.

What are token-tracking logs used for in OMX configuration analysis?

Token-tracking logs are parsed to identify usage patterns and bottlenecks within OMX. Analyzing token-tracking.jsonl files reveals session histories and configuration metadata to pinpoint optimization opportunities.

How do I generate actionable recommendations from session-history.json files?

Generating actionable recommendations from session-history.json files requires analyzing session histories alongside token-tracking data. This identifies underutilized features and outputs a concise report to optimize OMX adoption.

Does OMX usage analysis require any specific dependencies or components?

OMX usage analysis requires no external dependencies or components. It independently parses token-tracking.jsonl, session-history.json, and OMX config files to produce structured recommendations without additional setup.

What is the best way to find optimization opportunities in OMX usage patterns?

Finding OMX optimization opportunities involves analyzing token-tracking.jsonl and session-history.json files. This identifies underutilized features and bottlenecks, producing a structured recommendations report for stakeholders.