Skills Control Plane

Install a skill once and use it in every project — a versioned local library, per-project version pins, and a manifest you can commit.

Skills are usually copied per project, which means five projects hold five slightly different copies of the same instructions and nobody remembers which one is current.

The Control Plane view in the Skills dialog replaces that with a versioned library on your machine, plus a per-project pin saying which version each project gets.

The library

Install a skill once. The library keeps every version you have installed, and each library skill lists the projects that pinned it and the version they are on — so "who is still on v2?" is a glance, not an audit.

Pinning and applying

For each project, choose:

  • Which version of the skill it gets
  • Which agent directory it lands in — Claude, Cursor, Codex, or Kimi

Then Apply. Apply always shows exactly what it will link, switch, and remove before it touches anything.

A real skill folder is never overwritten silently. If a project already has a hand-written skill of that name, it is reported as a conflict and left alone until you say otherwise.

Skills are applied as links rather than copies, which is what makes a version change a repoint instead of a re-copy.

Sharing a skill set with your team

The manifest lives in your project at .1devtool/skills-manifest.json. Commit it and everyone on the repo gets the same skills at the same versions — the skill equivalent of a lockfile.

Rolling forward and back

Pick an older version from the row to roll a project back, or repin every outdated skill to the newest in one click when you want the whole machine current.

Related