Jules delegation
When and how to delegate coding tasks to Google Jules (async cloud coding agent) via the jules CLI. Use when the user says "jules", "send to jules", "delegate this", wants a task done in the background on a cloud VM, wants N parallel attempts at the same task, or wants to pull/apply a Jules session's result.From its SKILL.md
npx -y skills add prantikmedhi/jules-plugin-cc --skill jules-delegationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, as published. Nobody here has run it
Jules delegation
Jules is Google's asynchronous coding agent: it clones a connected GitHub repo into a cloud VM, works alone, and produces a patch. It is fire-and-forget — the local session keeps working while Jules runs.
When to delegate to Jules
- Well-scoped, self-contained tasks: "write unit tests for X", "add dark theme", "upgrade dependency Y and fix breakage", "fix issue #42".
- Tasks the user wants off their machine (long-running, or while they work on something else locally).
- Fan-out:
--parallel 2..5runs competing sessions on the same prompt; pick the best patch afterwards.
When NOT to delegate
- Tasks needing local secrets, local services, or tight interactive iteration.
- Repos not connected at https://jules.google (connect there first).
- Anything touching uncommitted local work — Jules only sees the remote repo.
Command map
| Intent | Command |
|---|---|
| Health/install/login check | /jules:setup |
| Delegate a task | /jules:new [--repo o/n] [--parallel N] <task> |
| See sessions / repos | /jules:list / /jules:list --repo |
| Review a result | /jules:pull <id> |
| Apply a result locally | /jules:pull <id> --apply |
| Clone+branch+apply in one step | /jules:teleport <id> |
Prompt quality
Jules starts with zero conversation context. Before sending, fold in: exact file paths, error text, constraints, and acceptance criteria. A prompt that would confuse a new contributor will confuse Jules.
Raw CLI (for scripting)
printf '%s' "task" | jules remote new --repo owner/name --parallel 3
jules remote list --session
jules remote pull --session <id> --apply
jules teleport <id>
Auth is Google OAuth via jules login (interactive; --no-launch-browser
for headless). There is no API-key path in the CLI.