One Skill Library for Every AI Coding Agent

Import once, choose where each Skill runs, and keep Claude Code, Codex, Cursor, and 28 other coding tools in sync. Scan community Skills before you install.

Free · MIT licensed · Local-first · macOS, Windows, and Linux
Skills Manager connections for Claude Code, Codex, Cursor, and other tools
900+GitHub stars
31AI coding tools
3desktop platforms
MITopen-source license
Compatibility

Use the same Skills where you already work

Skills Manager detects the AI coding tools installed on your machine and connects each one to the same central library, so a Skill you write once is available everywhere you work.

Claude Code
Codex
Cursor
Gemini CLI
OpenCode
Windsurf
Cline
Antigravity
Vercel Skills
Trae
Qwen Code
Augment

and 19 more tools — see the full directory matrix below

Compatibility matrix

Where each of the 31 supported tools reads its Skills

One Skill, one source file in ~/.skills-manager/skills — Skills Manager writes the connection into the directory each tool already scans. Everything stays single-copy and reversible.

ToolSkills directoryDetected byConnection
Claude Code~/.claude/skillsclaudeSymlink / Junction
Codex~/.codex/skillscodexSymlink / Junction
Cursor~/.cursor/skillscursorSymlink / Junction
Gemini CLI~/.gemini/skillsgeminiSymlink / Junction
OpenCode~/.config/opencode/skills~/.opencode/skillsopencodeSymlink / Junction
Windsurf~/.windsurf/skillswindsurfSymlink / Junction
Cline~/.cline/skillsclineSymlink / Junction
Antigravity~/.antigravity/skillsantigravitySymlink / Junction
Vercel Skills~/.agents/skills~/.vercel/skills~/.vercel-skills/skillsvercelSymlink / Junction
Trae~/.trae/skillstraeSymlink / Junction
Qwen Code~/.qwen/skillsqwenSymlink / Junction
Augment~/.augment/skillsaugmentSymlink / Junction
CodeBuddy~/.codebuddy/skillscodebuddySymlink / Junction
Droid~/.factory/skills~/.droid/skillsdroidSymlink / Junction
OpenClaw~/.openclaw/skillsopenclawSymlink / Junction
CommandCode~/.commandcode/skillscommandcodeSymlink / Junction
Continue~/.continue/skillscontinueSymlink / Junction
Crush~/.config/crush/skills~/.crush/skillscrushSymlink / Junction
Goose~/.config/goose/skills~/.goose/skillsgooseSymlink / Junction
iFlow~/.iflow/skillsiflowCopy mode
Junie~/.junie/skillsjunieSymlink / Junction
Kilo Code~/.kilocode/skillskiloSymlink / Junction
Kiro~/.kiro/skillskiroSymlink / Junction
Qoder~/.qoder/skillsqoderSymlink / Junction
Roo Code~/.roo/skillsrooSymlink / Junction
Zencoder~/.zencoder/skillszencoderSymlink / Junction
Pi~/.pi/agent/skillspiSymlink / Junction
Trae CN~/.trae-cn/skillstraeSymlink / Junction
Hermes~/.hermes/skillshermesSymlink / Junction
WorkBuddy~/.workbuddy/skillsworkbuddySymlink / Junction
QoderWork CN~/.qoderworkcn/skillsqoderworkcnSymlink / Junction

Symlinks on macOS and Linux; on Windows the app falls back from symlink to junction, so no admin rights are needed. Copy mode is used only for iFlow, which does not follow links.

Tool not in the list?

Add a custom tool by pointing Skills Manager at its configuration directory. The same library, toggles, and security scan apply to it.

Workflow

One source of truth. No more copied folders.

Skills Manager keeps your canonical Skills in one library, then creates and maintains the connections each coding agent expects.

Central Skill library~/.skills-manager/skills
Connected tools
Claude Code
Codex
Cursor
Gemini CLI
01

Import once

Bring existing Skills into one managed library without rebuilding your setup.

02

Choose each tool

Enable or disable a Skill per tool while keeping the source file untouched.

03

Stay in sync

Symlink-based connections make edits available across tools without manual copies.

Your entire skill system, visible at a glance

See every Skill, every connected tool, and every marketplace install in one focused workspace.

Skills Manager unified Agent Skills library
Getting started

From download to synced Skills in three steps

Skills Manager does not ask you to restructure anything first. It reads the Skills you already have, then takes over the wiring between them and your tools.

  1. 01

    Install and let it detect your tools

    Download the build for your platform and open it. Skills Manager probes all 31 built-in tool directories and lists the ones it finds.

    No account, no CLI setup. Detection is read-only — nothing is written until you enable a Skill.

  2. 02

    Import your existing Skills into one library

    Point the app at the Skills already sitting in folders such as ~/.claude/skills. They move into the central library at ~/.skills-manager/skills.

    Duplicates across tools collapse into one entry — you stop maintaining the same Skill in several places.

  3. 03

    Toggle each Skill per tool

    Flip a switch and the link appears inside the tool’s Skills directory. Flip it back and the link is gone — the source file is never modified.

    Every tool points at the same file, so one edit lands everywhere at once.

