JFrog integration for Claude Code: artifact management, security scanning, and supply-chain best practices.
This repository is the plugin: manifest at .claude-plugin/plugin.json, skills under skills/.
| Component | Path | Description |
|---|---|---|
| Manifest | .claude-plugin/plugin.json |
Plugin id jfrog, version, metadata. |
| Skills | skills/ |
skills/<name>/SKILL.md, invoked as /jfrog:<name> when the plugin is loaded. |
| MCP Gateway hook | hooks/hooks.json, scripts/inject-instructions.mjs, templates/jfrog-mcp-management.md |
A SessionStart hook that injects MCP-management instructions into Claude's context so MCP servers can only be added/removed/listed through the JFrog MCP Gateway (@jfrog/mcp-gateway). |
Skills are vendored from jfrog/jfrog-skills; the pinned release and commit are in skills/VENDOR.md.
- JFrog Platform access (Cloud or self-hosted).
- JFrog CLI (
jf) is used by several skills for authentication and REST API operations. It can be installed automatically if missing, or manually via Get JFrog CLI (installers and downloads) or the Install JFrog CLI documentation for full steps and troubleshooting.
From a clone of this repository (repository root is the plugin root):
claude --plugin-dir /path/to/claude-pluginAfter Claude Code starts, use /help to confirm skills under the jfrog namespace (for example /jfrog:<skill-name>). Run /reload-plugins after you change plugin files.
Plugins can be installed from catalogs described in Discover and install plugins once this repo is listed (for example in the official directory after submission).
Authentication details (for example browser login with jf) are described in individual skills where they apply.