redhat-developer/rhdh-users-agent-plugin

Author and validate RHDH Software Templates (Scaffolder) with AI-guided workflows. Use when asked to "create software template", "templatize a codebase", "convert repo to template", "write template.yaml", "location.yaml for templates", "scaffolder template", "golden path template", "parameterize skeleton files", "fix template gotchas", "validate template", "dry-run template", "list scaffolder actions", "explain scaffolder action", "Nunjucks in template", "template best practices", "reference templates", "example templates", "what templates are commonly used", "Template Editor", or mentions RHDH template authoring, Software Catalog templates, or /rhdh-templates commands. Covers setup, templatize (highest value), from-scratch create, reference example discovery, incremental parameter/step/skeleton authoring, location.yaml generation, common convention fixes, local validation, and live Scaffolder API dry-run/action discovery.

Customer-facing upgrade assessment for RHDH. Analyzes your configuration files (or asks about your environment) against a target RHDH release to produce a concrete migration plan with readiness scoring. Use when upgrading RHDH, planning a migration, checking what breaks in a new version, assessing upgrade impact, or asking "can I upgrade to X.Y", "what changed between versions", "migration guide", "upgrade checklist", "is my config compatible". No Jira access or Red Hat subscription required.

Create, audit, or consolidate agent skills following the Agent Skills open standard (agentskills.io). Interviews the user relentlessly about intent, scope, and edge cases before drafting. Covers SKILL.md structure, frontmatter, progressive disclosure, description optimization, script bundling, sub-command architecture, setup gates, context systems, and review. Use when the user wants to create a skill, write a skill, build a new skill, make a skill, draft a SKILL.md, or mentions "skill-maker". Also use when asked to review a skill, audit a SKILL.md, check why a skill never triggers, improve an existing skill, or fix a skill. Also use when asked to package expertise, workflows, or domain knowledge into a reusable skill. Also use when asked to consolidate skills, merge skills, combine skills, reduce skill count, or refactor multiple skills into one.