Terminal
Terminal/Skill
Lets your agent browse, install, update and publish agent skills and plugins from the JFrog AI Catalog using the JFrog CLI.
By JFrog
Works with
npx skills add jfrog/jfrog-skills --skill jfrog-ai-catalogDiscover, install, and manage agent skills and agent plugins from the JFrog AI
Catalog (Artifactory skills/plugins repositories), and publish your own back to
it, all through the JFrog CLI (jf skills, jf agent plugins) and the JFrog
Agent Guard.
Pick the row matching the user's intent and read that reference file.
| Intent | Read |
|---|---|
| "What skills are available?" / browse the catalog / list versions / search by name | references/discovering-skills.md |
| Install a skill with an explicitly resolved version and repo, update a skill, or handle a blocked download | references/installing-skills.md |
| "What's installed?" / remove an installed skill | references/managing-installed-skills.md |
| Publish / upload / release a skill to the catalog | references/publishing-skills.md |
| "What plugins are available?" / browse the plugin catalog / list plugin versions / search plugins | references/discovering-plugins.md |
| Install or update a plugin (latest or a pinned version) | references/installing-plugins.md |
| "What plugins are installed?" / remove an installed plugin | references/managing-installed-plugins.md |
| Publish / upload / release a plugin to the catalog | references/publishing-plugins.md |
Read the base jfrog skill first. ../jfrog/SKILL.md
owns the shared guards this skill depends on, so this skill does not repeat
them — follow them there:
jf
is installed before the first jf call, and install it if missing.<SID> once and reuse it, pass --server-id <SID>
after the subcommand on every jf call, and use one server per request.
Resolve it now, before any jf call:
jf config show 2>/dev/null \
| awk '/^Server ID:/{id=$NF} /^Default:[[:space:]]*true/{print id; exit}'
# stdout: the default server-id; if empty, stop and ask which server to use
jf failure, stop and never switch servers.One addition specific to this skill: never cat or parse
~/.jfrog/jfrog-cli.conf.v6 (it can hold access tokens); list servers only
with jf config show, which redacts secrets.
Agent Guard registry. Catalog discovery and repo provisioning run through
npx --yes @jfrog/agent-guard. <REGISTRY_URL> is the npm registry that
provides the @jfrog/agent-guard package itself: use JFROG_AGENT_GUARD_REPO
if set, otherwise
https://releases.jfrog.io/artifactory/api/npm/coding-agents-npm/. Pass the
same <SID> to Agent Guard as --server "<SID>" so it targets the same server
as your jf calls. Agent Guard also reads JFROG_URL / JF_URL directly when
set, so make sure the <SID> you resolved points at that same host.
Resolve the project (<PROJECT>) only when needed.
It is required for --list-skills, --list-skill-versions,
--provision-skills-repository, --list-agent-plugins,
--list-agent-plugin-versions, and --provision-agent-plugins-repository.
Resolve it with this priority:
~/.jfrog/setup.json (if present) and read .servers["<SID>"].currentActiveProject.$JF_PROJECT.PROJECT=$(jq -r --arg sid "<SID>" '.servers[$sid].currentActiveProject // empty' \
~/.jfrog/setup.json 2>/dev/null)
[ -z "$PROJECT" ] && PROJECT="${JF_PROJECT:-}"
There is no non-admin way to look up or validate project keys (the
/access/api/v1/projects list endpoint needs admin), so you cannot
silently correct a display name to a key. If the value looks like a
display name (spaces, mixed case) rather than a short slug, ask the
user to confirm the project key specifically. Never assume
default, never invent one. Install, update, remove, and publishing to
an explicit --repo are keyed by skill/plugin name and/or repo,
not a project.
Bundle manifests differ by type. Skill bundles require SKILL.md
in the bundle root; plugin bundles require plugin.json. Validate the
correct file before installing or publishing.
flowchart TD
A[User request] --> B{jf CLI installed?}
B -->|No| C[Ask user to install jf CLI, then continue]
B -->|Yes| D{Intent}
C --> D
D -->|List all skills / versions| E[npx @jfrog/agent-guard --list-skills --allowed-only]
D -->|Install / update skill| F[Resolve slug + version, then jf skills install/update]
D -->|List installed skills / remove| G[jf skills list / rm -rf install dir]
D -->|Publish skill| H[Resolve/provision repo, validate bundle, jf skills publish]
D -->|List all plugins / versions| I[npx @jfrog/agent-guard --list-agent-plugins]
D -->|Install / update plugin| J[Resolve slug + version, then jf agent plugins install/update]
D -->|List installed plugins / remove| K[jf agent plugins list / rm -rf install dir]
D -->|Publish plugin| L[Resolve/provision repo, validate bundle, jf agent plugins publish]
Catalog-specific rules only. The shared jf guards — single server per request,
stop-on-error, and cautious mutation — live in the base
jfrog skill; follow those too. Flow-specific rules live in
the reference files above.
npx/Agent Guard commands, --registry, flags, or cursors. Run follow-ups
yourself. Discuss catalog filtering only when the user asks about missing or
blocked results; follow the refusal in discovering-skills.md.discovering-skills.md. Never weaken that listing path,
including for audit, blocked-content, or named-repository requests. Each
locations[] entry from --list-skill-versions also carries its own
allowStatus, since a repo's governance status is a per-repo fact, never a
per-version one (MLAI-1309) — see discovering-skills.md and
installing-skills.md.--skip-scan flag) when
performing any jf agent plugins operation.