Turn the job you know into a kit anyone can run.

Who we are looking for

Professionals and experts in their field.

We are looking for people who know a job well enough to hand it over: the specialists, operators and advisors whose way of working is worth packaging. The expertise is the hard part of an AI worker, and it is the part you already have.

• Practitioners. You do the job every week and know its edge cases by heart: the recruiter, the bookkeeper, the support lead, the sales operator. A kit is that routine, written down once and run by everyone who needs it.
• Consultants and agencies. You have a method you repeat across clients. Package it once as a kit and deliver it in a single move, publicly for reach or privately for the client in front of you.
• Specialists in a field. You know the rules of a technical or regulated practice, and what a mistake in it costs. That judgment is what separates a worker that runs from a worker people trust with the real thing.

No code and no prompt engineering: the Studio handles the wiring, so what you bring is the judgment that makes the job come out right.

The Studio

Describe the job. Pin the access. Publish.

A no-code builder with validation at every step, so what reaches the directory is complete: the Job, the Loadout, the Trigger and the Proof.

• Describe the job. One sentence a stranger can act on: what the worker does, in whose apps, to what end. The Studio holds you to it.
• Pin the apps and the exact access. Every app the kit uses, at the level it needs, Off, Read or Write. Installers see the loadout before they take the kit, so asking for the minimum is part of the pitch.
• Validate and publish. The Studio checks the kit end to end before it ships. Public publishes also pass a static security scan on the way out, and the kit goes live at its own address.

The full walkthrough is on the blog: How to publish a kit others can run. The Studio is included on every plan, Free included.

The kit page

A permanent address, working for you.

Every public kit gets its own page in the directory, and the page does the selling.

• An address for life. The page and its link are created at publish and never change. Updates land in place, so the installs, the stars and every link you have ever shared stay with the kit.
• Grades that are earned. Every kit page grades itself per model, and each grade names its provenance: measured from real runs, or declared by you. A measured grade is proof no landing page can fake.
• Live counters. Installs and stars are counted on the page itself and move with the truth, so the evidence that a kit works compounds on its own.
• Your publisher profile. Every kit carries your name, and your profile page collects everything you maintain, with your links and your seals: one address to put in a proposal or a bio.

What installers weigh when they read your page is written up at kit publisher.

Three ways to ship

Public for reach. Private for clients. Protected for craft.

The same Studio builds all three; what changes is who can install it and what they can see.

• Public Listed in the directory with a permanent page. For the jobs that generalise: the kit is your work, doing its own marketing.
• Private Never listed. You or your clients install it directly, which is how consultants ship engagements: the client runs your kit in their own account, with their own grants.
• Protected Installers can run the kit but never read the instruction. The worker does the job; the method that makes it good stays yours.

Private kits are included on every plan; the definition and the trade-offs are at private kit.

The bar

A directory people trust is worth publishing in.

The checks protect installers, and they protect the publishers who do the work properly: your kit sits in a catalog where quality is legible.

• Scanned before it lists. Every public publish passes a static security scan, SkillSpector by NVIDIA, and a scan that raises something goes to a reviewer.
• Verification, visible. Kit cards and pages carry verification seals, Certified and Community, and publisher profiles carry the Official publisher seal, so standing is legible at a glance.
• Permissions in plain words. A kit states the apps it uses and the exact access each one needs before anyone takes it. Asking only for what the job needs is visible craft, and installers reward it.

The platform's own side of the story is on the security page.

Questions

Publisher questions, answered.

• Do I need to code to publish a kit? No. The Kit Creator Studio is a no-code builder: describe the job, pin the apps and the exact access each one gets, write the instruction, validate and publish. The hard part is the expertise, and that is the part you bring.
• Can a kit stay private? Yes. A private kit never lists in the directory: you or your clients install it directly, and on Team plans private kits are shared across the account. Private kits are included on every plan, Free included.
• Can installers read my instruction? Not on a protected kit. Installers can run it, and the worker does the job, but the instruction itself is never shown to them, so the method that makes your kit good stays yours.
• What checks does a public kit go through? Two. At publish, a static security scan, SkillSpector by NVIDIA, runs on every public kit before it lists. After publish, a scan that raises something goes to a human reviewer, and the kit's page shows its scan state.
• What does publishing cost, and what do I earn? Publishing is included on every plan, and kits are free for others to install; installers pay for their own runs. There is no revenue share today. What publishing earns you is distribution and proof: a permanent page with live install and star counts, per-model grades, and a publisher profile that collects everything you maintain.
• What happens when I update a published kit? The update lands in place. A kit keeps its address for life, so the page, the installs, the stars and every link you have shared stay with it, and the page shows when it was first published and last updated.

The Studio is open now. Building for clients at scale, or connecting a product of your own? The partner programs are next door.