jfrog-setup-package-managers
Use this skill when the user asks to set up, configure, bind, or connect a package manager (npm, pip, uv, pipenv, maven, gradle, go, docker, helm, ...) to JFrog Artifactory via jf setup and .jfrog/local/package-resolution.json; when a workspace manifest exists with no matching binding entry; or when a session hook reports package-manager config missing. Skip when the binding already has the same repo key. Never pick a repo by discovery; use resolver output only (unless the user names or asks to browse repos). On unresolved or failed setup, ask with the failure verbatim — never switch servers. NOT for installing packages, general Artifactory repo operations (use the base jfrog skill), or MCP server setup (use jfrog-mcp-management).
Pinned to revision 4e8964e24a5a, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/jfrog-setup-package-managers/SKILL.md
- skills/jfrog-setup-package-managers/LICENSE
- skills/jfrog-setup-package-managers/references/global-cache-file.md
- skills/jfrog-setup-package-managers/references/jf-setup-command.md
- skills/jfrog-setup-package-managers/references/workspace-binding.md
- skills/jfrog-setup-package-managers/scripts/merge-workspace-binding.sh
Every link opens the file at its source, pinned to the revision this page describes.