Claude
.claude/skills/
IntelliJ Platform 2024.2 → 2026.1 · Java 21
Manage Agent Skills like Maven dependencies. Without unzipping a single JAR.
SkillsJars Helper turns Maven-distributed
SKILL.md bundles into JetBrains IDE
first-class citizens. Discover, preview, and export to
9 agents' local directories — all without leaving your editor.
9
Agents supported
0
JARs unzipped
MIT
Open source
Built for 9 agents
One plugin, every coding agent.
Right-click any skill and pick a target. SkillsJars Helper writes
SKILL.md + assets to the agent's
well-known directory, plus a tiny .skillsjars-helper.json
manifest so future updates know exactly what changed.
Codex
.codex/skills/
Junie
.junie/skills/
Cursor
.cursor/skills/
Gemini
.gemini/skills/
Qoder
.qoder/skills/
Trae
.trae/skills/
CodeBuddy
.codebuddy/skills/
.agents
.agents/skills/
Why this plugin
Less plumbing, more skill-building.
Every feature is built to remove a friction you've already lived through: opening JARs by hand, copy-pasting SKILL.md, second-guessing whether the local copy is still in sync.
01 / Discover
Zero-extract preview.
Scans your Maven dependencies (regular and
skillsjars-maven-plugin) for
META-INF/skills/**/SKILL.md and renders them
directly. No unzip, no scratch directory, no manual
file diving.
02 / Export
9-agent hub.
Right-click → Extract to ▸ Claude / Codex / Cursor / … — or any custom directory.
03 / Trust
SHA-256 manifest.
Every export drops a .skillsjars-helper.json
with per-file hashes. Re-export later? It silently upgrades, asks before
clobbering local edits, and resolves same-name collisions deterministically.
04 / Visibility
Live install badges.
The tool window shows a brand badge next to every skill that's already installed to a given agent. State survives IDE restarts because it's rebuilt by re-scanning the manifest from disk — not held in memory.
05 / Extend
Open extension API.
Implement SkillSourceScanner in your own plugin
to feed Gradle, SBT, or any custom build system into the same coordination
layer. The api/ package is a stable contract.
06 / Privacy
Offline-first.
Reads your local Maven cache, writes your local agent directories. No telemetry, no remote calls, no network dependency.
Who it's for
Built for everyone wiring agents into a real workflow.
Replace the testimonials below with quotes from your team once you ship — for now, here are the four scenarios SkillsJars Helper was designed around.
"I just want one Claude skill in this repo, fast."
Drop a com.example:agent-skills dependency,
open the Agent Skills tool window, double-click to read the
SKILL.md, then right-click →
Extract to ▸ Claude. You're done in under a minute,
without ever touching jar -tf.
"Every team member needs the same skills, but each picks their agent."
Pin SkillsJar versions in pom.xml. Each developer
exports the bundle to their agent of choice. The
.skillsjars-helper.json manifest keeps everyone
aligned on which artifact / version is installed where.
"My company uses Bazel — I need to wire it into the same hub."
Implement SkillSourceScanner in a tiny companion
plugin and register it under the
skillSourceScanner extension point. Your scanner
produces SkillJarSource instances; the rest — parsing,
dedup, UI, export — is reused as-is.
"I switch between Cursor and Codex weekly. Don't make me copy files."
Same skill, two targets, two right-clicks. The plugin tracks both installations independently, shows badges for both, and on the next version bump silently upgrades whichever directories you've actually used.
FAQ
Which IDEs are supported?
IntelliJ IDEA Community / Ultimate 2024.2 — 2026.1 are the
official baseline. Other JetBrains IDEs built on the same platform
(PyCharm, GoLand, WebStorm, …) usually work within that build range,
but only IDEA is tested by CI.
I'm on Gradle, not Maven. Does it work?
Today the bundled scanner reads Maven dependencies and the
skillsjars-maven-plugin's embedded <dependencies>.
Gradle is on the roadmap, and the contract is already public:
implement SkillSourceScanner in your own plugin and you can
wire Gradle (or SBT, Bazel, your in-house tool) into the same UI today.
Does it phone home?
No telemetry, no analytics, no remote calls. The plugin only reads your
local Maven cache and writes to local agent directories you explicitly
pick from a context menu.
How is this different from copy-pasting SKILL.md by hand?
Three concrete differences. (1) You don't have to unzip a
JAR to look at it. (2) Each export drops a manifest with
sha256 per file, so the next export knows whether to silently
upgrade, ask before overwriting your local edits, or resolve a same-name
collision. (3) The tool window shows badges for every
target you've already installed to — across IDE restarts.
I edited the local SKILL.md. Will an upgrade overwrite me?
No. The manifest carries the original hashes, so a local edit is
detected and you get a yes/no confirmation dialog before anything is
written. If you intentionally want the upstream version back, just
accept; otherwise cancel and your edits are safe.
Two artifacts ship a skill with the same name. What happens?
The plugin detects a same-name collision from a different artifact and
offers three choices: overwrite, install with a
suffixed directory name, or cancel. The decision
is recorded in the manifest, so the next upgrade follows the same path.
Can I use the plugin's API from another plugin?
Yes. The
dev.dong4j.idea.skillsjars.helper.api package is the
public contract: SkillRegistry for snapshots,
SkillExportService for programmatic export,
SkillInstallationListener for events, plus the
skillSourceScanner extension point. Breaking changes get
called out in the changelog.
Is it open source? What license?
Yes — MIT, sources on
GitHub.
Issues, PRs and scanner integrations are welcome.
Get started in 30 seconds.
Install from JetBrains Marketplace, open any project that already has a SkillsJar dependency, and the Agent Skills tool window appears on the right. That's the whole onboarding.