Menu
Transform completed Red Hat Showroom lab modules or demo content into blog posts for Red Hat Developer, internal blogs, or marketing platforms.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run comprehensive quality verification on workshop or demo content using Red Hat standards and validation agents.
Generate AgnosticV catalog description from lab or demo content for RHDP provisioning.
Guide you through creating a Red Hat Showroom demo module using the Know/Show structure for presenter-led demonstrations.
Guide you through creating a single Red Hat Showroom workshop module from reference materials (URLs, files, docs, or text) with business storytelling and proper AsciiDoc formatting.
| name | blog-generate |
| description | Transform completed Red Hat Showroom lab modules or demo content into blog posts for Red Hat Developer, internal blogs, or marketing platforms. |
Transform completed Red Hat Showroom lab modules or demo content into blog posts for Red Hat Developer, internal blogs, or marketing platforms.
Use this skill when you want to:
Don't use this for:
/create-lab/create-demoIMPORTANT: This skill follows shared contracts defined in .claude/docs/SKILL-COMMON-RULES.md:
Blog generation does NOT directly create lab content, so some shared rules (version pinning, navigation updates, image paths) apply only to source modules.
See SKILL-COMMON-RULES.md for complete details.
I'll ask you:
Source modules:
workshop/openshift-pipelines/03-module-01.adoc)Source type:
I'll ask:
Target platform:
Output format (auto-selected based on platform):
Blog type:
Technical depth:
Blog parameters:
I'll:
Based on source type and target, I'll transform:
Workshop → Developer Blog:
Demo → Product Announcement:
Workshop → Marketing Blog:
Demo → Thought Leadership:
DEFAULT OUTPUT FORMAT: Markdown (.md)
I'll create a blog post with:
For Technical Blogs (Markdown format):
# Building Cloud-Native CI/CD Pipelines with OpenShift Pipelines
> **Summary**: Learn how to create production-ready CI/CD pipelines using Tekton on OpenShift in under 30 minutes.
## Introduction
If you've struggled with complex Jenkins configurations or brittle CI/CD scripts, OpenShift Pipelines offers a cloud-native alternative. Built on Tekton, it brings Kubernetes-native CI/CD to your workflows with declarative pipelines that scale with your applications.
In this tutorial, you'll learn how to:
- Create reusable Tekton tasks
- Build complete CI/CD pipelines
- Integrate with Git repositories
- Deploy applications automatically
## What You'll Build
By the end of this tutorial, you'll have a working pipeline that:
- Builds container images from source code
- Runs automated tests
- Deploys to OpenShift automatically
Let's dive in.
## Creating Your First Tekton Task
Tekton tasks are the building blocks of pipelines. Here's how to create a simple build task:
\`\`\`yaml
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
name: build-app
spec:
steps:
- name: build
image: maven:3.8
script: |
mvn clean package
\`\`\`
Apply this to your cluster:
\`\`\`bash
oc apply -f build-task.yaml
\`\`\`
This creates a reusable task that can be referenced in any pipeline. What makes this powerful is the ability to chain multiple tasks together...
## Building a Complete Pipeline
Now let's combine multiple tasks into a production-ready pipeline:
\`\`\`yaml
apiVersion: tekton.dev/v1beta1
kind: Pipeline
metadata:
name: build-and-deploy
spec:
tasks:
- name: build
taskRef:
name: build-app
- name: test
taskRef:
name: run-tests
runAfter:
- build
- name: deploy
taskRef:
name: deploy-to-openshift
runAfter:
- test
\`\`\`
The `runAfter` fields ensure tasks execute in the correct order...
## Next Steps
You've built a working CI/CD pipeline with OpenShift Pipelines. From here, you can:
- Add Git triggers for automatic builds
- Integrate security scanning
- Create multi-environment pipelines
## Try It Yourself
Want hands-on practice? Try the complete workshop: [OpenShift Pipelines Workshop](https://showroom.example.com/pipelines)
## Resources
- [OpenShift Pipelines Documentation](https://docs.openshift.com/pipelines/)
- [Tekton Official Site](https://tekton.dev)
- [Example Pipelines Repository](https://github.com/...)
---
**About this tutorial**: This post is based on a hands-on workshop created for Red Hat field demonstrations. [Try the full lab on Red Hat Showroom](https://showroom.example.com/pipelines).
---
**Tags**: OpenShift, CI/CD, Tekton, Kubernetes, DevOps
**Author**: [Your Name]
**Published**: [Date]
For Marketing Blogs:
# [Benefit-Focused Title]
**Introduction**:
- Business challenge hook
- What this means for readers
- Value proposition
**The Challenge**:
- Current state pain points
- Industry context
- Why change is needed
**The Solution**:
- Product/capability overview
- Key benefits (not features)
- Customer success snippets
**Business Impact**:
- Quantified outcomes
- Strategic advantages
- ROI considerations
**Getting Started**:
- Simple next steps
- Resources available
- Support options
**CTA**:
- Request demo
- Try it yourself
- Contact sales
**Metadata**:
- Executive-friendly title
- SEO-optimized description
- Product tags
Red Hat Developer Blog (developers.redhat.com):
\`\`\`bash
oc create deployment my-app --image=myimage:latest
\`\`\`
\`\`\`yaml
apiVersion: apps/v1
kind: Deployment
\`\`\`
Medium, dev.to, Hashnode:
Internal Red Hat Blogs (Source, Memo):
Marketing/Announcement Format:
)I'll:
Source Traceability (REQUIRED):
Every blog must include attribution to prevent over-claiming and confusion about authoritative docs vs narrative content.
For Red Hat Developer Blog:
---
**About this tutorial**: This post is based on a hands-on workshop created for Red Hat field demonstrations. [Try the full lab on Red Hat Showroom](https://showroom.example.com/...).
For Internal Blogs:
---
**Source**: Adapted from the "OpenShift Pipelines" demo used in customer technical briefings.
For Marketing Blogs:
---
**About**: This article is based on technical demonstrations shown at Red Hat Summit and customer events.
Rules:
You'll get:
Output location: blog-posts/<topic-slug>.md
If AsciiDoc requested (rare):
blog-posts/<topic-slug>.adocSource (workshop exercise):
== Exercise 1: Create Tekton Pipeline
. Create a task definition:
+
[source,yaml]
----
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
name: build-app
----
. Apply the task:
+
[source,bash]
----
oc apply -f task.yaml
----
Output (blog narrative):
## Building Your First CI/CD Pipeline with Tekton
Tekton Pipelines brings cloud-native CI/CD to OpenShift. Instead of wrestling with
complex Jenkins configurations, you can define your entire build process as
Kubernetes-native resources.
Let's start by creating a simple build task. In Tekton, tasks are reusable building
blocks that define a series of steps:
\`\`\`yaml
apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
name: build-app
spec:
steps:
- name: build
image: maven:3.8
script: |
mvn clean package
\`\`\`
Apply this task to your cluster with `oc apply -f task.yaml`, and you've just
created your first reusable CI/CD component. What makes this powerful is...
Source (demo Know section):
=== Know
_Customer challenge: Deployment cycles take 6-8 weeks, blocking critical business initiatives._
**Business Impact:**
* Development teams wait 6-8 weeks for platform provisioning
* Manual processes cause errors and rework
Output (marketing blog):
## Accelerating Time-to-Market with OpenShift
For many organizations, application deployment isn't just slow—it's a strategic
bottleneck. We've seen development teams wait 6 to 8 weeks just to provision
infrastructure, turning agile development into waterfall delivery.
OpenShift eliminates this bottleneck through self-service developer platforms that
reduce deployment time from weeks to minutes. Your developers get the infrastructure
they need when they need it, without manual ticket-and-wait processes...
User: Create a developer blog from my OpenShift Pipelines workshop modules:
workshop/openshift-pipelines/03-module-01.adoc
workshop/openshift-pipelines/04-module-02.adoc
Skill: I'll transform those modules into a developer blog. Let me ask...
Q1: Source modules? → [already provided]
Q2: Source type? → Workshop modules
Q3: Target platform? → Red Hat Developer blog
Q4: Blog type? → Technical tutorial
Q5: Technical depth? → Highly technical (for developers)
Q6: Word count? → 1500-2000 words
Q7: Include code samples? → Yes, comprehensive
Q8: Audience level? → Intermediate
[Reads both modules]
[Extracts: Tekton tasks, pipeline definitions, execution steps]
[Transforms exercises into narrative flow]
[Generates:]
✓ Created: blog-posts/openshift-pipelines-tutorial.md
✓ Format: Markdown for Red Hat Developer
✓ Length: ~1800 words
✓ Includes: 5 code examples, 3 screenshot references
✓ CTA: Links back to full Showroom workshop
✓ Metadata: Title, tags, description included
For Technical Blogs:
For Marketing Blogs:
General:
Pattern:
Don't:
Do:
Pattern:
Don't:
Do:
Every generated blog will have:
Red Hat Developer:
Internal Blogs (Source/Memo):
Marketing:
Agents invoked:
technical-editor - Refines tone and claritystyle-enforcer - Applies Red Hat standardsOutput format:
Why Markdown:
Output location:
blog-posts/<topic-slug>.mdblog-posts/openshift-pipelines-tutorial.md