jfrog-reference-architecture

Plans JFrog Platform topology, sizing, and deployment using live reference architecture documentation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the right JFrog Platform topology, sizing template, and deployment pattern requires up-to-date official guidance, and stale or memorized sizing numbers lead to under-provisioned Artifactory or Xray installations. ## Core Features & Use Cases - Sizing Recommendations: Maps peak RPM and concurrent connections to official t-shirt sizing templates (small through 2xlarge) for Artifactory and Xray, including AWS, Azure, and GCP guidance. - Topology & Use-Case Planning: Guides SaaS vs self-managed, single vs multi-site, active-active/active-passive, DR, air-gapped, and CI/CD separation decisions with cited official URLs. - Deployment Guidance: Recommends Kubernetes deployment via the jfrog-platform Helm chart with production considerations like external PostgreSQL and HA storage. - Use Case: A platform engineer asks how to size Artifactory for 5,000 peak RPM in production on EKS; the skill fetches the live reference architecture, recommends a template, and provides the matching Helm sizing values file. ## Quick Start Ask the agent to recommend a JFrog Platform sizing and deployment topology for your expected workload and hosting model.

Frequently Asked Questions about jfrog-reference-architecture

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

FAQPage Schema
How do I size Artifactory for production workloads?▼

Artifactory sizing uses official t-shirt templates from small to 2xlarge based on peak requests per minute and concurrent connections. The skill fetches the live sizing tables from jfrog.com/reference-architecture and recommends a template, noting that small is not intended for production.

Should I choose JFrog SaaS or self-managed deployment?▼

The choice depends on hosting preferences, compliance needs, and features like air-gapped support, which is self-managed only. The skill fetches the official SaaS value proposition and self-managed use cases to compare both options with cited sources.

What Helm chart should I use to deploy JFrog Platform on Kubernetes?▼

The recommended approach is the jfrog-platform Helm chart, even when deploying only Artifactory, by enabling Artifactory and disabling other products in values. Production deployments should use an external managed PostgreSQL and sizing values files like sizing/platform-<template>.yaml.

Does this skill require a configured JFrog instance or jf CLI?▼

No, planning-only questions require no jf CLI or configured JFrog instance. It only needs outbound HTTPS access to fetch live documentation from jfrog.com, and it requests full_network permission when fetches are blocked.

Why does the skill fetch documentation instead of answering from memory?▼

Sizing numbers, template names, and deployment guidance change over time, so every factual claim must come from a WebFetch in the current session. If the fetch fails, the skill retries or follows a fallback ladder rather than guessing from training data.

When should I not use the JFrog reference architecture skill?▼

Do not use it for artifact search or download, repository or permission administration, CVE lookups, live jf CLI operations, or package curation. Those tasks belong to the jfrog base skill or jfrog-package-curation skill instead.