/showroom:verify-content
Validate Showroom workshop or demo content against Red Hat quality standards. Runs all checks silently, then gives you one findings table — pick what to fix first.
Quick Start
/showroom:verify-content
Run this from inside your Showroom repo. The skill auto-detects the content and starts immediately.
How It Works
-
Auto-detect
Checks the current directory for Showroom content (
content/modules/ROOT/pages/). Infers whether it's a workshop or demo from the file structure. If nothing is found in CWD, asks for a local path or GitHub URL. -
All checks run silently
Reads the appropriate verification prompt files for your content type, then runs everything in one pass — scaffold files, structure, AsciiDoc formatting, Red Hat style, and technical accuracy. No output until complete.
-
One findings table
Every issue in a single sorted table: Critical first, then High, Medium, Low. Scaffold issues appear before content issues.
``` | # | ID | Issue | Severity | Location | |---|-----|----------------------------------|----------|-------------------| | 1 | E.4 | Hardcoded cluster URL | Critical | module-02.adoc:88 | | 2 | S.1 | site.title is a template default | High | site.yml:3 | | 3 | C.5 | Code block missing language | High | module-01.adoc:47 | | 4 | D.2 | "AAP" without first-use expansion| High | 01-overview.adoc:12| Total: 4 issues — 1 Critical, 3 High ``` -
Fix by number
The skill asks: "Which issue do you want to fix first?" Enter the number. The skill shows before/after, applies the fix, confirms, then shows the remaining table. Repeat until done.
What It Checks
Scaffold (S)
site.yml— title, start_page, ui-bundle, supplemental_filesui-config.yml— type, view_switcher, tabs configuredcontent/antora.yml— title, name, nav, lab_name attribute.github/workflows/gh-pages.yml— references correct playbook
Structure (B)
- index, overview, details, conclusion modules exist
- Learning objectives ≥3 per module
- Exercises have numbered steps + Verify sections
- nav.adoc includes all module files
AsciiDoc (C)
- Code blocks have language specifier
- Images have descriptive alt text
- Sentence case headings
- External links open in new tab (
^)
Red Hat Style (D)
- No prohibited terms (robust, powerful, leverage)
- Acronyms expanded on first use
- Oxford comma, numerals for 0–9
- Inclusive language (they/them, allowlist/denylist)
Technical (E)
- No hardcoded cluster URLs, usernames, passwords
- Expected output after every command
- No skipped heading levels
- All
{attribute}placeholders defined - E.3a (Critical): All executable command blocks use
[source,role="execute"]— without it the Showroom copy/execute button does not render. Common in repos cloned from nookbag before March 2026. Bulk-fixable — pick E.3a in the fix loop to update all module files at once.
Demo-specific (F)
- Know section before Show section
- Business value stated per section
- Presenter notes present
- No hands-on exercises in presenter-led content
Tips
Run from the right directory
Start Claude Code inside your Showroom repo so the skill auto-detects without asking. cd ~/work/showroom-content/my-lab && claude
Fix Critical first
Enter the number of the Critical issue first. Critical = broken builds or broken navigation. Everything else is quality.
Re-run after fixing
Once you've fixed everything, run /showroom:verify-content again to confirm clean. The table should come back empty.
Before every PR
Run verification before creating a pull request. Zero findings = ready to merge.