What problem does it solve? Connecting local package managers (npm, pip, uv, maven, gradle, go, docker, helm, and others) to JFrog Artifactory requires manual config edits and repo selection, which is error-prone and inconsistent across projects. This Skill automates the binding workflow using jf setup and persists the decision so later sessions re-apply it automatically. ## Core Features & Use Cases - Automated package-manager binding: Detects which package managers a workspace uses from manifests (package.json, uv.lock, pom.xml, go.mod, Dockerfile, and more), then runs jf setup <pm> --server-id <SID> --repo <repoKey> for each. - Resolver-driven repo selection: Reads the session hook's resolved repo table, workspace binding, or global cache instead of guessing repositories, and asks the user verbatim when resolution fails. - Persistent workspace binding: Merges each successful setup into .jfrog/local/package-resolution.json via a lock-safe shell script, never storing credentials. - Use Case: A developer opens a Python project with uv.lock and no Artifactory config; the Skill detects uv, applies the resolved PyPI repo key, runs jf setup uv, and records the binding so the next session starts ready. ## Quick Start Set up my package managers to resolve through JFrog Artifactory and persist the workspace binding.
