Skill Hub

Find, install, and publish skills and Skill Stacks from the terminal.

The CoDev Skill Hub is a registry of skills published by other teams. codev skill installs them into the same folders CoDev Code scans for your own — see Agent Skills for those — and /stacks in the TUI does it without leaving the chat.

Searching and installing public skills needs no account. Publishing does; the command signs you in, and the session is shared with the codevhub CLI.

Find a skill

codev skill search postgres

Each result shows the skill's name, version, publisher, and id. Add --json for one machine-readable line, --limit <n> to see more than 20.

Install a skill

codev skill pull pg-tuner

Run in a terminal, this asks two questions: where to install (the current directory or your home directory) and which agents the skill is for. CoDev Code is always included; tick Claude Code, Codex, or OpenCode as well if they're on the machine. The skill is extracted once and the other agents' folders are linked to it, so you never end up with three copies.

Where it lands depends on the agents you pick:

Agents	Real copy	Linked
CoDev Code, Claude Code, OpenCode	`.claude/skills/<name>`	—
Any set including Codex	`.agents/skills/<name>`	`.claude/skills/<name>`

Scripts and CI pass the answers as flags instead:

codev skill pull pg-tuner --here --agent claude,codex
codev skill pull pg-tuner --global --all-agents
codev skill pull pg-tuner --dir ./vendor/skills   # an exact folder, no agent layout

A skill that is already installed is refused; pass --force to replace it. There is deliberately no short alias for --force — it deletes a folder that may hold your edits.

Install a Skill Stack

A Skill Stack is a team's whole skill set published as one bundle. Installing one puts every skill in it where a single pull would.

codev skill stack list            # the public stacks, with the slug each one goes by
codev skill stack pull data-eng   # install every skill in the stack

Interactively this previews what the bundle actually contains before asking where to put it. When some of the stack's skills are already installed it stops and asks whether to skip them or overwrite them; the same location and agent flags as pull apply, and --skip-existing or --overwrite answers the question for scripts — which otherwise stop and list the collisions rather than guess.

A stack is not all-or-nothing: a skill that fails to install is reported by name and the rest still land, and a folder in the bundle with no SKILL.md is listed as excluded rather than dropped silently.

Publish your own

codev skill push ./my-skill        # a folder with SKILL.md at its root, or a .zip

You get a preview of the files that will be uploaded and a confirmation before anything is sent. The skill is submitted for review; --draft-only uploads without submitting.

The CoDev Office skills ship as their own offline bundle: codev skill office downloads and installs it. See Office skills.

In the TUI

/skills lists the skills already available in this session and puts the one you pick into the prompt.
/stacks opens the Skill Hub's stacks without leaving the chat: pick one, choose this project or global and which agents, and it installs — asking about skills that are already there, exactly as the CLI does. A skill installed this way is visible to the agent straight away, no restart.

Both have keybinds you can set (prompt_skills and prompt_stacks, unbound by default) — see Keybinds.

In the desktop app

The desktop and web apps have the same registry as a page: the Skill Hub entry in the sidebar, with a tab for skills and one for Skill Stacks. See Skill Hub in the desktop docs.