🤖 Personal hub for AI-focused resources: agents, skills, MCPs, hooks
Overview
A uze marketplace of self-contained plugins: an engineering standard, git conventions, a toolkit for recording terminal UIs, and a machine kept as a build product of its dotfiles. Install a plugin once and Claude Code, Codex, OpenCode and Antigravity each receive its skills through their own most native surface. Every skill declares who may invoke it in its own frontmatter. The default is model user, so an agent can reach for it and a person can call it by name. init is deliberately user-only. Into a project, so everyone who clones it gets the same plugins. uze writes agents.yaml (what the project wants) and agents.lock (the commit it resolved to); commit both. On a fresh clone, uze install rebuilds the same set; uze update is what moves it forward. Or on this machine only, for every project and none.
README
Plugins
| Skills | ||
|---|---|---|
openspec |
init · auto · adr |
Spec-driven change workflow (proposal → specs → design → tasks), run unattended by auto, with ADRs written only at archive time and Mermaid diagrams kept current per change |
git |
commit · pr |
Conventional Commits and gitflow-named pull requests, committed proactively once a unit of work is done, not only when asked |
tui |
record |
A TUI turned into a demo video, generated from a spec: one file says what the video shows and how to rebuild the sandbox it was recorded in |
env |
sync · reclaim |
The machine as a build product of its dotfiles, installed by writing its lane in the chezmoi source and never by hand, with its disks kept in check: prune what regenerates, decide the rest, shrink the WSL disk last |
Every skill declares who may invoke it in its own frontmatter. The default
is model and user, so an agent can reach for it and a person can call it
by name. init is deliberately user-only.
Install
Needs uze on the machine:
curl -fsSL https://uze.sh/i | sh
Into a project, so everyone who clones it gets the same plugins. uze writes
agents.yaml (what the project wants) and agents.lock (the commit it
resolved to); commit both.
uze openspec@ai
uze git@ai
On a fresh clone, uze install rebuilds the same set; uze update is what
moves it forward.
Or on this machine only, for every project and none. This is the natural
scope for env, which is about the machine itself:
uze install env@ai -m
uze install tui@ai -m
uze inspect shows what a plugin carries and how each agent
receives it; uze status (or -m) shows what is installed where.
Developing
Link the marketplace to a checkout and installs read its working tree, uncommitted files included, so there is no publish step while iterating:
uze market link ai ~/ai
uze agent plugin check env # the parsers an install runs, offline
uze agent market check .
uze update env -m # re-deliver after an edit
Layout
marketplace.json Catalog ┐ the only two things here
web/ Docs ┘ that aren't plugins
/
plugin.json Manifest (Agent Plugins 1.0)
skills/ Capabilities, one SKILL.md each
agents/ Subagents ┐
hooks/ Hook configs ├ created only when used
resources/ Runtime files │
.mcp.json MCP servers ┘
Docs
The site under web/ is the catalog with prose around it: what each
plugin carries, what each skill does, and what makes it fire.
cd web && bun install && bun run dev
Its catalog is generated from this repository at build time:
marketplace.json for the roster, each plugin.json for the manifest, each
SKILL.md’s frontmatter for the capability and its invocation policy. A skill
renamed here is renamed there on the next build, and no page can describe one
that no longer exists.
How uze itself installs, delivers and updates plugins is documented at uze.sh/docs.
Author: Romullo Sousa (hiukky)
Built with 🖤 by hiukky
Install
This server does not publish a one-line install command.
Open the repository installation guide