Typical setup timeUnder 5 minutes

Security

Inspect a Skill before you trust it

Run local static checks for dangerous commands, hidden downloads, privilege escalation, and suspicious instructions before enabling a Skill.

Local static scan

Deterministic rules run on your machine and keep source files private.

Optional LLM review

Add a second opinion for ambiguous or context-dependent findings.

Actionable findings

Review the exact file, severity, rule, and remediation before installation.

Security scan
Review complete
security-audit/SKILL.md
Destructive commandsClear
Network exfiltrationClear
Privilege escalationClear
Instruction overrides1 review
Security scanning

36 deterministic rules across four risk categories

A Skill can contain commands the agent will execute, so installing one from the internet is like running a script you did not read. Skills Manager scans the entire folder locally before you enable it — deterministic rules, same input, same verdict.

destructive.*9 rules

Destructive commands

Commands that delete, overwrite, or destroy data on the machine running the Skill.

  • destructive.rm_rf_root
  • destructive.mkfs
  • destructive.dd_to_device
  • destructive.fork_bomb
network.*9 rules

Network and exfiltration

Reverse shells, exfiltration, and anything that ships local files or credentials off-machine.

  • network.pipe_to_shell
  • network.nc_reverse_shell
  • network.curl_with_creds
  • network.scp_to_remote
privilege.*9 rules

Privilege and persistence

Sudo, permission loosening, and edits that help the Skill survive a reboot or hijack later commands.

  • privilege.sudo
  • privilege.write_shell_rc
  • privilege.crontab_persist
  • privilege.path_hijack
payload.*9 rules

Obfuscation and hidden payloads

Base64-decoded execution, zero-width characters, and other tricks aimed at hiding intent.

  • payload.base64_decode_exec
  • payload.eval_exec
  • payload.zero_width_chars
  • payload.rtl_override

Five severity levels

Each finding carries a confidence score mapped to a severity ladder. The report shows the highest severity first, then the exact file and line.

  • Criticalconfidence ≥ 0.95
  • Highconfidence ≥ 0.80
  • Mediumconfidence ≥ 0.60
  • Lowconfidence ≥ 0.40
  • Safebelow 0.40

Context lowers false positives

A rm -rf line inside a doc example is not the same as one inside an instruction. The scanner records where each match appeared and weights it accordingly.

  • Inside a Markdown code example
  • On a comment line
  • Under a docs/ directory
  • Language of the surrounding code block
Skills Manager built-in Agent Skills marketplace
Marketplace

Discover, install, and translate without breaking flow

Browse community Skills inside the desktop app, inspect their source, install with one action, and translate content when needed.

Multiple sources

Browse Skills from supported community catalogs and GitHub repositories.

Bilingual workflows

Translate Skill names, descriptions, and instructions between English and Chinese.

Comparison

Less maintenance. More control.

Manual folders work until every agent needs its own copy. Skills Manager keeps the workflow visible and reversible as your toolset grows.

WorkflowManual foldersSkills Manager
Canonical Skill sourceOne copy per toolOne central library
Per-tool enable controlsMove files by handBuilt-in toggles
Tool discoveryFind every path yourselfAutomatic detection
Security reviewRead every file manuallyLocal static scan
English and ChineseTranslate by handIntegrated translation
Concepts

Agent Skills, SKILL.md, and why they need managing

Agent Skills are the portable format AI coding agents load on demand. Getting them right starts with knowing what a Skill is — and what it is not.

Agent Skill
An Agent Skill is a folder containing a SKILL.md file plus any scripts or templates it needs. Agents index the front matter of every SKILL.md up front, and load the body only when a task matches the description — so a large library never floods the context window.
SKILL.md
SKILL.md is the entry point of a Skill: a Markdown file opening with YAML front matter. The front matter is what agents index; the body is what they follow after the Skill triggers. A folder without SKILL.md is simply ignored.
Skills directory
Every tool scans its own directory: Claude Code reads ~/.claude/skills, Codex reads ~/.codex/skills, Cursor reads ~/.cursor/skills. Different paths per tool is why the same Skill historically ends up copied into every one of them.
The management problem
Copies drift: edit a Skill in ~/.claude/skills and the copy in ~/.codex/skills keeps the old behaviour. Skills Manager keeps one canonical folder and links it into each tool, so an edit lands everywhere at once.

Anatomy of a SKILL.md file

Agents index the front matter and match it against the task. The description decides whether the Skill loads at all — write it more carefully than the name.

  • nameRequired

    Lowercase identifier for the Skill. Convention is to match the folder name, using hyphens instead of spaces.

  • descriptionRequired

    What the Skill does and when to use it. Write both halves — the trigger condition is what makes the Skill fire at the right moment.

  • allowed-toolsOptional

    Restricts the Skill to a specific set of tools. Supported by Claude Code; other agents ignore fields they do not recognise.

  • Markdown bodyRequired

    The instructions the agent follows after the Skill is triggered. Keep it short and imperative; link out to reference files for anything long.

