菜单
Safely operate existing Invoker workflows and tasks from natural-language requests. Trigger when asked to list, inspect, retry, restart, resume, cancel, approve, reject, or check pending/failed/running Invoker tasks or workflows.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate a reusable loop instruction doc, loop driver script, and Invoker workflow from an interview. Trigger: "loop generator", "generate a loop", "invoker-loop-generator", "/invoker-loop-generator", or requests to build a reusable babysit/watch/retry loop. For benchmark/direct-output prompts with "Required output path", write the requested artifact directly to that literal path, do not ask clarifying questions, and do not validate, review-gate, or submit.
Convert a plan into an Invoker YAML plan file. Trigger: "convert to invoker", "submit to invoker", "create invoker plan", "invoker-plan-to-invoker", "/invoker-plan-to-invoker", "/plan-to-invoker", or turning a plan file into Invoker tasks. For benchmark/direct-output prompts with "Required output path", write a complete YAML document directly to that literal path; it must start with top-level name, onFinish, mergeMode, repoUrl, and tasks, never version or metadata wrappers, and must not scan, validate, submit, or discover env vars.
Create or update a pull request in this repo using the preferred PR schema, upstream-first branch workflow, and repo-specific publication rules. Trigger when asked to make a PR, update a PR body, prepare PR text, publish a stacked PR branch, or whenever a branch/PR change means the GitHub PR metadata may now be stale.
Shape code changes, workflow plans, and PR stacks so each diff is easy to review: one local claim, one safety invariant, clear architectural effect, and an explicit reason for the slice.
Land (queue/merge) a Mergify-managed PR stack safely. Trigger when asked to land, merge, ship, or queue a PR or PR stack with Mergify. Enforces that you act only on SHA-verified PR numbers — never a PR found by branch name.
Get a new machine "good to go" for Invoker and optionally wire up the Slack integration. Trigger when asked to set up Invoker, run the setup/tutorial, check the environment, fix missing tools, or configure the Slack bot ("set up slack", "/setup", "am I good to go?").
| name | invoker-ops |
| description | Safely operate existing Invoker workflows and tasks from natural-language requests. Trigger when asked to list, inspect, retry, restart, resume, cancel, approve, reject, or check pending/failed/running Invoker tasks or workflows. |
Use this skill for operator requests against existing Invoker state.
Examples:
Do not query or mutate the SQLite database directly for normal operations.
Use Invoker commands first. Direct database reads are only allowed when the user explicitly asks to debug persistence/storage internals, or when the Invoker command surface itself is the broken thing being investigated.
./run.sh --headless query workflows --output text
./run.sh --headless query workflows --status failed --output json
./run.sh --headless query tasks --workflow <workflowId> --output text
./run.sh --headless query tasks --workflow <workflowId> --status pending --output json
./run.sh --headless query tasks --workflow <workflowId> --status failed --output json
./run.sh --headless query tasks --workflow <workflowId> --status running --output json
If the request says "all workflows", first list workflows, then query each workflow through query tasks --workflow <workflowId>.
./run.sh --headless retry-tasks --status failed --parallel 8
./run.sh --headless retry-tasks --status pending --parallel 8
./run.sh --headless retry-tasks --status pending --parallel 8 --dry-run
./run.sh --headless retry-task <taskId> --no-track
./run.sh --headless retry <workflowId> --no-track
Bulk retry commands must use --no-track.
The operator acknowledgement means the retry request was accepted for dispatch. It does not mean the task finished.
After submitting, verify with query commands, not database reads.
./run.sh --headless retry-tasks --status <status> --parallel 8.query tasks commands when the user asks for current state.Do not invent SQL as the fallback.
Report the missing command surface and add/fix the command if the user asked for a durable production-safe path.