Send the bulky reading in a task to the on-device worker, then check its answer
once. The main session keeps planning and answering. The worker reads the big
inputs on the local model, so they never enter the main context.
compute the answer, do it yourself now: no plan, no notes about this
skill. Delegate only when you would otherwise READ more than about 25 KB
of text into your context (prose, many files). Never delegate security
review or design decisions.
local-coding:on-device-worker (the plugin id). If the task tool lists it
as plain on-device-worker instead (copied into an agents folder), use
that. If neither is available, work normally.
name: "on-device-description: 3-5 wordsagent_type: the worker id from step 2mode: "sync"model: the on-device model id named in the session's routing line,exactly (if there is none:
"winml-azureml-mai-code-1.1-flash-on-device/MAI-Code-1.1-Flash-On-Device").
The worker does not pin a model, so without this it runs on your own
model.
prompt, exactly:```text
GOAL:
INPUTS:
RULES: Read only INPUTS. At most 8 tool calls. Edit nothing but OUTPUT. No questions.
OUTPUT:
ANSWER: Reply ONCE with only
If you cannot, reply only: UNABLE:
```
check). Never recompute the answer or re-read the input. If the answer is
wrong, UNABLE, or the task call fails: do it yourself. Then finish.
User: "Use the on-device-delegate skill. From the logs under logs\, list
every distinct error message with its count, most frequent first."
Task prompt:
GOAL: Count each distinct error message in the logs.
INPUTS: logs\
RULES: Read only INPUTS. At most 8 tool calls. Edit nothing but OUTPUT. No questions.
OUTPUT: reply only
ANSWER: Reply ONCE with only lines of the form "<count> <message>", most frequent first, then stop.
If you cannot, reply only: UNABLE: <reason>
Check: confirm the lines match the format and spot-check one count with a
single search. Then answer the user.
catches format errors, not every wrong fact. Tell the user what you checked.
call while the local model loads.
scripts/ holds two setup scripts for the user, described in the
local-coding plugin README. They are not part of a task: never run them while
you work on the user's request.
scripts/Set-LocalOutputCap.ps1 caps thelocal model's output tokens in the user's providers.json.
installs or updates the plugin, then runs the cap script.