Skills Manager

Skills Control Plane

Install a skill once into a versioned library on your machine, then pin which version each project gets and which agent directory it lands in. Applying links rather than copies, and the manifest commits with your repo so a team shares one skill set.

Skills Control Plane

Why You Need This

How this feature boosts your daily productivity

Copying a skill into each project is how you end up with four versions of the same skill and no idea which project has which. Improve one three weeks later somewhere else and the drift is invisible until an agent behaves differently in one repo than another. The Control Plane keeps a single append-only library at `~/.1devtool/skill-store`, and each project selects from it through `.1devtool/skills-manifest.json` — pinned by version, targeted at Claude, Cursor, Codex or Kimi. Apply shows exactly what it will link, switch and remove before touching anything, and a real folder you copied in by hand is reported as a conflict rather than silently overwritten. Because versions are kept rather than replaced, you can drop back to an older one or repin every outdated skill to the newest in one click — and each library skill lists the projects that pinned it, so "who is still on v2" is a glance instead of an audit.

How It Works

Get started in 4 simple steps

1
1

Open the Control Plane

A new view in the Skills dialog backed by an append-only library at ~/.1devtool/skill-store, so a skill is installed once on your machine instead of copied into every project.

2
2

Pin a version per project

Choose which version each project gets and which agent directory it lands in — Claude, Cursor, Codex or Kimi. Each library skill also lists the projects that pinned it and the version they are on.

3
3

Apply and see it first

Apply shows exactly what it will link, switch and remove before it touches anything, then writes symlinks (junctions on Windows). A real folder you copied in by hand comes back as a conflict rather than being silently overwritten.

4
4

Commit the manifest

The selection lives at .1devtool/skills-manifest.json in your project, so committing it gives everyone the same skills at the same versions. Drop back to an older version, or repin every outdated skill to the newest, in one click.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# Copy the skill folder into the project
# Improve it three weeks later, somewhere else
# Now four projects have four versions
# No idea which project has which
# New teammate: "here are some folders to copy"

The 1DevTool Way

One versioned library at ~/.1devtool/skill-store.
Each project pins the version it wants.
Apply shows every link and removal first.
Commit the manifest — cloning brings the skills.

Key Capabilities

Everything included with Skills Control Plane

Install a skill once into a versioned library on your machine
Pin which version each project gets, independently
Target Claude, Cursor, Codex or Kimi skill directories per project
Preview every link, switch and removal before applying
Keep a hand-copied skill folder safe as a reported conflict
Roll back to an older version from the row
Repin every outdated skill to the newest in one click
See which projects pinned a skill and at which version
Commit .1devtool/skills-manifest.json to share the set with your team

Why It Matters

The productivity impact of having skills manager built into your workspace

Curated Skill Registry

Browse and install AI agent skills from a curated registry instead of searching GitHub and reading docs.

Security Scanning

Every skill is rated from Safe to Critical risk. Know exactly what you're running before you run it.

Custom Skill Creation

Write your own skills with a proper editor. Turn your best prompts into reusable, shareable assets.

Multi-Agent Support

Skills work across Claude Code, Codex, Gemini, Amp, and more. One library, all your agents.

Ready to boost your workflow?

Download 1DevTool for free and experience Skills Control Plane along with 170 other features — all in one app.