plan-to-invoker
Skill20 starsChanged 8 months agoLicence not identifiedView on GitHub
Convert a plan into an Invoker YAML plan file. After `install-skills`, this routing is always on via Cursor `~/.cursor/rules/invoker-execution-precedence.mdc`, a Codex AGENTS.md marked block, and a Claude UserPromptSubmit hook. One-slice same-repo edits stay local; multi-layer or multi-PR work goes through this skill (then chat-submit / auto_submit after the completeness gate) unless the user says "do it locally". Uninstall with `install-skills uninstall`. 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 (or scratch: true for no-repo mode), and tasks, never version or metadata wrappers, and must not scan, validate, submit, or discover env vars.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/harness-coverage.mdcCursor rule
- .cursor/rules/keep-docs-in-sync.mdcCursor rule
- .cursor/rules/land-stack-precedence.mdcCursor rule
- .cursor/rules/plan-safety-invariant.mdcCursor rule
- .cursor/rules/skill-command-precedence.mdcCursor rule
- admin-bypass-sweepSkill
- chat-submitSkill
- failure-triageSkill
- invoker-opsSkill
- invoker-setupSkill
- land-stackSkill
- make-prSkill
- prove-itSkill
- remote-ci-verifySkill
- review-compressionSkill
- route-delegationSkill
- verifySkill
- visual-proofSkill
- workflow-chain-submitSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
29 rules. About 0 are common, 9 are distinctive, and 20 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
20
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.