invoker-ops

Operates existing Invoker workflows and tasks through headless CLI commands.

18|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill invoker-ops-neko-catpital-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: invoker-ops
Source: https://github.com/Neko-Catpital-Labs/Invoker/tree/main/skills/invoker-ops
Command: npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill invoker-ops-neko-catpital-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Operators of Invoker multi-agent workflows need a safe, consistent way to inspect, retry, restart, and cancel tasks without touching the SQLite database directly or relying on stale state from earlier checks. ## Core Features & Use Cases - Safe command map: Lists workflows and tasks, retries failed or pending tasks in bulk or individually, and supports dry-runs for destructive-looking operations via invoker-ui --headless commands. - State freshness enforcement: Requires re-running query commands in the same turn before reporting workflow, task, CI, or merge status, since state drifts between checks. - Edge-case handling: Diagnoses needs_input tasks with empty output by reading execution.inputPrompt, handles macOS open -a stdout loss by calling the app binary directly, and sequences chain cancellations downstream-first. - Use Case: When asked to "restart all failing tasks", run a dry-run, execute retry-tasks --status failed --parallel 8, report accepted/failed submission counts, then verify with fresh query commands. ## Quick Start Ask the assistant to list all failed Invoker tasks and retry them, then confirm the current state with a fresh query.

Frequently Asked Questions about invoker-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retry all failed Invoker tasks?

Run `invoker-ui --headless retry-tasks --status failed --parallel 8` to dispatch retries for all failed tasks. For broad or destructive-looking requests, add `--dry-run` first, then verify remaining state with `query tasks` commands afterward.

How do I list running workflows and tasks in Invoker?

Use `invoker-ui --headless query workflows --output text` to list workflows, optionally filtering with `--status failed`. Then run `query tasks --workflow <workflowId> --status running` to inspect tasks within a specific workflow.

Can I query the Invoker SQLite database directly?

No, direct database reads are prohibited for normal operations; use Invoker commands first. Direct database access is only allowed when explicitly debugging persistence internals or when the command surface itself is broken.

Why does a task show needs_input with empty output?

A task that goes needs_input seconds after submit with empty output was stopped by the owner before launch, and the reason is stored in execution.inputPrompt. No headless query projection emits that field, so inspect the task record key set and the owner's emitter before retrying.

Why does invoker-ui --headless return empty output on macOS?

On macOS, `invoker-ui --headless` goes through `open -a`, which discards stdout and the exit code, so an empty result proves nothing. Call the binary directly at /Applications/Invoker.app/Contents/MacOS/Invoker with the same headless arguments.

How do I cancel a chained Invoker workflow safely?

Cancel downstream workflows first, then the chain head, because cancelling the head releases downstream merge-gate dependencies and launches their tasks on master. Re-query tasks after each cancel until every task shows failed, since the cancel exit code is unreliable.