jfrog-init

Verifies and configures JFrog CLI, MCP server, project, and AI Catalog readiness.

1|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/jfrog/jetbrains-plugin --skill jfrog-init-jfrog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jfrog-init
Source: https://github.com/jfrog/jetbrains-plugin/tree/main/.junie/skills/jfrog-init
Command: npx skills add https://github.com/jfrog/jetbrains-plugin --skill jfrog-init-jfrog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up the JFrog plugin involves many prerequisites — Node.js, the JFrog CLI, server credentials, MCP configuration, project selection, and AI Catalog entitlement — and a failure in any one of them leaves the environment broken with no clear diagnosis. This Skill walks an ordered checklist of detectors, stops at the first failing check, and guides the user through the exact fix before continuing. ## Core Features & Use Cases - Ordered readiness checklist: Runs eight detector steps (Node.js ≥ 18, jf CLI install, server connection, credential validity, MCP plugin entry, project resolution, AI Catalog entitlement, Claude marketplace registration) and stops at the first non-passing result. - Guided remediation: Each failure branch maps to an exact fix — approval-gated Node or jf installation, web-login vs. access-token authentication, and interactive server/project pickers. - Cross-harness support: Detects the host harness (Claude Code, OpenCode, Kiro, Junie, VS Code, Devin) and adapts MCP config paths and prompt mechanisms accordingly. - Use Case: After installing the JFrog plugin for the first time, run the initialization walk to install the JFrog CLI, connect it to your JFrog Platform via browser login, pick a project, and confirm the MCP server and AI Catalog are reachable — all in one guided pass. ## Quick Start Ask the agent to run /jfrog-init to verify and complete your JFrog plugin setup.

Frequently Asked Questions about jfrog-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the JFrog plugin after first install?▼

Run the /jfrog-init walk, which checks Node.js, installs the JFrog CLI if missing, connects it to your JFrog Platform, and verifies the MCP server, project, and AI Catalog. It stops at the first failing check and guides you through the fix.

How do I connect the JFrog CLI to my JFrog Platform server?▼

The walk offers two options: web login, which opens a browser page with a verification code and saves credentials automatically, or an access token command you run yourself in your own terminal. The token never enters the chat conversation.

What are the requirements for running jfrog-init?▼

You need Node.js 18 or newer with npx on PATH, plus network access to your JFrog Platform instance. The walk installs the JFrog CLI itself if it is missing, broken, or below the required minimum version.

Does jfrog-init work with agent harnesses other than Claude Code?▼

Yes, it detects the current harness and adapts accordingly, supporting OpenCode, Kiro, Kiro CLI, Junie, VS Code, and Devin. MCP configuration is written to each tool's own config path, and Step 8's marketplace registration runs only on Claude Code.

Why does the AI Catalog check report not entitled?▼

A 403 from the authenticated catalog probe means the catalog is reachable but your user lacks permission. Ask your JFrog admin for the AI Catalog Read role; this gap is non-blocking and does not affect the core CLI setup.

What happens if a setup check fails during the walk?▼

The walk stops at the first non-passing check and presents the matching fix, such as an install approval prompt or a re-authentication command. Non-blocking gaps like an unconfigured MCP entry or missing catalog entitlement are reported in the final summary instead.