SKILL.md
---
name: release-notes
description: Drafts release notes from merged pull requests. Use when
  the user asks for a changelog or release summary for a version tag.
allowed-tools: Bash(git log:*), Read, Write
---

# Release notes

1. Collect merged pull requests since the previous tag.
2. Group them by type: feat, fix, perf, docs.
3. Write one line per change, newest first.
Skills vs MCP

Agent Skills and MCP servers solve different problems

Skills and MCP servers are not alternatives. A Skill encodes a procedure; an MCP server grants access to a system the agent cannot reach on its own. Most real setups use both.

DimensionAgent SkillsMCP servers
What it addsProcedure and domain knowledgeConnections to external systems
FormatA folder with SKILL.md and support filesA running server speaking a JSON-RPC protocol
Runtime costNone until the Skill is triggeredA process and a live connection per server
Loaded whenThe task matches the descriptionThe agent starts, tools listed up front
Authoring effortWrite MarkdownWrite and ship a server
Best fitRepeatable workflows, house style, checklistsDatabases, ticketing, internal APIs

Rule of thumb: a task you can write down is a Skill; a task that needs live data or credentials is an MCP server. Skills Manager manages the first.

Specifications

What you are installing

A Tauri desktop app that runs locally, reaching the network only for features you explicitly start.

Current version
2.1.8
License
MIT
Price
Free, no paid tier
Platforms
macOS (Apple Silicon and Intel), Windows 10+, Linux
Package formats
.dmg, .exe, .msi, .AppImage, .deb, .rpm
Built-in tool definitions
31, plus custom tools
Central library
~/.skills-manager/skills
Connection method
Symlink on macOS and Linux, junction on Windows
Security rules
36 local static rules, 5 severity levels
Account required
No, for local Skill management
Interface languages
English and Simplified Chinese
Who built this

Every number on this page can be checked in the repository

Skills Manager is maintained by one developer in public. This section states who wrote the page, where each claim comes from, and what the product deliberately does not do.

Maintainerjiweiyeah@jiweiyeah

Independent developer and sole maintainer of Skills Manager. Wrote the Rust linking layer that swaps between symlinks, Windows junctions, and tracked copies, the static rule engine behind the security scan, and the tool definitions for every supported agent.

Why this exists

The first version came out of a problem I had myself: running Claude Code and Codex side by side meant keeping the same Skill in ~/.claude/skills and ~/.codex/skills. Fix a bug in one and the other quietly kept the old behaviour. Everything on this page grew out of that one annoyance.

449+
commits since February 2026
22
tagged releases
2.1.8
current version

Where each claim comes from

Product numbers come from the source files that define them, not from marketing copy. Anything describing Agent Skills or MCP follows the official specification rather than a second-hand summary.

Claim on this pagePrimary source
31 built-in tools and their Skills directoriessrc-tauri/src/models/tool.rs
36 static security rules across four categoriessrc-tauri/src/services/risk/rules.rs
Symlink, junction, and copy fallback behavioursrc-tauri/src/services/linker.rs
What an Agent Skill is and how SKILL.md is loadedAnthropic — Agent Skills documentation
How to write a description that triggers reliablyAnthropic — Skill authoring best practices
What an MCP server is and how it differs from a SkillModel Context Protocol specification
Directory junctions need no elevation on WindowsMicrosoft Learn — mklink

What Skills Manager does not do

Knowing the limits matters more than the feature list when you are deciding whether to trust a tool with your setup.

The scan reads code, it does not run it

The security scan is static analysis over the files in a Skill folder. It matches patterns in text and cannot observe what a command actually does at runtime, so a novel or heavily obfuscated payload can pass a clean scan. Treat the result as a first filter, not a guarantee.

There is no web catalogue of Skills

The marketplace lives inside the desktop app. This site does not host browsable Skill pages, and there is no public API for searching Skills from a browser.

One tool gets a copy instead of a link

iFlow does not follow filesystem links, so Skills Manager keeps a tracked copy for it and records the source path. That copy does not update on its own after you edit the source — toggling the Skill off and on re-copies the folder. Every other supported tool sees the edit immediately.

Translation and LLM review send text to a provider

Both features are optional and off by default. When you start one, the Skill content is sent to the language model provider you configured with your own API key. Everything else — organizing, linking, scanning — never leaves your machine.

Page last reviewedReviewed against the shipping build and the linked sources above.

Download

Make every coding agent feel like one workspace

Download Skills Manager, connect your tools, and stop maintaining the same Skill in multiple folders.

v2.1.8
View all release files

Prefer to inspect the source first?

Skills Manager is MIT-licensed and developed in public.

Explore the repository
FAQ

Frequently asked questions

Download free