Orchestrator skill for RHDH plugin development. Provides CLI tooling, activity tracking, and routes to specialized skills (overlay, etc.).
Orchestrates RHDH plugin development workflows by routing tasks, tracking activity, and providing CLI tooling for environment management.
/plugin marketplace add durandom/rhdh-skill/plugin install rhdh-plugin@rhdhThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/github-reference.mdreferences/jira-reference.mdreferences/slack-notification.mdreferences/versions.mdrhdh/__init__.pyrhdh/__main__.pyrhdh/cli.pyrhdh/config.pyrhdh/formatters.pyrhdh/todo.pyrhdh/worklog.pyrhdh/workspace.pyscripts/rhdh<cli_setup> Locate and set the CLI variable:
The CLI script is at scripts/rhdh relative to this SKILL.md file (not the working directory).
When you read this file, note its path and derive the script location:
/path/to/skills/rhdh/SKILL.md/path/to/skills/rhdh/scripts/rhdhRHDH="/path/to/skills/rhdh/scripts/rhdh" # Use the actual path
Get oriented (run first):
$RHDH
This shows environment status, discovered repos, and available tools. </cli_setup>
<essential_principles>
<principle name="track_activity"> Use `$RHDH log` and `$RHDH todo` to maintain context across sessions. Log milestones with tags. Create todos when blocked on external input. This enables resuming work without re-explaining context and builds an audit trail. See the `<tracking_system>` section for details. </principle> <principle name="consult_tool_references"> **Before using JIRA or GitHub CLI**, read the corresponding reference file: - **GitHub:** `references/github-reference.md` — PR queries, CI analysis, `/publish` triggers - **JIRA:** `references/jira-reference.md` — JQL queries, issue creation, comment formatThese contain critical gotchas (jq escaping, JQL limitations, assignee format) that prevent common errors. </principle>
</essential_principles>
<context_scan> Run on invocation to understand current state:
$RHDH
This checks:
If repos not found: Run $RHDH config init to auto-detect or configure paths.
</context_scan>
$RHDH
If needs_setup: true: Stop and run $RHDH doctor to fix setup issues.
What would you like to do?
For working with the rhdh-plugin-export-overlays repository
For creating new RHDH dynamic plugins from scratch
Wait for response before proceeding. </intake>
<routing> ### Doctor Route (Priority)| Condition | Action |
|---|---|
needs_setup: true in CLI output | Run $RHDH doctor |
Always check this first.
| Response | Skill |
|---|---|
| 1-5, "onboard", "update", "fix", "triage", "PR", "overlay", "plugin", "workspace" | Route to @overlay skill |
To route: Read ../overlay/SKILL.md and follow its intake process.
| Response | Skill |
|---|---|
| 6, "backend plugin", "create backend", "new backend plugin" | Route to @create-backend-plugin skill |
| 7, "frontend plugin", "create frontend", "new frontend plugin" | Route to @create-frontend-plugin skill |
| 8, "export", "package", "OCI", "publish plugin" | Route to @export-and-package skill |
| 9, "wiring", "mount points", "routes", "entity tabs" | Route to @generate-frontend-wiring skill |
To route: Read the corresponding skill file in ../ and follow its workflow.
| Response | Action |
|---|---|
| 10, "doctor", "setup", "config" | Use CLI commands below |
| 11, "log", "todo", "activity" | Use tracking commands below |
<cli_commands> Environment status (no args):
$RHDH
Shows overlay repo, rhdh-local, tools status, and next steps.
Full environment check:
$RHDH doctor
Configuration:
$RHDH config init # Create config with auto-detection
$RHDH config show # Show resolved paths
$RHDH config set overlay /path # Set repo location
$RHDH config set local /path # Set rhdh-local location
Workspace operations:
$RHDH workspace list # List all plugin workspaces
$RHDH workspace status <name> # Show workspace details
</cli_commands>
<tracking_system>
The CLI includes worklog and todo tracking to maintain context across sessions. Use is recommended but not required.
Append-only activity log stored in .rhdh/worklog.jsonl:
# Log activity with tags for searchability
$RHDH log add "Started onboard: aws-appsync" --tag onboard --tag aws-appsync
$RHDH log add "PR #1234 merged" --tag aws-appsync --tag pr
# View recent entries
$RHDH log show --limit 10
# Search past activity
$RHDH log search "aws-appsync"
$RHDH log search "onboard"
Section-based markdown todos stored in .rhdh/TODO.md:
# Create todo when blocked
$RHDH todo add "Check license with legal" --context "aws-appsync"
$RHDH todo add "Follow up on stale PR #1234" --context "triage"
# List and manage
$RHDH todo list # All todos
$RHDH todo list --pending # Only open items
# Update progress
$RHDH todo note <slug> "Sent email to legal@redhat.com"
$RHDH todo done <slug>
# View raw file
$RHDH todo show
Log these milestones:
Create todos for:
Todos must be self-contained—a new session should understand the task without re-investigating.
| ❌ Too vague | ✅ Actionable |
|---|---|
| Fix #1875 version mismatch | Fix #1875 (lightspeed): bump 1.3.0→1.4.0 in workspace.yaml like #1903 |
| Add /ok-to-test to #1921 | Add /ok-to-test to #1921 (techdocs) — smoke tests ready, needs external trigger |
| Review #1906 SonarCloud | Review #1906 (catalog): SonarCloud blocked on coverage — check if test file missing |
Include: PR number, plugin name, specific action, and why it's needed.
</tracking_system>
<reference_index> GitHub CLI (PRs, CI, workflows): references/github-reference.md JIRA CLI (issues, JQL, comments): references/jira-reference.md </reference_index>
<skills_index>
| Skill | Purpose | Path |
|---|---|---|
| overlay | Manage plugins in rhdh-plugin-export-overlays | ../overlay/SKILL.md |
| create-backend-plugin | Bootstrap new RHDH backend dynamic plugins | ../create-backend-plugin/SKILL.md |
| create-frontend-plugin | Bootstrap new RHDH frontend dynamic plugins | ../create-frontend-plugin/SKILL.md |
| export-and-package | Export and package plugins as OCI/tgz/npm | ../export-and-package/SKILL.md |
| generate-frontend-wiring | Configure frontend mount points, routes, tabs | ../generate-frontend-wiring/SKILL.md |
| Reference | Purpose | Path |
|---|---|---|
| versions | RHDH/Backstage version compatibility matrix | references/versions.md |
</skills_index>
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.