Skill Manager
OSS Claude Code, Codex, Cursor, Gemini CLI, VS Code & more — fully supported

One dashboard for
every agent skill.

Discover, enable, disable, edit, and delete AI coding agent skills across Claude Code, Codex, Cursor, Gemini CLI, VS Code, Roo Code, Kiro, Junie, Crush, Factory Droid, and OpenCode — instead of digging through a dozen different config folders by hand, and letting every skill you've ever installed sit there active.

v0.3.1 · free · open source · mit licensed · all downloads

Skill Manager: browsing all installed skills, filtering by tool, searching, and opening a skill's SKILL.md in the view/edit modal

actual screen capture — not a mockup · 74 skills across four tools, one list

the concept

What's a skill?

Anthropic introduced Agent Skills — a folder with a SKILL.md manifest describing when an agent should reach for it, and what to do once it does. The idea spread fast: Claude Code, Codex, Cursor, Gemini CLI, and OpenCode all read the same shape now, just from their own directory.

Which is exactly the problem. Many tools, many folders, and the moment you're using more than one of them, nothing shows you the whole picture.

~/.claude/skills/pdf-tools/SKILL.md
---
name: pdf-tools
description: Read, edit, merge, and
  split PDF files.
---
the problem

Past a certain count, it's skill hell.

Every skill you've ever installed sits there active, and your agent has to disambiguate against all of them just to trigger the right one for what you're doing right now. A crowded skills directory doesn't just look messy — it makes the agent worse at picking. Disabling what you don't need for the project you're in is how you climb back out.

Without Skill Manager With Skill Manager
See what's installed Open a terminal, ls a dozen different folders One dashboard, every tool
Turn a skill off Delete the folder and hope you don't need it back Toggle it — fully reversible
Keep triggering accurate Every installed skill competes for a match, even irrelevant ones Disable the noise, leave only what's relevant
Know what's wired into a project Global and project-level skills look identical until something breaks Per-project breakdown, separate from global
Edit a SKILL.md Open a text editor, hunt down the path Rendered markdown, one-click raw edit
features

Everything the config folders won't show you.

Unified view

See every tool's skills directory in one dashboard instead of digging through ~/.claude, ~/.agents, and friends.

Enable / disable

Toggle a skill off without deleting it — fully reversible, never touches the tool's own config.

Keep triggering accurate

Fewer active skills means fewer candidates competing for a match — disable what's irrelevant to the project you're in.

View & edit

A skill's SKILL.md renders as formatted markdown by default, with a one-click switch to raw edit.

Per-project breakdown

Track individual project folders and see exactly which skills are installed inside each one.

Detected projects

Folders you already work in — found via Claude Code history, editor recents, and git repos — appear as one-click suggestions with activity times and skill counts. No folder-picker spelunking.

Pinned & most-used first

Pin the tools and projects you touch daily. The sidebar keeps your three most-used projects (30-day window) on top, and every list can sort by use or by skill count.

Search

Find a skill by name or description across every tool, without leaving the dashboard.

coverage

Supported tools

All paths are verified against each tool's own docs — not guessed.

Tool User-level directory Project-level directory Status
Claude Code ~/.claude/skills .claude/skills fully supported
Agents (shared) — Codex, Goose, Amp ~/.agents/skills .agents/skills fully supported
Cursor ~/.cursor/skills .cursor/skills fully supported
Gemini CLI ~/.gemini/skills .gemini/skills fully supported
VS Code / Copilot ~/.copilot/skills .github/skills fully supported
Crush ~/.config/crush/skills .crush/skills fully supported
Roo Code ~/.roo/skills .roo/skills fully supported
Kiro ~/.kiro/skills .kiro/skills fully supported
Junie ~/.junie/skills .junie/skills fully supported
Factory Droid ~/.factory/skills .factory/skills fully supported
OpenCode ~/.config/opencode/skills .opencode/skills fully supported
roadmap

What's next.

v0.2.0 shipped the full ecosystem and smart project setup. v0.3.0 makes project discovery privacy-first. The focus moves to:

faq

Before you ask.

Does this modify how my tools load skills?

No. Skill Manager only moves folders between a skills directory and a sibling .disabled folder, and edits SKILL.md files directly on disk. It never touches a tool's own config or settings files.

Is it safe to disable a skill?

Yes — disabling moves the skill folder to .disabled next to it. Re-enabling moves it back. Nothing is deleted until you explicitly delete it.

Does it phone home or collect telemetry?

No. Skill Manager is a local desktop app — it only reads and writes the skill directories already on your machine.

Why isn't my tool supported?

Open an issue with a link to that tool's own skills documentation and an adapter will be added — see contributing below.

Why does macOS/Windows warn that the app isn't verified?

v0.3.1 is not code-signed or notarized by Apple, and its Windows installer is not signed by a verified publisher. We have not completed Apple or Microsoft publisher verification. Only continue if you downloaded it from this project's GitHub Releases page. Code-signed releases are on the roadmap. We know the extra steps are inconvenient; optional sponsorship helps fund code-signing and notarization work. Until then:

macOS — click Done on the warning, then either right-click the app in Finder → OpenOpen again in the dialog, or go to System Settings → Privacy & Security, scroll to the blocked-app notice, and click Open Anyway (then confirm once more). You only need to do this once.

Windows — click More info on the SmartScreen warning, then Run anyway.

Built by a handful of small PRs.

Pin down a tool's real skills directory, add support for a new agent, or fix a bug. Every one of these is scoped to be doable in one sitting.