Dispatch coding and development tasks to Codex CLI (codex exec) in background with automatic callback/notification on completion. Use when the user asks to use Codex or Codex CLI for build, fix, review, refactor, or other long-running coding tasks.
Robust two-phase process termination pattern for PyQt6 apps with UI feedback and guaranteed cleanup
Build small MoonBit WASIp1 CLI tools using the peter-jerry-ye/wasi library, focused on simple read/write tasks (echo, cat, wc, simple file ops). Use when creating or updating CLI examples, scripts, or skills for this repo.
Use this skill for ANY multi-pane or multi-agent terminal orchestration in cmux. Required when the user wants to: run things in parallel in separate terminal panes, split the terminal, spawn a sub-agent (Claude Code, Codex) in another pane, fan out tasks across splits, send keystrokes or text to another pane (including ctrl-c), read terminal output from another pane, update sidebar status or progress bar, open a URL in cmux's built-in browser pane, or display markdown preview alongside the terminal. The cmux CLI is the ONLY way to do these things — Bash cannot split panes or spawn agents. Trigger phrases: 'in parallel', 'split pane', 'spawn agent', 'fan out', 'new pane', 'browser pane', 'sidebar', 'send to pane', 'read from pane', 'show the plan', 'ctrl-c to', '分屏', '并行', '开个 pane'. NOT for: single command execution, basic bash operations, or questions about tmux.
This skill should be used when the user says "sketch", "arness code sketch", "preview this", "show me what this looks like", "UI preview", "sketch the feature", "visual preview", "sketch this page", "what will this look like", "mock this up", "prototype this UI", "preview the design", "sketch the UI", "preview this command", "show me what the output looks like", "sketch the TUI", "what will the CLI look like", "mock up the terminal output", or wants to see a working interface preview of a feature in the context of their existing application before committing to full implementation. Creates real, runnable artifacts using the project's actual framework and conventions, rendered in a dedicated sketch namespace.
Guide for developing bin programs (CLI commands) in ZerOS. Use when creating command-line tools, terminal commands, or CLI programs that run in D:/bin/ directory.
Modify the usethis CLI layer (commands, options, help text) and keep documentation in sync
Simulate user testing for CLI commands by running them in a fresh temporary project to verify the happy path
Dogfood new or modified CLI commands by running them against the usethis repo itself to catch edge cases
Add Discord commands to the bot. Use when implementing new slash commands or message commands.
SuprSend CLI is a command-line interface tool for managing your SuprSend account and resources. It provides a convenient way to interact with the SuprSend API, allowing you to perform various operations such as managing workspaces, users, workflow, templates and more.
Design command-line interface parameters and UX: arguments, flags, subcommands, help text, output formats, error messages, exit codes, prompts, config/env precedence, and safe/dry-run behavior. Use when you’re designing a CLI spec (before implementation) or refactoring an existing CLI’s surface area for consistency, composability, and discoverability.
Beeper Desktop CLI for chats, messages, search, and reminders.
Enables Claude to send messages, manage chats, and handle Telegram communications through the web interface
Browser automation via Playwright CLI. Open pages, interact with elements, take screenshots, and more. Ideal for coding agents and automated testing workflows.
Build CLI scripts alongside MCP servers for terminal environments. File I/O, batch processing, caching, richer output formats. Templates for TypeScript scripts and SCRIPTS.md. Use when: MCP companion scripts, batch processing, saving results to files, CLI API wrappers. Troubleshoot: context too large, no file access, batch input.
