wrkx-clone

Clone all repositories defined in wrkx.json into their configured paths.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ClankerGuru/opsx --skill wrkx-clone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wrkx-clone
Source: https://github.com/ClankerGuru/opsx/tree/main/cli/src/main/resources/content/skills/wrkx-clone
Command: npx skills add https://github.com/ClankerGuru/opsx --skill wrkx-clone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bootstrap a workspace by cloning every repo listed in wrkx.json into its configured path, ensuring an idempotent setup where existing repos are skipped.

Core Features & Use Cases

  • Batch clone: clones all repos defined in wrkx.json into their configured paths.
  • Variant support: supports /wrkx-clone (all repos) and /wrkx-clone-<repo> (single repo) activations.
  • Idempotent bootstrap: avoids re-cloning repos already present on disk and respects baseBranch/workingBranch if declared.

Quick Start

Run the wrkx-clone skill from the workspace root to clone all repositories defined in wrkx.json.

Frequently Asked Questions about wrkx-clone

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

FAQPage Schema
How do I batch clone all repositories defined in wrkx.json into my workspace?

To batch clone repositories defined in wrkx.json, run the wrkx-clone skill from your workspace root. It reads the configuration file and clones every listed repository into its configured path, skipping any repositories already present on disk for an idempotent bootstrap.

Can I clone a single repository from wrkx.json instead of all of them?

Yes, you can clone a single named repository from wrkx.json by using the /wrkx-clone-<repo> variant activation. This targets only the specified repository, cloning it into its configured path while respecting any declared baseBranch or workingBranch settings.

What fields does a wrkx.json file need to support workspace bootstrapping?

A wrkx.json file requires name, path, and remote fields for each repository entry to support workspace bootstrapping. It also accepts optional baseBranch and workingBranch fields to specify which git branches are checked out during the cloning process.

Does cloning repositories from wrkx.json skip directories that already exist?

Yes, cloning repositories from wrkx.json skips directories that already exist on disk. This idempotent behavior prevents re-cloning during workspace refreshes, ensuring existing repositories remain untouched while missing ones are cloned.

What dependencies are required to bootstrap a workspace using wrkx.json?

Bootstraping a workspace using wrkx.json requires git installed locally and network access to the remote repositories. The skill uses git to clone repositories from their remotes into the configured local paths.

When should I use wrkx.json for workspace bootstrapping over manual git clone commands?

Use wrkx.json for workspace bootstrapping when you need to clone multiple repositories into specific paths with consistent branch configurations. It automates batch cloning and idempotent refreshes, eliminating the need to run individual manual git clone commands.