jfrog
- 45 skills
- 0 followers
- 7 hours ago last updated
- ▌ Release Version Bump · jfrog bundleEnd-to-end release bump for vault-plugin-secrets-artifactory: update Go version and Go module dependencies, run local build/tests against the existing Artifactory image, then create a PR only after asking permission. Use when the user asks to bump Go, refresh go.mod dependencies, prepare a plugin release, or ship a version bump PR. Do not bump the Artifactory image version. Ask the user only twice: before starting Artifactory/integration tests, and before commit/push/PR.
- ▌ Dap · jfrog bundleUse when the user says "write a blueprint", "fix my blueprint", "create a deployment", "what node type", "how do I deploy", "blueprint won't validate", "lint this", "review this yaml", "add an input", "which plugin", "help me with TOSCA", "add update support", "support deployment update", "support drift", "add check_drift", "add reinstall", "make this updatable", "day 2", "babysit", "monitor", "did it pass", "did it fail", "last run", "any failures", "check status", "how to", "tutorial", "guide", "help me get started", "walk me through", "what are plugins", "how do I delete", "how do I create secret", or any request to write, review, debug, test, or get step-by-step help with blueprint YAML or DAP workflows. Also known as "Blueprint Assist" — triggers on "blueprint assist", "blueprint-assist", or "Blueprint Assist".
- ▌ Dap Scripts · jfrog bundleUse when writing or debugging Python scripts for DAP blueprints — from dell import ctx, ctx_parameters, runtime_properties, NonRecoverableError, RecoverableError, REST client. Triggers — blueprint script, dell ctx.
- ▌ Dap Deployment Update · jfrog bundleUse when updating a deployment — blueprint version bumps, input changes, skip_install/uninstall/reinstall, reinstall_list, force_reinstall, preview mode, drift check. Triggers — deployment update, node reinstall.
- ▌ Dap Service Composition · jfrog bundleUse when composing services — ServiceComponent sub-deployments, SharedResource, chaining blueprints, get_environment_capability. Triggers — service component, sub-deployment, dell.nodes.ServiceComponent, or requests to chain deployments.
- ▌ Belt · jfrogOperate the belt CLI to evaluate headless coding agents (Claude Code, Cursor, Codex, Gemini, and others) end to end. Use when the user asks to write or run eval scenarios, compare agents, score outputs with rules or LLM judges, register a new agent adapter, interpret reports or benchmark cards, or set up evals in CI. Also use when the user mentions agent-belt, scenario JSON, BELT_ env vars, llm_scorer_instruction, llm_scorer_evidence_files, TurnExpectation, or benchmark cards.
- ▌ Bookstore Assistant · jfrogCustomer support and order operations for the Folio bookstore. Use whenever the user asks about a book, an order, a refund, a return, store credit, or anything else customer-facing. All canonical data lives behind the `folio` MCP server - never invent prices, stock counts, customer details, or order history.
- ▌ Orders Helper · jfrogLook up customer orders through the orders_db MCP server. Use whenever the user asks about an order, a tracking number, a delivery, or a customer's purchase history.
- ▌ Inventory Audit · jfrogIdentify Folio books with low on-hand stock so the operator can replenish before the title goes out of stock. Use whenever the user asks about books running low, low stock, restock list, what's almost gone, stock audit, or which titles need reordering.
- ▌ Processing Watch · jfrogIdentify and surface every order currently in the `processing` state, so the operator can chase down stalled fulfilment. Use whenever the user asks about stalled orders, processing backlog, things stuck in processing, or orders that haven't shipped yet.
- ▌ Jfrog AI Catalog Skills · jfrog bundleDiscover, install, manage, and publish agent skills hosted in the JFrog AI Catalog (Artifactory skills repositories) using the JFrog CLI (`jf skills`) and the JFrog Agent Guard. Lists and searches available skills (catalog-wide or scoped to a project), shows a skill's versions and which repos host it, installs the latest or a pinned version, verifies the install, lists installed skills, updates and removes them, and publishes (uploads) a local skill bundle and releases new versions. Use when the user asks what skills are available or installed, to search/browse the catalog, to install/update/uninstall a skill, to see a skill's versions, or to publish/upload/release a skill to JFrog / Artifactory / the AI Catalog.
- ▌ Jfrog Package Safety And Download · jfrogCheck JFrog Public Catalog and stored packages for a version, interpret catalog security signals, and download through Artifactory (JFrog Platform locations, remote cache, curation-aware package managers, or repo proxy). Use when the user asks whether a package is safe, allowed, curated, or wants to download npm, Maven, PyPI, Go, or similar packages via JFrog. Do NOT use for pure CVE or vulnerability lookups (e.g. "details on CVE-2021-23337") — those are handled by the jfrog skill's Public security domain queries without this workflow.
- ▌ Jfrog · jfrog bundleInteract with the JFrog Platform via the JFrog CLI, JFrog MCP server and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name. Do NOT use this skill to install, add, remove, list, or manage MCP servers.
- ▌ Jfrog Init · jfrog bundleSet up and verify the JFrog plugin. Run on first install, to complete initial configuration, or to diagnose a broken setup.
- ▌ Jfrog AI Catalog · jfrog bundleDiscover, search, install, update, remove, and publish agent skills and plugins hosted in the JFrog AI Catalog (Artifactory) via the JFrog CLI (`jf skills`, `jf agent plugins`) and JFrog Agent Guard. Use whenever the user asks what skills or plugins are available or installed, wants to browse/search the catalog, see versions, install/update/uninstall/delete a skill or plugin, or publish/upload/release one to JFrog / Artifactory / the AI Catalog.
- ▌ Jfrog MCP Management · jfrog bundleUse to install, list, or remove MCP servers, and to discover which MCPs the user can install — including questions about available, approved, or allowed MCPs for a project. That governed catalog is the authoritative answer; do not answer those questions from local IDE/settings allowlists alone. Use whenever the user wants to add/enable/install/list/remove/uninstall/configure an MCP or write/update the agent's MCP config — even if they name a package like `@scope/pkg` and even without saying "MCP" or "JFrog". Never install an MCP any other way. All of this goes through the JFrog Agent Guard (npx @jfrog/agent-guard).
- ▌ Jfrog Package Curation · jfrog bundleCheck/download a package (npm, Maven, PyPI, Go...) via JFrog — safe, allowed, curated? Or: package op fails/blocked (ETARGET, 403, blocked by curation policy, missing version, waiver) — root cause it. Checks the JFrog Public Catalog and stored packages for a version, interprets catalog security signals, and downloads through Artifactory (JFrog Platform locations, remote cache, curation-aware package managers, or repo proxy). Do NOT use for pure CVE or vulnerability lookups (e.g. "details on CVE-2021-23337") — those are handled by the jfrog skill's Public security domain queries without this workflow. Do NOT use for installing, listing, or approving MCP servers/tools (even when named like a package, e.g. `@scope/pkg`) — that's `jfrog-mcp-management`.
- ▌ Jfrog Reference Architecture · jfrog bundleGuides 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.
- ▌ Jfrog Setup Package Managers · jfrog bundleUse this skill when the user asks to set up, configure, bind, or connect a package manager (npm, pip, uv, pipenv, maven, gradle, go, docker, helm, ...) to JFrog Artifactory via `jf setup` and `.jfrog/local/package-resolution.json`; when a workspace manifest exists with no matching binding entry; or when a session hook reports package-manager config missing. Skip when the binding already has the same repo key. Never pick a repo by discovery; use resolver output only (unless the user names or asks to browse repos). On unresolved or failed setup, ask with the failure verbatim — never switch servers. NOT for installing packages, general Artifactory repo operations (use the base jfrog skill), or MCP server setup (use jfrog-mcp-management).
- ▌ Jfrog CLI · jfrog bundleUse when working with the JFrog CLI (jf command) -- uploading/downloading artifacts, running security scans, managing builds, creating release bundles, configuring the JFrog Platform from the command line, or invoking platform REST APIs via jf api. Triggers on mentions of jf command, jfrog cli, jf api, jf rt, jf audit, jf scan, jf docker, file spec, or jf config.
- ▌ Jfrog Access · jfrog bundleUse when working with JFrog Access -- managing tokens, users, groups, permissions, projects, or authentication. Triggers on mentions of access token, permission, user, group, project, RBAC, authentication, or authorization.
- ▌ Jfrog Runtime · jfrog bundleUse when working with JFrog Runtime -- monitoring runtime clusters, checking node health, or listing running container images with vulnerability info. Triggers on mentions of runtime, runtime cluster, running images, runtime sensor, runtime controller, container monitoring, or node health.
- ▌ Jfrog Workers · jfrog bundleUse when working with JFrog Workers -- creating serverless TypeScript functions, hooking into platform events, or building HTTP-triggered automations. Triggers on mentions of worker, serverless, event hook, TypeScript worker, BEFORE_DOWNLOAD, AFTER_CREATE, or custom platform logic.
- ▌ Jfrog Apptrust · jfrog bundleUse when working with JFrog AppTrust -- managing applications, creating and promoting application versions, releasing to production, rolling back, or binding packages. Triggers on mentions of apptrust, application entity, application version, trusted release, application risk, promote version, release version, rollback, or package binding.
- ▌ Jfrog Curation · jfrog bundleUse when working with JFrog Curation -- managing package curation policies, auditing blocked packages, configuring curated repositories, or managing waivers. Triggers on mentions of curation, package firewall, blocked package, curated repository, waiver, or supply chain policy.
- ▌ Jfrog Onemodel · jfrog bundleQuery any entity on the JFrog Platform using OneModel GraphQL — applications, release bundles, artifacts, builds, evidence, packages, and catalog data through a single unified API. Use this skill when the user wants to query, search, or list anything from the JFrog Platform using GraphQL, including applications, application versions, release bundles, artifacts, evidence, packages, catalog information, or build traceability. Also use when the user asks "what do I have" or "list my..." for JFrog Platform entities. Triggers on mentions of "onemodel", "graphql", "release bundle info", "evidence query", "search evidence", "release bundle artifacts", "build traceability", "graphql query jfrog", "run a graphql query against jfrog", "list applications", "my applications", "search packages", or "catalog info".
- ▌ Jfrog Patterns · jfrog bundleUse when helping users set up JFrog Platform architectures, best practices, or workflows. Covers 22 recommended patterns across CI integration, repositories, security, release lifecycle, multi-site, and AppTrust. Also covers 5 user journeys (Modernize Delivery, Secure SDLC, Accelerate Productivity, Enterprise Complexity, Trusted AI). Triggers on mentions of pattern, best practice, architecture, get started, CI integration, multi-site, release lifecycle, AppTrust, or how to set up JFrog.
- ▌ Jfrog Security Xray · jfrog bundleUse when working with JFrog Security/Xray -- scanning for vulnerabilities, managing policies/watches/violations, generating SBOMs, configuring advanced security (SAST, secrets detection, contextual analysis), or monitoring runtime. Triggers on mentions of xray, vulnerability, CVE, scan, policy, watch, violation, SBOM, SAST, secrets detection, contextual analysis, IaC scanning, or runtime security.
- ▌ Jfrog Artifactory · jfrog bundleUse when working with JFrog Artifactory -- managing repositories, deploying/downloading artifacts, querying with AQL, configuring builds, replication, or federation. Triggers on mentions of artifactory, repository, artifact, deploy, docker registry, build info, AQL, replication, or federation.
- ▌ Jfrog Distribution · jfrog bundleUse when working with JFrog Distribution and Release Lifecycle Management -- creating release bundles, promoting through environments, distributing to edge nodes, or managing evidence. Triggers on mentions of distribution, release bundle, promote, environment, edge node, release lifecycle, or evidence.
- ▌ Jfrog Oidc Setup · jfrogConfigure OpenID Connect (OIDC) integration between GitHub Actions and JFrog Platform for secretless CI authentication. Checks subscription compatibility, creates OIDC providers, and sets up identity mappings per repository. Use when setting up OIDC for GitHub Actions workflows.
- ▌ Jfrog Create Repos · jfrog bundleCreate Artifactory repositories (local, remote, virtual) for npm, Maven, PyPI, Go, Docker, and Helm ecosystems within a JFrog project. Supports ecosystem-based auto-generation, explicit custom repository definitions, or a smart merge of both. Use when the user needs to set up Artifactory repos, create package repositories, or configure artifact storage for a project.
- ▌ Jfrog Mission Control · jfrog bundleUse when working with JFrog Mission Control -- managing JFrog Platform Deployments (JPDs), checking deployment health, auditing licenses, or listing proxies. Triggers on mentions of mission control, JPD, platform deployment, license, proxy, or deployment health.
- ▌ Jfrog Delete Project · jfrogDelete a JFrog project and all its repositories. Use when the user wants to remove, delete, or clean up a JFrog project, or mentions deleting JFrog resources.
- ▌ Jfrog Manage Members · jfrogAdd users and groups to a JFrog Platform project with role assignments. Use when the user wants to manage project membership, add developers to a JFrog project, or assign roles to teams.
- ▌ Jfrog Provision Project · jfrog bundleProvision a new project on the JFrog Platform via REST API. Use when the user wants to create a JFrog project, set up a new project in Artifactory, or as part of onboarding a GitHub repo to JFrog.
- ▌ Detect Existing Patterns · jfrogDetect existing project and repository naming patterns on the JFrog Platform before onboarding. Queries all projects and repos, analyzes naming conventions, and presents the user with a choice between following detected patterns or using the standard naming rules. Use before creating new projects or repositories.
- ▌ Jfrog Project Onboarding · jfrog bundleOrchestrate end-to-end JFrog Platform onboarding for GitHub projects. Provisions JFrog projects, creates Artifactory repositories, adds members, configures OIDC, configures package managers, and updates CI workflows. Use when the user wants to onboard, connect, or integrate GitHub repos with JFrog, or when processing an onboarding manifest.
- ▌ Jfrog Reconcile Manifest · jfrogReconcile JFrog Platform state with a desired-state manifest. Reads current configuration, computes a diff, presents changes for approval, and applies only the delta. Use when the user wants to update, sync, or reconcile JFrog with manifest changes.
- ▌ Jfrog System Config Repo · jfrogPersist and retrieve onboarding manifests via Artifactory or Git. Supports configurable project/repo for Artifactory and clone/commit/push for Git. Routes by state.destination in the manifest. Use when persisting or retrieving onboarding manifests.
- ▌ Jfrog Create Users Groups · jfrogCreate users and groups on the JFrog Platform via REST API. Use when onboarding discovers missing users or groups, or when the user wants to create JFrog platform users/groups. Supports assigning users to groups during creation and setting a default password.
- ▌ Jfrog Curation Onboarding · jfrogSet up JFrog Curation with protection policies on an existing JFrog Platform instance. Checks if Curation is enabled, collects a notification email, then creates security, license, and operational risk policies on remote repositories. The "Block Malicious" policy blocks downloads; all others run in dry-run (audit) mode. Use when the user wants to set up curation, onboard curation, enable curation protection, or block malicious packages.
- ▌ Apptrust Evidence Policies · jfrog bundleCreate JFrog project lifecycle policies that check for evidence existence on promotion or release events for applications with specific labels. Use when the user asks to create a policy, evidence policy, promotion policy, lifecycle policy, compliance check, or evidence validation for application promotions. Triggers on mentions of policy, evidence policy, promotion policy, lifecycle policy, compliance check, evidence validation, AppTrust promotion.
- ▌ Github Configure CI Workflows · jfrog bundleModify GitHub Actions workflows to resolve dependencies from JFrog Artifactory and upload build artifacts. Adds jfrog/setup-jfrog-cli action, replaces native build commands with JFrog CLI equivalents. Use when integrating CI/CD pipelines with JFrog or updating GitHub Actions for Artifactory.
- ▌ Github Configure Package Managers · jfrog bundleConfigure package manager settings in GitHub repositories to resolve dependencies from JFrog Artifactory. Handles npm (.npmrc), Maven (settings.xml), pip (pip.conf), Go (GOPROXY), Docker, and Helm. Use when setting up local developer dependency resolution through Artifactory.