Skill Hub
Skill Hub in the sidebar, just above Settings, opens the CoDev Skill Hub inside the app: skills published by other teams, installed into your projects without leaving the chat.
It has two tabs. Skills is the registry one skill at a time. Skill Stacks is whole sets — a team's curated skills, installed together.
Browse skills
The Skills tab searches the registry, sorts it (Featured, Newest, Most downloaded, Top rated) and filters it by domain (Developer, Personal assistant, Workflow builder). A card opens the skill's page: its SKILL.md as the agent will read it, the author, stars and download count, and a link to the same skill on the Skill Hub site.
Install a skill
-
Open a skill and press Install.
-
Choose where it goes. This project installs into one of the projects the app knows about — pick which; Global (all projects) installs into your home directory.
-
Choose which agents it is for. CoDev Code is always included; tick Claude Code, Codex or OpenCode as well if they are on the machine. The skill is put on disk once and the other agents' folders are linked to it.
-
Press Install. The dialog lists the exact folders it wrote.
If the skill is already installed, the dialog says where and offers to Overwrite it — which discards any edits you made to that copy — or you can cancel and keep yours.
Where a skill lands follows the same rule as codev skill pull in the terminal: .claude/skills/<name> (or ~/.claude/skills/<name> for global) when the agents are CoDev Code, Claude Code and OpenCode; .agents/skills/<name> with a link from .claude/skills once Codex is among them. See Skills for what the app scans.
Install a Skill Stack
A stack card shows who curates it, how many skills and members it has, and a preview of the skills inside. Install asks the same two questions — where, and for which agents — then downloads the bundle and checks it against what you already have.
When some of the stack's skills are already installed, it stops and names them, and asks:
- Skip them, install the rest — your copies are left exactly as they are.
- Overwrite them — the stack's versions replace yours, and any local edits to them are lost.
Cancelling at that point installs nothing. When nothing collides, the whole stack installs straight away.
A stack is not all-or-nothing. The result lists every skill as installed, skipped, or failed, so one broken skill never costs you the others.
Signing in
Browsing and installing public skills needs no account. When the hub asks for a signed-in session — a private skill, or publishing — the install dialog offers Sign in and runs the same browser sign-in the app uses elsewhere. That sign-in is shared with codev skill and codevhub in the terminal, so signing in once covers all three.
The sign-in button only appears when the app is running the server on this computer. Connected to a server elsewhere, sign in on that machine instead — codev skill push in a terminal there will offer it.
Where the install happens
The app doesn't install skills itself. It asks the server your session runs on, and the server downloads the skill and installs it where the agent actually runs. That is what makes This project valid for every project the app shows — including one on a WSL distro, in a sandbox, or on a remote server — and it is why the Skill Hub is also available in the web app.
A skill installed this way is visible to the agent straight away: the server's skill list is refreshed as part of the install, so there is nothing to restart. Skills you add by hand still need the restart described in Picking up a new skill.
From the terminal instead
Everything the Skill Hub does is also a command: codev skill search, codev skill pull, codev skill stack list, codev skill stack pull, and codev skill push to publish your own. See Skill Hub in the CoDev Code docs. In the terminal app, /stacks opens the same stack browser inside the chat.