fix inconsistencies

Signed-off-by: Kashish Mittal <kmittal@redhat.com>

Author: 04kash

README.md

@@ -18,6 +18,21 @@ Agent Skills for adopting and using [Red Hat Developer Hub](https://developers.r
 
 Interactive authoring for RHDH Scaffolder templates — templatize an existing repo, create from scratch, fix common gotchas, and validate locally or against a running instance.
 
+- **[rhdh-templates](./skills/rhdh-templates/SKILL.md)** — Interactive authoring and validation for Software Templates. Includes curated reference catalog (official library + AI quickstarts), worked examples (`nodejs-backend`, `java-springboot`) and bundled JSON Schema validation. Sub-commands:
+  - **[init](./skills/rhdh-templates/references/init.md)** — Check tooling, scaffold template repo layout, optional RHDH connectivity.
+  - **[templatize](./skills/rhdh-templates/references/templatize.md)** — Convert existing codebase into a parameterized template.
+  - **[create](./skills/rhdh-templates/references/create.md)** — Guided from-scratch template authoring when no reference code exists.
+  - **[add-parameter](./skills/rhdh-templates/references/add-parameter.md)** — Add a parameter or parameter group to existing `template.yaml`.
+  - **[add-step](./skills/rhdh-templates/references/add-step.md)** — Add a scaffolder step to existing `template.yaml`.
+  - **[add-skeleton](./skills/rhdh-templates/references/add-skeleton.md)** — Add or parameterize skeleton files with Nunjucks.
+  - **[create-location](./skills/rhdh-templates/references/create-location.md)** — Generate or update root `location.yaml` for catalog registration.
+  - **[fix-gotchas](./skills/rhdh-templates/references/fix-gotchas.md)** — Auto-fix common RHDH template mistakes (raw/endraw blocks, catalog-info path, etc.).
+  - **[validate](./skills/rhdh-templates/references/validate.md)** — Local YAML schema, gotcha validation, and optional Nunjucks lint via `--lint-skeleton` (no RHDH required).
+  - **[list-actions](./skills/rhdh-templates/references/list-actions.md)** — List available Scaffolder actions from a running RHDH instance.
+  - **[dry-run](./skills/rhdh-templates/references/dry-run.md)** — Test template execution via Scaffolder v2 dry-run API.
+  - **[explain-action](./skills/rhdh-templates/references/explain-action.md)** — Show action input schema or template parameter schema.
+  - **[example-catalog](./skills/rhdh-templates/references/example-catalog.md)** — Browse curated reference templates (official library, AI quickstarts, bundled).
+
 Example prompts:
 
 - "Help me turn this Node.js repo into an RHDH Software Template"
@@ -78,6 +93,7 @@ npx skills add ./rhdh-users-skill-pack
 You can also name the skill explicitly:
 
 ```
+Use the rhdh-templates skill to validate my template.yaml
 Use the skill-maker skill to audit my SKILL.md
 ```
 

skills/rhdh-templates/SKILL.md

@@ -7,7 +7,7 @@ description: >-
   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 do customers use",
+  "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,
@@ -96,7 +96,7 @@ Command descriptions and argument hints: `scripts/command-metadata.json`
 | 11, "dry-run", "dry run", "test template remotely" | [references/dry-run.md](references/dry-run.md) |
 | 12, "explain-action", "action schema", "parameter schema" | [references/explain-action.md](references/explain-action.md) |
 | 13, "examples", "reference templates", "show me templates", "what templates exist" | [references/example-catalog.md](references/example-catalog.md) |
-| First word doesn't match | Infer from context. "Turn my Spring Boot app into a template" → `templatize`. "Add owner picker to my template" → `add-parameter`. "Does my template validate?" → `validate`. "What templates do customers use?" → `examples`. |
+| First word doesn't match | Infer from context. "Turn my Spring Boot app into a template" → `templatize`. "Add owner picker to my template" → `add-parameter`. "Does my template validate?" → `validate`. "What example templates exist?" → `examples`. |
 
 </routing>
 

skills/rhdh-templates/assets/examples/README.md

@@ -8,7 +8,7 @@ For the full curated catalog of upstream reference templates (official library,
 python skills/rhdh-templates/scripts/list_examples.py --recommended --json
 ```
 
-See [../references/example-catalog.md](../references/example-catalog.md) for category guide and customer-demand context.
+See [../references/example-catalog.md](../references/example-catalog.md) for category guide and common-demand context.
 
 | Example | Stack | Highlights |
 |---------|-------|------------|

skills/rhdh-templates/references/create.md

@@ -37,7 +37,7 @@ python <skill-dir>/scripts/list_examples.py \
 
 Present upstream URLs from the matches. When a match includes `local_bundled`, also point at `assets/examples/<name>/` for offline patterns. Ask whether to mirror a reference's step sequence or start from `assets/examples/minimal-template/`.
 
-Load `example-catalog.md` when the user asks what customers typically build.
+Load `example-catalog.md` when the user asks what templates teams typically build.
 
 ## Step 2: Ensure layout
 

skills/rhdh-templates/references/example-catalog.md

@@ -8,7 +8,7 @@
 
 <process>
 
-Surface curated reference templates customers reach for most often. Use when the user asks "what templates exist?", "show me an example", "what do customers usually build?", or before `create` / `templatize` to pick a study reference.
+Surface curated reference templates teams reach for most often. Use when the user asks "what templates exist?", "show me an example", "what do teams usually build?", or before `create` / `templatize` to pick a study reference.
 
 ## Step 1: Parse intent
 
@@ -70,7 +70,7 @@ Upstream templates in GitHub are **learning aids**, not production-ready golden
 | AI Lab samples | [ai-lab-template](https://github.com/redhat-ai-dev/ai-lab-template) | Smaller AI samples (RAG, chatbot, codegen) |
 | Bundled skill examples | `assets/examples/` in this skill | Local validation, minimal patterns without cloning repos |
 
-## Categories (customer demand order)
+## Categories (common demand order)
 
 1. **backend** — Go, Node.js, Spring Boot, Quarkus, Python services with CI (most common golden path)
 2. **catalog** — Register existing repos into the Software Catalog
@@ -93,15 +93,15 @@ Templates marked **recommended** upstream (`tags: recommended` in their `templat
 | AI / RAG / agent request | Prefer `ai-quickstart-templates` over generic backend examples |
 | Import-only workflow | Point at `register-component` |
 
-Do not copy upstream skeletons wholesale into customer repos without review — study their **parameter forms**, **step sequences**, and **conventions**, then adapt.
+Do not copy upstream skeletons wholesale into target repos without review — study their **parameter forms**, **step sequences**, and **conventions**, then adapt.
 
 ## Catalog maintenance
 
 Data lives in `assets/example-catalog.json`. Refresh when:
 
 - `templates.yaml` changes in the official library
 - New AI quickstart templates ship
-- Field teams report a recurring customer pattern not yet listed
+- Teams report a recurring pattern not yet listed
 
 Run `list_examples.py --json` after edits to verify parsing.
 

tests/unit/test_claude_md.py

@@ -50,4 +50,5 @@ def test_has_verification_command(self, agents_md):
     def test_has_available_skills_section(self, agents_md):
         """AGENTS.md should list user-facing skills."""
         assert "## Available skills" in agents_md
+        assert "rhdh-templates" in agents_md
         assert "skill-maker" in agents_md