Beta·every release is a pre-releaseAPIs and harness behavior are still changing·every release until v1 is a pre-release
uzev1.0.0-beta.12
Package manager

Authoring

Write a plugin once and it works in every agent

Ask an agent

The fastest way is to describe what you want, with the uze:author skill:

/uze:author create a plugin with a skill that writes our release notes

The agent picks or creates a marketplace, scaffolds the plugin, checks it, and installs it. Then you iterate on the files, and deliver each change to your agents with uze update <plugin> -m.

What a plugin is

hooks.json
mcp.json
plugin.json

Only plugin.json is required; ship what you need. These are open standards (Agent Plugins, Agent Skills, MCP), not a uze format, so a plugin written for uze is a plugin for everyone.

A skill is a folder with a SKILL.md:

---
name: release-notes
description: Write release notes from the commits since the last tag
---

What the agent should do when this skill runs.

By hand

The same steps the skill runs:

uze agent market create my-market --at ~/my-market   # once
uze agent plugin create my-plugin --market my-market  # --mcp, --hook, --agent
uze agent plugin check ~/my-market/plugins/my-plugin  # validate, offline
uze install -m my-plugin@my-market                    # install it
uze update my-plugin -m                               # after each change

To publish, push the marketplace repository. Anyone can then uze market add it.

On this page