JFrog Workers are the secure, modern path forward for customizing the JFrog Platform, and are the recommended replacement for user plugins. Built as event-driven functions that run in an isolated sandbox, Workers provide a standardized, testable way to automate your platform without compromising system stability. In contrast, plugins were often hard to test locally, tricky to scale, and vulnerable to breaking during upgrades.
To help you leap without rewriting everything from scratch, we built the migrate-groovy-plugin skill: an AI-assisted skill that automates the heavy lifting of your migration while keeping you in complete control.
Why Make the Switch?
Workers give you the same lifecycle hooks you rely on, but in a much more resilient package.
|
Legacy Groovy Plugins
|
Modern JFrog Workers
|
Environment
|
Runs directly inside the JVM
|
Runs in an isolated, secure sandbox
|
Testing
|
Difficult to test locally
|
Standard npm test scaffold per worker
|
Access
|
Broad internal system access
|
Governed by the Platform REST API
|
Deployment
|
Manual file drops
|
Automated via CLI or CI pipelines
|
Meet Your Migration Assistant
You don’t have to manually translate hundreds of lines of Groovy into TypeScript. By pointing the migrate-groovy-plugin skill at your existing .groovy files, the tool does the boilerplate work for you:
-
Analyzes and Maps: It reads your Groovy source and maps every hook closure to its equivalent JFrog Worker event (e.g., mapping storage.beforeCreate to BEFORE_CREATE).
-
Scaffolds the Code: It automatically generates an isolated, ready-to-test TypeScript worker project for each hook.
-
Translates APIs: It converts legacy papi calls into verified JFrog REST API calls.
-
Generates an Audit Trail: It creates a comprehensive MIGRATION_REPORT.md detailing exactly what was converted and what needs a human touch.
Best of all, you keep control. Generated workers are deployed in a disabled state (enabled: false) by default. Nothing goes live until your team has reviewed the code, run the tests, and given the green light.
What to Expect
Simple plugins — like download gates, storage triggers, or scheduled jobs — often migrate quickly. The skill excels at converting standard hooks for downloads, builds, replication, and standard REST endpoints.
Because Workers are securely sandboxed, certain legacy patterns require a redesign. The migration skill won’t fail silently; it explicitly flags these areas for you:
Legacy Pattern
|
Why it requires redesign
|
Modern Alternative
|
Custom Auth (realms)
|
Workers don't handle authentication
|
Configure OIDC/SAML via JFrog Access
|
Filesystem I/O / Threads
|
The sandbox blocks host access
|
Use the REST API or context.state
|
Shared Static State
|
Workers run in isolation
|
Use artifact properties to pass state
|
Prerequisites
Before you run the skill (not required only to download it):
-
Claude Code and/or Cursor
-
JFrog CLI (jf) installed — see Get JFrog CLI
-
A configured JFrog server: jf c add
-
Working Workers support on that server (quick check: jf worker list-event)
-
curl and unzip on your machine (for skill install)
Note: Public distribution of this skill is a downloadable ZIP. Do not use jf skills / jf agent skills install for this package
The Migration Workflow
1. Install the Skill
Install version 0.2.0 into your agent’s global skills folder.
1.1. Download the skill ZIP
curl -fsSL -o /tmp/migrate-groovy-plugin-0.2.0.zip \
"https://releases.jfrog.io/artifactory/api/skills/jfrog-skills/api/v1/download?slug=migrate-groovy-plugin&version=0.2.0"
To pin a different version, change version=0.2.0 in the URL and match the /tmp/…zip filename.
1.2. Create the destination folder
Cursor (global):
mkdir -p ~/.cursor/skills/migrate-groovy-plugin
Claude Code (global):
mkdir -p ~/.claude/skills/migrate-groovy-plugin
1.3. Unzip into that folder
Cursor:
unzip -o /tmp/migrate-groovy-plugin-0.2.0.zip -d ~/.cursor/skills/migrate-groovy-plugin
Claude Code:
unzip -o /tmp/migrate-groovy-plugin-0.2.0.zip -d ~/.claude/skills/migrate-groovy-plugin
Install for both agents if you use both:
mkdir -p ~/.cursor/skills/migrate-groovy-plugin ~/.claude/skills/migrate-groovy-plugin
unzip -o /tmp/migrate-groovy-plugin-0.2.0.zip -d ~/.cursor/skills/migrate-groovy-plugin
unzip -o /tmp/migrate-groovy-plugin-0.2.0.zip -d ~/.claude/skills/migrate-groovy-plugin
1.4. Confirm the install
Cursor:
ls ~/.cursor/skills/migrate-groovy-plugin/SKILL.md
Claude Code:
ls ~/.claude/skills/migrate-groovy-plugin/SKILL.md
You should also see a references/ directory next to SKILL.md.
5. Clean up and start a new chat
rm /tmp/migrate-groovy-plugin-0.2.0.zip
Open a new Claude Code or Cursor chat so the skill is loaded.
2. Run the Skill
In a new Claude Code or Cursor chat, point the skill at your plugin file or directory:
/migrate-groovy-plugin /path/to/your-plugin.groovy
or:
Migrate this Groovy plugin to a worker: /path/to/your-plugin/
Optional flags:
The skill discovers hooks, scaffolds worker projects with jf worker init, migrates logic, and writes MIGRATION_REPORT.md.
3. Review the Report
Open the generated MIGRATION_REPORT.md. This is your roadmap. Search the generated code for TODO and WARN comments left by the skill so engineers can focus on edge cases and platform limits rather than boilerplate.
4. Test and Deploy
Every generated project includes a standard npm test setup. Run local tests, deploy to staging, and only then set enabled: true after review.
Ready to modernize your automation? Install the migrate-groovy-plugin skill with the steps above, configure the JFrog CLI, and start building faster, safer, and more resilient platform extensions.
Related Topics