How do I install the Jfrog Search Docker Image skill?

Run npx skillmds@latest add evindunn/jfrog-search-docker-image in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jfrog Search Docker Image safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jfrog Search Docker Image?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jfrog Search Docker Image free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jfrog Search Docker Image?

evindunn (@evindunn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jfrog Search Docker Image by evindunn

Name: Jfrog Search Docker Image
Author: evindunn

Jfrog Search Docker Image

Find available Docker image tags in JFrog Artifactory using the `jf` CLI, especially when a user asks to search Artifactory/JFrog for a Python, base, CI, Docker, or container image tag and choose a concrete repository image string.

evindunn 2c6acd2 3 files · 5.8 KB Updated Sep 17, 2026

File contents

JFrog Docker Image Search

Use this skill to verify image tags that actually exist in Artifactory before editing CI/CD image references.

Workflow

Confirm jf is installed and configured:
```
jf --version
jf c show
```
Prefer the Docker registry tag API over raw artifact glob searches. Docker repositories may not expose tag directories in a way that jf rt s can find reliably.
In Codex sandboxed sessions, Artifactory hostnames commonly fail DNS resolution until the command is rerun with escalated network access. If any jf command fails with lookup <host>: no such host, rerun the same JFrog query or helper command immediately with network escalation instead of retrying inside the sandbox.

For exact or narrow tag checks, prefer the bundled helper first so output stays small and unambiguous:

python ~/.codex/skills/jfrog-search-docker-image/scripts/filter_docker_tags.py \
  --repo public-docker-prod \
  --image library/python \
  --prefix 3.12 \
  --contains slim

List raw tags with jf rt curl when the helper is not enough or broader inspection is needed:
```
jf rt curl "/api/docker/<repo>/v2/<image-path>/tags/list"
```
Example for Python official images mirrored in Artifactory:
```
jf rt curl "/api/docker/public-docker-prod/v2/library/python/tags/list"
```

Report the exact usable image string:

<registry-host>/<repo>/<image-path>:<tag>

Notes

If jf fails with DNS or network errors in Codex, rerun the JFrog query/helper with escalated network access and continue from that result. Do not repeat non-network setup checks such as jf --version or jf c show.
If a broad tag-list response is large, use the helper script so only matching tags are shown.
Use library/python for official Python images in public-docker-prod; python alone may return NAME_UNKNOWN.
If a manifest check fails for a tag that appears in tags/list, trust tags/list for availability unless the user specifically asks to debug the manifest API path or headers.

---name: jfrog-search-docker-imagedescription: Find available Docker image tags in JFrog Artifactory using the `jf` CLI, especially when a user asks to search Artifactory/JFrog for a Python, base, CI, Docker, or container image tag and choose a concrete repository image string.---# JFrog Docker Image SearchUse this skill to verify image tags that actually exist in Artifactory before editing CI/CD image references.## Workflow1. Confirm `jf` is installed and configured: ```bash jf --version jf c show ```2. Prefer the Docker registry tag API over raw artifact glob searches. Docker repositories may not expose tag directories in a way that `jf rt s` can find reliably.3. In Codex sandboxed sessions, Artifactory hostnames commonly fail DNS resolution until the command is rerun with escalated network access. If any `jf` command fails with `lookup <host>: no such host`, rerun the same JFrog query or helper command immediately with network escalation instead of retrying inside the sandbox.4. For exact or narrow tag checks, prefer the bundled helper first so output stays small and unambiguous: ```bash python ~/.codex/skills/jfrog-search-docker-image/scripts/filter_docker_tags.py \ --repo public-docker-prod \ --image library/python \ --prefix 3.12 \ --contains slim ```5. List raw tags with `jf rt curl` when the helper is not enough or broader inspection is needed: ```bash jf rt curl "/api/docker/<repo>/v2/<image-path>/tags/list" ``` Example for Python official images mirrored in Artifactory: ```bash jf rt curl "/api/docker/public-docker-prod/v2/library/python/tags/list" ```6. Report the exact usable image string: ```text <registry-host>/<repo>/<image-path>:<tag> ```## Notes- If `jf` fails with DNS or network errors in Codex, rerun the JFrog query/helper with escalated network access and continue from that result. Do not repeat non-network setup checks such as `jf --version` or `jf c show`.- If a broad tag-list response is large, use the helper script so only matching tags are shown.- Use `library/python` for official Python images in `public-docker-prod`; `python` alone may return `NAME_UNKNOWN`.- If a manifest check fails for a tag that appears in `tags/list`, trust `tags/list` for availability unless the user specifically asks to debug the manifest API path or headers.

Frequently asked questions