jfrog-reference-architecture
Guides JFrog Platform topology, sizing (RPM, t-shirt templates), deployment, multi-site use cases, SaaS vs self-managed, HA, air-gapped, and disaster recovery using the official Reference Architecture site as the sole source of facts. Use this skill when the user asks how to size Artifactory or Xray, which deployment pattern to choose, single vs multi site, active-active, active-passive, CI/CD separation, Helm/Kubernetes install planning, or reference architecture (live WebFetch from jfrog.com/reference-architecture). Do NOT use for artifact search or download, repository or permission admin, CVE or vulnerability lookups, live jf CLI operations against their instance, or package curation — use the jfrog base skill or jfrog-package-curation instead.
Install
With your agent
Install OMGSkills skill "jfrog/claude-plugin:skills/jfrog-reference-architecture" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/jfrog/claude-plugin /tmp/claude-plugin && ln -s /tmp/claude-plugin/skills/jfrog-reference-architecture ~/.claude/skills/jfrog-reference-architectureFrom README
JFrog Reference Architecture Planning skill for topology, sizing, and deployment. Answers must come from live fetches of the JFrog Platform Reference Architecture — not from training data or duplicated tables in this repo. Prerequisites Read ../jfrog/SKILL.md for JFrog Platform concepts, product vocabulary, and routing to other workflows. No jf CLI required for planning-only questions (no live instance needed). Source of truth | Allowed in this skill | Not allowed | |-----------------------|-------------| | Fetch procedures, workflows, output templates | Sizing RPM tables, use-case narratives, deployment checklists copied from the site | | Helm chart preference (jfrog-platform on Kubernetes) | Hardcoded slug lists or criteria | Every factual claim (numbers, template names, limitations, infrastructure guidance) must come from a WebFetch in the current session. If fetch fails, retry or ask the user to open the URL — do not guess from memory.