Personal AI tooling. Portable by default.

Skills your agent
already knows.

A uze marketplace of self-contained plugins: an engineering standard, git conventions, a toolkit for recording terminal UIs. Every capability is a skill an agent reaches for on its own, in whichever coding agent you happen to be in.

$ uze market add hiukky/ai

The catalog

Grouped by what the capability is about, not by how it is invoked. Each plugin is self-contained: its own manifest, its own skills, its own bundled resources, installable on its own, with nothing shared between them.

  • openspec

    2 skills

    Personal engineering standard: OpenSpec (proposal/specs/design/tasks) extended with optional ADRs for durable, hard-to-reverse decisions, plus LikeC4 for living architecture diagrams.

  • git

    2 skills

    Personal git workflow conventions: a Conventional Commits skill and a pull/merge request skill (gitflow branches, conventional titles).

  • tui

    1 skill

    Terminal UI media - starting with a record skill that generates a demo video from a spec: one file says what the video shows and how to rebuild the sandbox it was recorded in.

* marks a skill whose invocation policy is narrowed, see below.

Every capability is a skill

There is no commands directory. A capability's logic lives in one SKILL.md, and the same file declares who may invoke it. uze derives each vendor's surface: a slash command, a $name, plain auto-discovery, all from that one policy.

  • model + user

    The default

    No invoke: block at all. The agent finds the skill on its own when the work matches, and a person can still call it by name. Almost every skill here is this.

  • user only

    A deliberate action

    model: false. Something that rewrites a project’s scaffolding once and should never fire because a sentence sounded close enough. openspec:init is one.

  • model only

    Background work

    user: false. A capability that has no meaning as a command someone types. Nothing here needs it yet, but the slot exists so the policy stays a policy, not a convention.

Every skill, and what triggers it

Installed through

uze

ai is a catalog, not a runtime. uze owns a plugin's bytes and delivers them to every coding agent on the machine through that agent's own native mechanism, so a skill taken from here turns up in all of them.

uze.hiukky.com
  • Claude Code
  • Codex
  • OpenCode
  • Antigravity

Then take what you need

uze plugin install puts a plugin on the machine for every project. Dropping the subcommand scopes it to the project you are in and writes it to that project's agents.lock instead.

openspec

$ uze plugin install openspec@ai

git

$ uze plugin install git@ai

tui

$ uze plugin install tui@ai

No uze yet? curl -fsSL https://uze.hiukky.com/i | sh. Linux, x86_64 or aarch64, checksum verified. Everything else it does ↗