Skip to main content
Skills are reusable capabilities you give your agents — packaged instructions and helpers an agent loads on demand. A skill can teach an agent your conventions, wrap a tool, or encode a workflow you repeat. Avibe manages them in one place, across every backend, so you set them up once instead of re-explaining your work every session.

​
What a skill is

A skill is a small bundle — a SKILL.md of instructions plus any commands or helpers it needs — that an agent pulls in when a task calls for it. Skills range from “follow our PR workflow” to “use this CLI to query Sentry” to “search large files with ripgrep.” The agent loads a skill only when it’s relevant, so the working context stays lean.

​
One library, every agent

  • Manage global skills (available in every project) and per-project skills from the Workbench.
  • The same skills layer works across Claude Code, Codex, and OpenCode — you don’t redo setup per agent. A skill can target one backend or all of them.
  • Browse a registry and install a skill with a click, or add your own from a Git source.
  • Avibe manages skills through the open askill toolchain, installed as a managed dependency so it’s ready when you need it.

​
Global vs per-project

  • Global skills are your standing toolkit — conventions and helpers you want everywhere.
  • Per-project skills live with a repo: its build steps, its test commands, its house style — so an agent picks them up only in that project.
Both kinds are visible side by side in the Workbench, with their source and version, and they apply no matter which backend runs the task.

​
A quick example

Say every repo at your shop follows the same review flow. Capture it once as a skill — “branch, commit with a conventional message, open a non-draft PR, wait for review, fix, merge” — and every agent you run can follow it without you spelling it out again. Add a second skill that wraps your deploy CLI, and “ship it” starts meaning the same thing to all three backends.

​
Why it matters

Skills are how an agent gets better at your work over time — your conventions, your workflows, your repeated tasks — without you re-explaining them every session. Set them up once; every agent you run inherits them. As the library grows, so does the leverage of every new session. → Manage them in the Workbench · part of the Agent OS world model.