skills.rest
jfrog
jfrogOFFICIAL
Explore all skills by this author →
WebsiteGitHub

jfrog-system-config-repo

Persist and retrieve onboarding manifests across Artifactory or Git backends.

5|1|Updated Mar 2, 2026
Search Tags:#git#versioning#onboarding#persistence#manifests#artifactory
One-click install
npx skills add https://github.com/jfrog/ai-agent-examples --skill jfrog-system-config-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jfrog-system-config-repo
Source: https://github.com/jfrog/ai-agent-examples/tree/main/onboarding-workflows/skills/jfrog-system-config-repo
Command: npx skills add https://github.com/jfrog/ai-agent-examples --skill jfrog-system-config-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist onboarding manifests by storing and retrieving configuration data across Artifactory or Git, enabling centralized audit trails and repeatable onboarding.

Core Features & Use Cases

  • Persist and retrieve onboarding manifests using two backends: Artifactory (default) and Git.
  • Route operations based on state.destination in the manifest to support Artifactory storage and Git-based versioning.
  • Use cases include baseline onboarding, audit trails, and reproducible provisioning across projects.

Quick Start

Persist or retrieve onboarding manifests by selecting Artifactory or Git as the backend via the manifest's state.destination.

Frequently Asked Questions about jfrog-system-config-repo

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

FAQPage Schema
How do I persist onboarding manifests using Artifactory or Git?▼

You can persist onboarding manifests by configuring the manifest's state.destination to route operations to either Artifactory or Git backends. This enables centralized audit trails and repeatable onboarding across projects.

What is the best way to store configuration data for reproducible provisioning?▼

Storing configuration data as onboarding manifests in Artifactory or Git provides centralized versioning and reproducible provisioning. The routing logic selects the backend automatically based on the manifest's destination state.

How do I route manifest storage operations between Git and Artifactory?▼

Manifest storage operations are routed automatically based on the state.destination field within the manifest itself, directing the persistence and retrieval actions to the selected Artifactory or Git backend.

Do I need to configure both Artifactory and Git to use this persistence approach?▼

You must enforce configuration via state.artifactory and state.git to establish repository access and branch selection guardrails. Artifactory serves as the default backend if no specific destination is defined.

Can I retrieve baseline onboarding manifests from Git for audit trails?▼

Yes, retrieving baseline onboarding manifests from Git supports audit trails and reproducible provisioning. The system enforces branch selection guardrails to ensure correct repository access during retrieval operations.

Why does manifest persistence require state.artifactory and state.git configurations?▼

Manifest persistence requires state.artifactory and state.git configurations to enforce guardrails for secure repository access and proper branch selection when routing operations across the two storage backends.

Related Skills

Explore More Software Engineering Skills→
SebasArenSebasAren
2

commit

Commit repository changes and persist session findings into .claude/rules/.

Community
Intermediate
ArtemioPadillaArtemioPadilla
3

release-check

Evaluate test coverage, security, changelog, dependencies, and tech debt to generate a GO/NO-GO release verdict.

Community
Advanced
TencentBlueKingTencentBlueKing
2.5k

artifactory-module-architecture

Architect Artifactory storage backends and artifact lifecycle policies for BK-CI.

Official
Intermediate
ProteusiqProteusiq
9

dotfiles

Provision a reproducible macOS developer environment with dotfiles and installer scripts.

Community
Advanced