What is a worker kit?
A worker kit is a ready-made AI worker packaging the instruction, app permissions, memories and schedule for one job, ready to run with your own accounts.
A kit is to an AI worker what a recipe is to a meal: the whole method, written down by someone who already cooked it, so you do not have to work it out yourself.
What is inside a kit
A kit is not a prompt. It carries every part of a worker that had to be decided:
- The instruction. The standing brief for the job, written and tested against real runs rather than drafted once and hoped for.
- The app permissions. Which apps the job needs, and the exact access level each one gets. A kit states this before you take it, so you know what you are agreeing to.
- The memories. The facts and rules the worker should carry between runs.
- The schedule or trigger. When the job should happen.
- The per-model grades. How the kit performs on Claude, ChatGPT, Gemini and Grok, each grade marked with where it came from: measured from real runs, or declared by the publisher.
Why a package and not a prompt
The hard part of an unattended agent is never the model. It is the instruction, the access rules and the wiring, and all three take real work to get right.
Someone has to discover that the job breaks when the CRM field is empty. Someone has to decide the agent gets Read on the calendar and Write on drafts only. Someone has to write the sentence that keeps it from replying to the wrong thread. A kit is that work, already done, by a publisher who ran it.
So the value of a kit is not that it saves you typing. It is that it saves you the four hundred runs it takes to learn what the instruction should have said.
Taking a kit
Taking a kit mints a worker in your own account, with its own key and only the access you granted. The kit is a template; the worker is yours. Two things follow:
- The publisher never gains access to your accounts. A kit cannot reach an account you have not connected.
- You can narrow or revoke any permission afterwards, and the worker keeps running with whatever is left.
Public, private, and permanent
A published kit gets its own page and a permanent address for life, so an update lands on the same URL rather than a new one and every link to it keeps working. Kits can also stay private, on every plan including Free.
Anyone can publish one. The Kit Creator Studio is a no-code builder: describe the job, pin the apps and the access each gets, write the instruction, validate, publish.
Worker kit vs Agent Skill vs AI plugin
This is the comparison most people arrive with, and the short version is that they answer different questions:
| What it is | What it needs to work | |
|---|---|---|
| Agent Skill | Instructions that teach an agent a technique | An agent, and you, driving it |
| AI plugin | A bundle that installs capability into a client | That client, and you, driving it |
| Worker kit | A whole configured worker for one job | Your connected accounts. It runs itself |
A skill and a plugin extend an assistant you are using. A kit is a worker that runs when you are not there. Each comparison has its own page: Agent Skill vs worker kit and AI plugin vs AI worker.
Four real kits, and what each one shows
| Kit | Apps it uses | What the shape teaches |
|---|---|---|
| Support Inbox Triager | email, tasks | Write access earned by a narrow job: classify, prioritise, draft, file |
| Meeting Prep Assistant | calendar, email, meetingNotes, crm | A four-app loadout, all reads, one output |
| Appointment Reminder Texter | calendar, messaging | Outbound to real people, which is what contact rules govern |
| School Email to Calendar | email, calendar | Open app slots: the kit names the surface, you pick the provider |
That last row is worth pausing on. A kit can leave an app slot open rather than pinning a vendor, so the same kit works whether your mail is Gmail or Outlook. You fill the slot when you take it.
When a kit is not the right starting point
A kit is a shortcut to a tested instruction, and the shortcut stops paying in four situations worth recognising early.
| Situation | Better move |
|---|---|
| The job is specific to your company | Build it in the Studio as a private kit |
| You would edit most of the instruction | Write your own; a rewrite is slower than a draft |
| Its access request exceeds what you will grant | Narrow it, or pick another kit. Never grant to make a kit work |
| Nothing close exists | The job may not be repeatable enough yet |
The third row is the one to hold firmly. A kit asking for more access than your version of the job needs is not a reason to widen the grant; the app firewall lets you refuse and see what the worker still produces, and a kit that only works with sweeping access was probably built for a broader job than yours.
A kit is also not the answer when the work itself should not be unattended: a one-off task, an exact calculation, or anything whose mistakes are not recoverable. Those are properties of the job rather than of the catalog, and no kit fixes them.
When a kit is close but not exact, which is the common case, the answer is usually neither of the extremes above. See when a kit is 80% of what you need.
FAQ
Is a worker kit the same as a prompt template?
No. A prompt template is text you paste into a chat. A kit carries the instruction plus the app permissions, the memories, the schedule and the per-model grades, and taking it mints a real worker in your account with its own key. Nothing about a prompt template runs on Tuesday at 7am.
Does the kit's publisher get access to my accounts?
No. Taking a kit mints a worker in your own account, with its own key and only the access you granted. A kit cannot reach an account you have not connected, and you can narrow or revoke any permission afterwards with the worker still running on what is left.
What happens when a publisher updates a kit?
A kit keeps its address for life, so an update lands on the same page rather than a new URL and every link to it keeps working. Each kit page shows when it was first published and when it was last updated.
Can I keep a kit private?
Yes, on every plan including Free. Private kits are not published to the directory. Team plans can also share private kits across the team without publishing them.
Can I build my own kit without code?
Yes. The Kit Creator Studio is a no-code builder: describe the job, pin the apps and the access each one gets, write the instruction, then validate and publish. Published kits get their own page and a permanent address.
Which models can run a kit?
Claude, ChatGPT, Gemini and Grok, because a kit brings the instructions rather than the model. Every kit page grades itself per model, and each grade is marked measured from real runs or declared by the publisher. See model agnostic.