detect-existing-patterns

Detect and analyze JFrog Platform repository naming patterns to guide onboarding.

5|1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/jfrog/ai-agent-examples --skill detect-existing-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-existing-patterns
Source: https://github.com/jfrog/ai-agent-examples/tree/main/onboarding-workflows/skills/detect-existing-patterns
Command: npx skills add https://github.com/jfrog/ai-agent-examples --skill detect-existing-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboarding new projects and repositories on the JFrog Platform often requires aligning with existing naming conventions. This skill detects and analyzes existing project and repository names and presents a choice between following detected conventions or applying standard onboarding rules.

Core Features & Use Cases

  • Scans all existing projects and repositories to identify separators, component order, virtual suffix, and token mappings used in repo names.
  • Generates concrete example names for both the detected naming pattern and the standard onboarding pattern to aid decision making.
  • Interactively presents a clear choice to the user before provisioning new projects or repositories.

Quick Start

Ask the system to detect existing naming patterns and present a choice between the detected pattern and the standard onboarding pattern.

Frequently Asked Questions about detect-existing-patterns

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

FAQPage Schema
How do I detect existing repository naming patterns on the JFrog Platform?

It scans all existing projects and repositories to analyze separators, component order, virtual suffix usage, and token mappings, deriving a naming_pattern object to guide your repository onboarding decisions.

Can I automatically align new repository provisioning with existing naming conventions?

Yes, you can align new repository provisioning by generating a naming_pattern object that captures type_map and eco_map fields, driving automated repository creation that matches your detected conventions.

Does the JFrog Platform naming pattern analysis require API access?

Yes, performing naming pattern analysis requires access to JFrog Platform APIs to scan existing projects and extract repository naming structures for the naming_pattern object.

What is the best way to standardize repository onboarding rules versus detected naming patterns?

The best way is to generate concrete example names for both detected patterns and standard onboarding rules, then interactively present a clear choice to the user before provisioning new repositories.

How do I map repository tokens and virtual suffixes during project onboarding?

You map repository tokens and virtual suffixes during onboarding by analyzing existing repository names to derive a naming_pattern object containing virtual_suffix, type_map, and eco_map fields.