/showroom:create-lab

๐Ÿ“ Workshop Lab Creation

Create hands-on workshop content where customers follow along step-by-step.


Is This The Right Skill?

Use create-lab when

Customers DO things hands-on

  • Customers click buttons, run commands, follow steps
  • You want Know โ†’ Do โ†’ Check structure
  • Multiple participants learning together
Use create-demo instead when

YOU present, customers watch

  • One-directional presentation (like PowerPoint)
  • Know โ†’ Show structure
  • Single presenter showing features
๐Ÿ’ก
Not sure? Labs are more interactive. Demos are more presentational.

What Youโ€™ll Need Before Starting

Required Inputs

๐Ÿ“š

Workshop Topic

Example: "Getting started with OpenShift Pipelines"

๐ŸŽฏ

Learning Goals

What should customers learn?

๐Ÿ“Š

Number of Sections

Typically 3โ€“5 modules

๐Ÿ“–

Reference Materials

Product docs, screenshots, etc.

What The AI Will Create

โœ…
Generated Files:
  • Navigation page (index.adoc)
  • Module files (one per section)
  • Know/Do/Check structure for each module
  • Placeholder images and examples
โ„น๏ธ
You DON'T need: Git knowledge, coding experience, or AsciiDoc expertise. The AI handles all technical aspects.

Quick Start

  1. Open Your IDE

    Launch Claude Code (or VS Code with Claude extension)

  2. Invoke Skill

    Type /showroom:create-lab in the chat

  3. Answer Questions

    Provide workshop title, abstract, technologies, modules, and objectives

  4. Review & Customize

    Review generated content and edit as needed


What It Creates

content/modules/ROOT/
โ”œโ”€โ”€ pages/
โ”‚   โ”œโ”€โ”€ index.adoc              # Navigation home
โ”‚   โ”œโ”€โ”€ module-01.adoc          # First module
โ”‚   โ”œโ”€โ”€ module-02.adoc          # Second module
โ”‚   โ””โ”€โ”€ module-03.adoc          # Third module
โ””โ”€โ”€ partials/
    โ””โ”€โ”€ _attributes.adoc        # Workshop metadata

Common Workflow

  1. Invoke Skill

    ``` /showroom:create-lab โ†’ Skill loads prompts from showroom/prompts/ ```
  2. Workshop Details

    Answer prompts for workshop title, abstract, technologies, and number of modules.

  3. Provide Showroom Repository Path

    Skill asks for your Showroom repo. You can provide a local path or a GitHub URL โ€” the skill auto-clones GitHub URLs to /tmp/:

    ``` # Local path ~/work/showroom-content/your-lab-showroom # GitHub URL (auto-cloned to /tmp/your-lab-showroom) https://github.com/rhpds/your-lab-showroom ```
  4. Showroom Scaffold (site.yml + ui-config.yml)

    Skill configures the two key infrastructure files in your Showroom repo (cloned from showroom_template_nookbag):

    ``` site.yml # Antora playbook โ€” fix title, ui-bundle theme ui-config.yml # Split view + tabs (view_switcher.enabled: true) ```

    Skill also asks: "Will this lab embed an OCP console or terminal tab?" โ€” configures console embedding if yes.

    โ„น๏ธ
    Showroom 1.5.3+ required for split-view and OCP console embedding. Clone from showroom_template_nookbag as your starting template.

    Existing nookbag repos: If your repo was cloned before March 2026, it may have [source,bash] blocks without role="execute". The skill detects this and offers to bulk-fix all existing modules. New content is always generated with [source,role="execute"] regardless.
  5. Generate Module Content

    Skill generates index.adoc and one file per module using Know/Do/Check structure. UserInfo attributes are written once in _attributes.adoc (no duplicate entries).

  6. Verify Content

    ``` /showroom:verify-content โ†’ Check quality and standards โ†’ Checks ui-config.yml for console and view_switcher ```
  7. Generate Blog Post (Optional)

    ``` /showroom:blog-generate โ†’ Transform to blog format ```

Module Structure Pattern

Know โ†’ Do โ†’ Check

Each module follows this proven learning pattern:

๐Ÿ“–

Know Section

  • Explains the concept
  • Provides context and background
โš™๏ธ

Do Section

  • Hands-on exercise
  • Step-by-step instructions
  • Code examples with syntax highlighting
โœ“

Check Section

  • Verification steps
  • Expected results
  • Troubleshooting tips

Tips & Best Practices

๐Ÿ“Š

Module Count

Start with 3โ€“4 modules for new workshops

โฑ๏ธ

Timing

Each module should take 10โ€“15 minutes

๐ŸŽฏ

Focus

Keep Do sections focused on one main task

๐Ÿ“ธ

Screenshots

Use screenshots sparingly (AsciiDoc format)


Troubleshooting

Skill not found? - Restart Claude Code or VS Code - Verify installation: `ls ~/.claude/skills/create-lab` (Claude Code) or `ls ~/.cursor/skills/showroom-create-lab` (Cursor) - Check the [Troubleshooting Guide](../reference/troubleshooting.html)
Generated content looks wrong? - Check your workshop template is up to date - Verify you're in the correct directory - Run `/showroom:verify-content` to check standards compliance