jfrog-init

/jfrog-init — verify and guide JFrog plugin readiness

First output must be a tool call, not text. No "I'll start..." preamble.

Walks a fixed, ordered checklist and stops at the first red result, guiding the user through the matching fix before re-checking. Every detector in scripts/ is idempotent, read-only, JSON-emitting, and implemented in Node (.mjs), so the same detector runs unmodified on macOS, Linux, and Windows. Step 3's web-login uses this skill's own local .mjs scripts, same as every other step. The one interactive fix step that isn't a Node script at all is Step 1's Node install itself — a missing Node can't run a .mjs installer, so that one step branches on OS or shell directly.

Approval model — every user-approval point is detailed in its own Step below (exact wording, AskUserQuestion payloads, forbidden phrases); this is just the map:

• node — AskUserQuestion Yes/No before auto-installing (Step 1).
• jf (JFrog CLI) — AskUserQuestion Yes/No before auto-installing (Step 2).
• jf config — AskUserQuestion picker (web login, in-session, vs. access token, which never enters this conversation) (Step 3/4).
• Project selection — the user answers with a project name or key; an AskUserQuestion picker offers the first two enumerated projects plus "Other" (Step 6).
• Everything else in the walk is read-only, except Step 5's placeholder substitution (writes the plugin's mcp.json, unattended by design — no AskUserQuestion, see references/script-invocation.md), Step 8's ~/.netrc write (also unattended, no AskUserQuestion — see references/marketplace-setup.md), and the Final summary's state write below.

Step 1's nvm install and jfrog-install-jf-cli.mjs, Step 3's web-login scripts, Step 8's jfrog-add-claude-marketplace.mjs call, and the Final summary's jfrog-state-file.mjs set call are deliberately not in allowed-tools and will raise the harness's own approval prompt — intended, not a misconfiguration; see references/script-invocation.md.

${CLAUDE_SKILL_DIR} below is this file's own directory. Claude Code substitutes it automatically, identically, in both this text and the allowed-tools Bash rules above — write it literally rather than resolving it yourself, so the two stay byte-for-byte consistent regardless of install depth (see references/script-invocation.md). On a harness that doesn't perform this substitution (e.g. Cursor or Codex, neither of which consults allowed-tools for approval — every command below still raises its own prompt there), replace it with the real absolute path of this file's directory yourself, same as before.