Getting started
From nothing installed to an agent that reaches for these skills on its own
Three steps: get UZE, register this marketplace, take the plugins you want.
1. Install UZE
UZE is the runtime that installs and delivers these plugins. If you already have it, skip to step 2.
$ curl -fsSL https://uze.hiukky.com/i | shLinux, x86_64 or aarch64, checksum verified. Anything else, build from source: see uze.hiukky.com/docs/getting-started.
Then let it find the coding agents you already have, and provision the ones you don't through each vendor's own installer:
uze setup2. Register the marketplace
$ uze market add hiukky/aiThat resolves hiukky/ai as a Git repository and registers it under the alias
ai. From here on, every plugin in the catalog is addressed as <name>@ai.
On a dotfiles-managed machine where this repo is already cloned locally, uze setup picks it up and you can skip this step.
Check what it found:
uze list3. Install a plugin
Two scopes, and they never touch each other's state.
Machine-wide, available in every project on this machine:
uze plugin install openspec@ai
uze plugin install git@ai
uze plugin install tui@aiProject-scoped, written into the current project's agents.lock, so the
project carries its own tooling and anyone who checks it out gets the same set:
uze openspec@aiopenspec@ai bootstraps a project's scaffolding when you run its init
skill: openspec/, docs/adr/, docs/architecture/likec4/, plus edits to
openspec/config.yaml. Every step is idempotent and checks before writing,
but it is still a change to your repository. That is exactly why init is
the one skill here declared user-only: the model will never trigger it
because a sentence sounded close enough.
4. Use them
Nothing else to wire up. The skills are already discoverable, so an agent reaches for them when the work matches:
- Finish a coherent unit of work and
git:commitwrites the Conventional Commit and pushes it, without being asked. - Make a decision that clears the bar (a new dependency, a boundary expensive
to move later) and
openspec:adroffers to record it underdocs/adr/. - Ask for a demo of a TUI and
tui:recorddrives the take, cuts the waiting, and scans the result for your username before it ships.
Call one by name when you want it explicitly. In Claude Code that is a slash
command; in other harnesses it is whatever that harness calls native. UZE
derives the surface from each skill's invoke: policy.
Verify
uze list # marketplaces, plugins, what is installed where
uze context inspect # what each detected harness is actually reading
uze doctor # store, harnesses, attachment health