Menu
Operate Genome's Agentic OS runtime registries, heartbeats, schedules, run queues, and guarded Notion runtime tracking from file-backed state.
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 | runtime-operator |
| description | Operate Genome's Agentic OS runtime registries, heartbeats, schedules, run queues, and guarded Notion runtime tracking from file-backed state. |
Use this skill when a task asks to initialize, inspect, dry-run, or diagnose the installed Agentic OS runtime.
~/agentic_os.agentic-os runtime init --root <root> if runtime registries are missing.shared_factory/00-control-plane/runtime-registry.yml and run-queue.yml.agentic-os heartbeat run <heartbeat_id> --root <root> --dry-runagentic-os schedule run-due --root <root> --dry-runagentic-os run-queue prune --root <root> --dry-runagentic-os runtime doctor --root <root> or agentic-os heartbeat doctor --root <root> before treating the runtime as healthy.agentic-os notion track-runtime --root <root> --dry-run before any apply.shared_factory/06-runs-and-logs/heartbeats/.shared_factory/06-runs-and-logs/run-queue-prune/.Groom rough software ideas into source-backed implementation specs with original intent, capability discovery, tracker hierarchy, QA, Gherkin, and Notion documentation projection.
Append environment variables to ~/.zshenv on bigmac, genomesbox, and the Mac laptop in one step. Use when the user pastes `KEY=value` pairs and asks to add them to zshenv, or when setting secrets that need to be available on all three hosts. ssh aliases `bigmac`, `genomesbox`, and `mac` are already configured where needed.
Commit all local changes in logical groups until the repository is clean. Use when the user asks to commit everything, make all needed commits, or cleanly commit the full worktree without pushing.
Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with `composio listen`, script workflows with `composio run`, and call authenticated app APIs with `composio proxy`. Use when the user asks how to do something with `composio`, wants to run a known tool slug, needs to discover a slug with `composio search`, fix a missing connection with `composio link`, inspect tool inputs with `--get-schema` or `--dry-run`, troubleshoot top-level CLI flows, or explicitly needs `composio dev` guidance.
Use when the user wants to work a LOS Jira ticket or non-trivial LOS task in a dedicated fast worktree, especially when they mention /workon, /orchestrate, fast worktree, use a worktree, or parallel agents.
Use when working or resuming LOS Jira implementation in a fast worktree with minimal chat output, especially after noisy /workon loops, repeated stack setup, test polling, or context/token burn.