wrkx

Lists all registered wrkx workspace tasks and per-repo variants from wrkx.json without modifying files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

List every registered wrkx workspace task (clone, pull, checkout, status, prune) plus the per-repo variants. Activates when the user wants to see, list, or discover what workspace commands are available.

Core Features & Use Cases

  • Lists aggregate tasks like wrkx, wrkx-clone-<repo>, wrkx-pull-<repo>, wrkx-checkout-<repo>, wrkx-status, wrkx-prune.
  • Reveals per-repo task variants derived from wrkx.json, enabling quick auditing of workspace actions.
  • Use case: audit your Gradle wrkx configuration to understand available actions before executing automation.

Quick Start

Run wrkx to print the catalog of all wrkx tasks for your workspace.

Frequently Asked Questions about wrkx

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

FAQPage Schema
How do I list all Gradle workspace tasks configured in wrkx.json?

To list Gradle workspace tasks configured in wrkx.json, run the wrkx command from your workspace root to print a complete catalog of all registered aggregate and per-repo tasks.

What wrkx commands are available for cloning and pulling per-repo variants?

Available wrkx commands include aggregate tasks like clone, pull, checkout, status, and prune, alongside per-repo variants such as wrkx-clone-<repo> and wrkx-pull-<repo> derived from wrkx.json.

Can I audit my Gradle wrkx configuration without modifying the repository?

You can audit your Gradle wrkx configuration without modifying the repository by running the wrkx command, which reads wrkx.json and enumerates tasks via the zone.clanker.wrkx settings plugin.

How do I discover per-repo task coverage for a wrkx workspace?

To discover per-repo task coverage for a wrkx workspace, execute the wrkx command from the workspace root to reveal all per-repo variants derived from your wrkx.json file.

Does the wrkx task catalog require the zone.clanker.wrkx settings plugin?

The wrkx task catalog relies on the zone.clanker.wrkx settings plugin to read wrkx.json and enumerate all available workspace commands and per-repo variants.

What is the best way to see available wrkx workspace actions before running automation?

The best way to see available wrkx workspace actions before running automation is to run the wrkx command, which outputs a full catalog of clone, pull, checkout, status, and prune tasks.