메뉴
This skill should be used when the user asks to "create a demo module", "write a Know/Show demo", "build a presenter demo", "create a Showroom demo", "write a facilitator guide", "build a demo script", or "create a presenter-led demo for RHDP".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
This skill should be used when the user asks to "create a catalog", "build a common.yaml", "add a new RHDP lab", "set up a new catalog item", "create an AgnosticV catalog", "build a dev.yaml", "add a catalog entry", or "create a new lab catalog for RHDP".
This skill should be used when the user asks to "validate my catalog", "check my AgnosticV config", "review common.yaml", "validate my RHDP catalog", "check for errors in my catalog", "lint my AgnosticV files", or "verify my catalog before submitting".
This skill should be used when the user asks to "turn this lab into a blog post", "write a blog post from this module", "generate a blog from my Showroom content", "convert my workshop to a blog", "write a Red Hat Developer blog post", or "create a blog post from my demo".
This skill should be used when the user asks to "create a lab module", "write a workshop module", "build a Showroom lab", "convert docs to a lab", "write a hands-on exercise", "create an AsciiDoc module", or "turn this documentation into a lab exercise".
This skill should be used when the user asks to "write solve and validate playbooks", "add E2E testing to my lab", "generate solve.yml", "generate validate.yml", "add solve and validate buttons", "set up runtime automation", "add ZT grading to my lab", "set up load testing for my lab", "add Demolition grading", or "configure run_e2e_load_test".
Infrastructure Health Checker — use this when you need to validate that a workload or service DEPLOYED SUCCESSFULLY (pods running, routes accessible, dependencies ready). This is NOT for student E2E lab testing. For student exercise validation (solve/validate buttons), use /ftl:rhdp-lab-validator instead. Triggers on: 'create a validation role', 'build health checks', 'add deployment validation', 'create post-deployment checks', 'validate my deployment', 'check if my workload is healthy'.
| name | showroom:create-demo |
| description | This skill should be used when the user asks to "create a demo module", "write a Know/Show demo", "build a presenter demo", "create a Showroom demo", "write a facilitator guide", "build a demo script", or "create a presenter-led demo for RHDP". |
Orchestrates agents to create Red Hat Showroom presenter-led demo content using the Know/Show structure. Two modes: interactive (human) and headless (Publishing House via ph_payload).
This skill is an orchestrator. Generation and review are delegated to agents:
showroom:file-generator (Sonnet) — generates one AsciiDoc file, runs in parallel for new demosshowroom:module-reviewer (Sonnet) — quality check on generated filesThe orchestrator handles: argument parsing, repo detection, planning, agent spawning, nav merge, delivery.
Demos separate what presenters need to understand from what they need to do:
See @showroom/skills/create-demo/references/content-rules.md for detailed Know/Show patterns.
See @showroom/docs/SKILL-COMMON-RULES.md for AsciiDoc rules, version pinning, image conventions.
If ph_payload is present, skip ALL interactive questions and run headless. Return structured JSON.
ph_payload:
target_dir: content/modules/ROOT/pages/
mode: new | continue
previous_module: 03-module-01-pipelines.adoc # continue mode only
spec:
demo_name: OpenShift Pipelines Live Demo
audience: Platform Engineers, Architects
business_scenario: ACME Corp needs to modernize their CI/CD pipeline
key_messages: [Speed up delivery, Reduce toil, Enterprise-grade reliability]
duration: 45min
module_outline: |
Module 1: Pipeline overview (~15 min)
Module 2: Live pipeline run (~20 min)
Module 3: Monitoring and insights (~10 min)
env:
ocp_version: "4.18"
attributes: {user: user1, password: openshift}
Headless return (JSON only):
{
"files_created": ["index.adoc", "01-overview.adoc", "02-details.adoc", "03-module-01-pipelines.adoc"],
"nav_updated": true,
"quality": {"critical": 0, "high": 0, "warnings": 1},
"warnings": ["No customer ROI metrics provided — add in Know section"]
}
/create-demo # interactive
/create-demo <directory> # specify target directory
/create-demo <directory> --new # new demo
/create-demo <directory> --continue <module> # continue from module
Validate directory exists. If empty: tell user to clone nookbag template:
git clone https://github.com/rhpds/showroom_template_nookbag <repo-name>
If not set by arguments:
Are you:
1. Starting a NEW demo (creates index + overview + details + first module)
2. Adding a module to an EXISTING demo
For NEW demo — ask as one grouped form:
Let's plan your demo. Answer what you know — skip anything you're unsure about:
Demo name:
Target audience (e.g. Platform Engineers, Solution Architects, CxOs):
Primary business challenge being solved:
Key messages (3-4 points you want the audience to leave with):
Duration (e.g. 20min, 45min, 1hr):
Module breakdown (how many modules, what each demonstrates):
Customer story or ROI metrics to reference (or leave blank):
Competitive angle (what makes this stand out vs alternatives):
OpenShift version (or leave blank for {ocp_version} placeholder):
Access type (admin / multi-user):
UserInfo variables (paste from demo.redhat.com → My services → Details → Advanced settings):
Leave blank to use placeholders {user}, {password}, {openshift_console_url}
Reference materials (URLs, docs, competitive briefs — leave blank to use templates):
Writing style (optional — skip for standard Red Hat style):
Describe: "executive-friendly, outcome-focused, analogies over jargon"
OR paste 1-3 paragraphs of your own writing as an example
OR give a file path to an existing demo module you wrote
Saved profile? Point to: ~/.claude/context/my-writing-style.md
Confirm plan in one summary:
📋 Demo plan confirmed:
Demo: [name] | [audience] | [duration]
Modules: [breakdown]
Key messages: [list]
Generating files... (running in parallel)
For CONTINUE mode:
Which module are you adding? (title + what you'll demonstrate)
Reference materials for this module? (URLs or blank)
Ask Q0–Q3 from @showroom/skills/create-demo/references/showroom-scaffold.md:
Create/update site.yml and ui-config.yml in repo root.
Build FULL_SPEC JSON from planning answers. Set CONTENT_TYPE: demo.
NEW demo — spawn all files simultaneously:
Task tool:
subagent_type: showroom:file-generator
prompt: |
TARGET_FILE: <repo_path>/content/modules/ROOT/pages/index.adoc
FILE_TYPE: index
FULL_SPEC: <FULL_SPEC JSON>
LAB_TYPE: <ocp|rhel|vm|ai>
CONTENT_TYPE: demo
REPO_PATH: <absolute repo path>
Task tool:
subagent_type: showroom:file-generator
prompt: |
TARGET_FILE: <repo_path>/content/modules/ROOT/pages/01-overview.adoc
FILE_TYPE: overview
CONTENT_TYPE: demo
FULL_SPEC: <FULL_SPEC JSON>
...
Task tool:
subagent_type: showroom:file-generator
prompt: |
TARGET_FILE: <repo_path>/content/modules/ROOT/pages/02-details.adoc
FILE_TYPE: details
CONTENT_TYPE: demo
FULL_SPEC: <FULL_SPEC JSON>
...
Task tool:
subagent_type: showroom:file-generator
prompt: |
TARGET_FILE: <repo_path>/content/modules/ROOT/pages/03-module-01-<slug>.adoc
FILE_TYPE: module
CONTENT_TYPE: demo
FULL_SPEC: <FULL_SPEC JSON>
...
All four run concurrently.
CONTINUE mode — single agent:
Task tool:
subagent_type: showroom:file-generator
prompt: |
TARGET_FILE: <next-module path>
FILE_TYPE: module
CONTENT_TYPE: demo
PREVIOUS_MODULE: <path to previous .adoc>
FULL_SPEC: <FULL_SPEC JSON>
REPO_PATH: <absolute repo path>
Spawn showroom:module-reviewer on each generated file with CONTENT_TYPE: demo:
Task tool:
subagent_type: showroom:module-reviewer
prompt: |
MODULE_FILE: <path>
CONTENT_TYPE: demo
LAB_TYPE: <ocp|rhel|vm|ai>
SHARED_CONTEXT: <JSON>
REPO_PATH: <absolute repo path>
is_first_module: <true if overview>
is_conclusion: false
Fix any Critical or High issues before delivering.
Merge nav_entry values from file-generator outputs. Update content/modules/ROOT/nav.adoc.
Human mode:
✅ Files created:
index.adoc
01-overview.adoc
02-details.adoc
03-module-01-<slug>.adoc
✅ nav.adoc updated
Quality: 0 Critical, 0 High, 1 Warning
- W1: No customer ROI metrics — add in Know section when available
Next: Add more modules with /create-demo --continue, or verify with /verify-content
Headless mode: return JSON from ph_payload schema.
When all modules complete:
Task tool:
subagent_type: showroom:file-generator
prompt: |
FILE_TYPE: conclusion
CONTENT_TYPE: demo
FULL_SPEC: <FULL_SPEC JSON with all module summaries>
...
See @showroom/skills/create-demo/references/conclusion-template.md for demo conclusion structure (ROI recap, call-to-action, presenter action items, Q&A guidance).
/showroom:verify-content — full quality review after content is created/showroom:create-lab — hands-on workshop content/showroom:blog-generate — transform demo to blog post