菜单
Use when commands need sudo, root/admin elevation, require_escalated, pseudo-terminal/PTY handling, interactive sudo or elevated terminal password prompts, or managed tmux run tracking.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Practical Node.js and Next.js project runbook. Use for Node, Next.js, React, package-manager, build, migration, debugging, testing, security, deployment, and version-verification tasks.
Host-first Scrapling integration skill: install or upgrade Scrapling via pipx, run single-URL extractions (simple and structured), and manage adapter and version refresh flows, with Docker as an optional escape hatch.
Project-aware shadcn/ui guide. Use for shadcn setup, components, CLI/MCP, registry, theming, forms, Radix/Base UI, aliases, updates, and troubleshooting in React UI projects.
Use when running a bounded Codex goal loop over GitHub issues, PRs, and maintenance alerts with explicit approval gates.
Comprehensive OmniRoute administration and automation via Python tooling. Use when you need full API-driven control of providers, nodes, aliases, combos, fallbacks, keys, policies, budgets, backup/restore, sync, resilience, and configuration reconciliation with safety gates.
OmniRoute client onboarding and Codex CLI configuration workflow. Use for setup, launch, Codex profile files, wire_api responses configuration, and safe agent-client registration with OmniRoute.
| name | ls-workflow-ops-tmux-session |
| description | Use when commands need sudo, root/admin elevation, require_escalated, pseudo-terminal/PTY handling, interactive sudo or elevated terminal password prompts, or managed tmux run tracking. |
| metadata | {"version":"1.0"} |
Use this workflow package for server or remote ops through tmux wrappers.
Primary references: localsetup://doc/ops/tmux-ops-managed.md and localsetup://doc/ops/tmux-ops-remote.md.
Use this workflow when a command needs sudo, root/admin elevation, require_escalated, pseudo-terminal/PTY behavior, interactive sudo or elevated terminal password prompt handoff, or durable managed tmux run tracking through localsetup://tool/tmux_ops.
Do not use this workflow for normal repo-local coding, API authentication, token setup, non-privileged file edits, or commands that can run safely without managed terminal state.
localsetup://tool/tmux_ops pick and show the returned attach command.localsetup://tool/tmux_ops probe -t <session>.
"action_required": true or "sudo": "password_required", stop.attach_command, run sudo -v in that exact tmux pane, enter the password, then reply sudo ready.sudo ready before probing again.localsetup://tool/tmux_ops run -t <session> -- <cmd>.localsetup://tool/tmux_ops status -t <session> --run-id <id>.localsetup://tool/tmux_ops cancel -t <session> --run-id <id>.Use the returned run_id, status, tail, and log_path as evidence.
For active privileged work where the user has already entered sudo in the same managed pane, use bounded one-shot keepalive commands instead of ad hoc loops.
Request a marker only after probe reports sudo ready:
localsetup://tool/tmux_ops keepalive request -t <session> --owner <id> --ttl-seconds 7200 --max-refreshes 24 --reason "<reason>"
Refresh only as an explicit one-shot action while privileged work remains active and the managed pane is idle between commands:
localsetup://tool/tmux_ops keepalive refresh -t <session>
Report state with localsetup://tool/tmux_ops keepalive status -t <session>.
Clear the marker with localsetup://tool/tmux_ops keepalive clear -t <session> --owner <id> when privileged work ends.
Keepalive is restricted to managed ops* sessions, caps TTL at 7200 seconds and refreshes at 24, and runs only hard-coded sudo -n -v during refresh. It must not start a background loop, prompt for a password, or refresh while a managed run is active, another refresh is in progress, or the pane is not idle.