Bezi turns repeated Unity workflows into slash commands
By Steven Van ·
New Skills feature saves multi-step prototyping, debugging, and build-prep routines for one-command reuse.
On July 1, 2026, Bezi introduced Skills, a new way to capture the workflows you run over and over inside Unity and fire them off with a single slash command. If you find yourself repeatedly walking the AI agent through the same steps to prototype a feature, debug physics, or prep a build, Skills lets you save that routine once and reuse it instantly.
Repeated workflows become one slash command
Every game project accumulates rituals: spinning up a test scene, wiring a new gameplay feature, chasing down a physics glitch, or running the checklist before a build. Bezi Skills lets you turn any of these repeated sequences into a named slash command. Instead of re-explaining the same multi-step process to the agent each time, you type the command and Bezi executes the workflow with the full context of your project. It is the difference between narrating a recipe every session and just pressing a button.
Built on Bezi's deep Unity understanding
Skills sit on top of the same foundation that already makes Bezi useful inside Unity. Bezi real-time indexes your scripts, assets, scenes, packages, and extra context like local folders and design docs, so a Skill does not run blind. When you trigger a prototyping or debugging Skill, it operates with awareness of your actual GameObjects, prefabs, components, and script interactions. That context is what separates a reusable Skill from a generic prompt template that has to relearn your project every time.
Prototyping, debugging, and build prep out of the box
The launch highlights three concrete use cases. Prototyping a feature can chain together script generation, GameObject creation, and component configuration into one call. Debugging physics can trace the interactions between scripts, scene objects, and colliders to pinpoint the source of a problem and propose a targeted fix. Prepping a build can bundle your pre-release checks into a repeatable routine. Because Bezi's Agent Mode implements changes with reviewable diffs and checkpoints, every Skill-driven change can still be inspected, accepted, or undone before it touches your game.
Why it matters for solo devs and studios
For solo developers, Skills cut down the friction of context-switching and reduce the tedious re-typing that eats into building time. For studios, a Skill is effectively a shareable, standardized workflow: teams can encode their conventions once and let everyone invoke them consistently. It follows Bezi's broader 2026 direction, from Actions operating inside the engine to Workspaces adding persistent shared knowledge, of moving the AI from an advisor that answers questions to an agent that carries out the work you repeat most.
Sources: bezi.com, Bezi Changelog, Introducing Actions.