Installs into .claude/skills of the current project.
Are you the author of Using Iii?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/iii-hq-using-iii-dce9f2da)
<!-- generated by iii-skill-render. DO NOT EDIT (changes here are overwritten on the next render). Edit docs/next/using-iii/workers-registry.mdx. -->
# Worker Registry
## Browsing the registry
The iii Worker Registry at [workers.iii.dev](https://workers.iii.dev/) is the index of installable
workers. Each worker page lists the functions and trigger types it provides, its configuration
schema, supported platforms, and agent skills. Use that information to locate a worker that fulfills
a capability your project needs.
{/* TODO: Add a llm-only note here on how an llm can browse the registry once that surface is stable in the skills worker */}
Workers can also be found on Docker and OCI-compatible registries.
## Adding a worker
`iii worker add` accepts three sources. In every case the worker is added to your project's
`config.yaml` and started automatically.
```bash
iii worker add iii-state # Downloads and adds a worker from iii registry
iii worker add ./workers/my_worker # Adds a local worker created with `iii worker init`
iii worker add ghcr.io/org/worker:tag # Adds a local worker from a Docker or OCI image registry
```
<Note>
For removing workers and the broader `iii worker` subcommand set (start, stop, restart, sync,
verify, etc.), see [Workers](./workers).
</Note>
## Artifact types
Each registry worker is published as either a native binary (with per-platform artifacts for macOS,
Linux, and Windows) or as a Docker / OCI compatible image that runs on every supported platform.
