Menu
Meta-skill for core mu operating primitives. Routes to mu, programmable-ui, memory, tmux, and code-mode based on task shape.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | core |
| description | Meta-skill for core mu operating primitives. Routes to mu, programmable-ui, memory, tmux, and code-mode based on task shape. |
Use this meta-skill when the user asks for general mu operation guidance and you need to pick the correct foundational skill.
mu — default CLI-first operating workflow (inspect, mutate, verify, handoff).programmable-ui — canonical mu_ui/UiDoc workflow for publishing, inspecting, and debugging interactive UI docs.memory — prior-context retrieval, timeline reconstruction, and memory-index maintenance.tmux — persistent terminal/session substrate for bounded command execution and fan-out.code-mode — tmux-backed REPL loops for iterative execution and context compression.mu for most day-to-day operator work.programmable-ui when the user asks about mu_ui, /mu ui ..., UiDoc payloads, action wiring, or interactive prompt behavior.memory when prior context or timeline anchors are required.tmux when durable shell state or parallel worker shells are needed.code-mode when solving by live execution is cheaper than chat-only reasoning.mu commands (get, read, health) to inspect current state, then use memory to find "when did this last work?" before attempting a fix.programmable-ui to emit schema-valid UiDoc templates quickly, verify state with /mu ui status|snapshot, and close docs with mu_ui remove|clear.code-mode. The agent can spin up a REPL, iterate on a fix offline, and return only the root cause to the chat.tmux to spawn parallel worker shells, keep them running in the background, and periodically read their output.Runs core mu operator workflows for bounded investigation, CLI-first state operations, and session handoffs. Use when general mu execution or state-management guidance is needed.
Produces clear, argument-driven technical prose. Use when drafting or reviewing systems papers, design docs, READMEs, PR descriptions, error messages, API references, or other technical communication.
Builds and debugs mu_ui UiDocs with schema-valid payloads, interaction wiring, and status/snapshot verification.
Runs cross-store memory retrieval and index maintenance workflows with bounded filters and timeline anchors. Use when querying prior context or repairing memory index health.
Defines compositional control-flow policies for orchestration DAGs (for example review-gated retry loops) using protocol-preserving transitions.
Runs issue-driven execution supervision with heartbeat orchestration and tmux fan-out. Use when work should progress through durable parallel execution loops.