help

Guide oh-my-codex setup, keyword routing, and usage analysis.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users understand how to set up, route, and use the oh-my-codex plugin so they can get consistent behavior from the runtime without guessing which command or keyword to use.

Core Features & Use Cases

  • Setup Guidance: Explains how to initialize OMX, install the plugin, and prepare the environment for full runtime wiring.
  • Workflow Routing: Describes keyword-based control such as planning, persistence, and parallel execution so prompts land in the right lane.
  • Usage Analysis: Helps inspect token tracking, session history, and configuration settings to identify underused features and improvement opportunities.
  • Use Case: A developer wants to enable OMX, choose the right workflow for a complex task, and review their usage patterns to improve efficiency.

Quick Start

Ask for help setting up OMX, choosing the right routing keyword for your task, or analyzing your usage data for tailored recommendations.

Frequently Asked Questions about help

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

FAQPage Schema
How do I set up the oh-my-codex plugin for workflow routing?

The oh-my-codex plugin uses keyword-based routing to direct prompts into specific workflows like planning, persistence, or parallel execution. By matching explicit keywords in your prompts, OMX ensures tasks land in the correct processing lane for consistent runtime behavior.

What's the best way to analyze OMX token tracking and session history?

To analyze OMX usage, inspect your token tracking data and session history to identify underused features and improvement opportunities. This usage analysis helps developers understand patterns and optimize efficiency for future runtime interactions.

Can I use keyword-based controls to stop active OMX operations?

Yes, advisory prompt-routing controls driven by explicit keywords allow you to stop active operations within the oh-my-codex runtime. This keyword-based mechanism manages workflow execution and halts processes when specific routing terms are detected.

How do I choose the right routing keyword for a complex development task?

Choose the right routing keyword by matching your task complexity to OMX workflow options like planning, persistence, or parallel execution. Reviewing configuration settings and understanding advisory prompt-routing controls ensures prompts land in the appropriate lane.

Do I need OMX configuration awareness to inspect session and token data?

Yes, OMX configuration awareness is required to properly inspect session and token data for usage analysis. Understanding your configuration settings enables you to identify underused features and accurately review token or session history for efficiency improvements.