chat-submit

Routes approved plans into Invoker for durable parallel workflow execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Moving an approved multi-layer or multi-PR plan out of a chat session and into durable, parallel execution normally requires manual orchestration. This Skill automates the handoff of reviewed plans into Invoker so long-running agent work runs as persisted workflows instead of staying in the chat. ## Core Features & Use Cases - Plan-to-workflow handoff: Converts an approved plan into plans/invoker-handoff.yaml and submits it through the Invoker MCP tools with a review token and explicit approval gate. - Completeness and safety gates: Runs a planning completeness check before submission and blocks submission when Goal, Motivation, Safety invariant, repoUrl, or Verify fields are missing. - Background monitoring: Parks on invoker-cli wait after submission and resumes on INVOKER_WAKE to handle blockers, approvals, or the reviewed onFinish outcome such as opening a pull request. - Use Case: After approving an implementation plan spanning three stacked PRs, ask the assistant to submit it to Invoker; the Skill prepares the review, submits one head workflow first, confirms it is running, fans out the rest, and ends the turn while a background wait watches for completion. ## Quick Start Ask the assistant to submit the approved plan to Invoker and run it as durable parallel workflows.

Frequently Asked Questions about chat-submit

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

FAQPage Schema
How do I submit an approved plan to Invoker from chat?

Ask the assistant to run the plan on Invoker. The Skill builds plans/invoker-handoff.yaml, runs the completeness check, calls invoker_prepare_plan_review for a review token, gets your approval, then submits with invoker_submit_plan in live mode.

When should work go to Invoker instead of staying in chat?

Use Invoker for multi-layer, multi-PR, overnight, or durable parallel agent work and approved plans. Keep one-slice same-repo features, one-file fixes with a local repro, and read-only questions in the current chat.

Can Invoker run on a remote host instead of locally?

Yes. The default MCP target is local invoker-cli mcp, but if you name a host or SSH alias the Skill probes SSH first and retargets the harness MCP only on success. It never invents HTTP/SSE MCP or clobbers the local setup on failure.

Why does plan submission get blocked before review?

Submission is blocked when the planning completeness gate fails, such as missing Goal, Motivation, Safety invariant, repoUrl, or Verify fields, or leftover REPLACE_ME placeholders. Clarify the missing fields in chat before resubmitting.

What happens after a workflow is submitted to Invoker?

The Skill arms a background invoker-cli wait and ends the turn instead of polling. On INVOKER_WAKE it checks workflow status, routes blockers to invoker-ops, and on success completes the reviewed onFinish outcome such as opening a pull request.