WorkflowTemplate foundations: versioned, reusable automation building blocks with parameter contracts, error handling, volumes, and RBAC for production workflows.
Creates reusable, versioned Argo WorkflowTemplates with parameter contracts, error handling, volumes, and RBAC for production workflows. Use when you need to extract shared workflow logic to avoid duplication across triggers and maintain a single source of truth.
/plugin marketplace add adaptive-enforcement-lab/claude-skills/plugin install patterns@ael-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
WorkflowTemplates are the foundation of reusable automation in Argo Workflows. Rather than defining workflows inline or copying YAML between projects, WorkflowTemplates let you create versioned, tested building blocks that can be invoked by events, schedules, or other workflows.
Start Simple
Begin with basic structure and retry strategy. Add init containers and custom volumes only when the simpler approach proves insufficient.
The naive approach to workflow automation is embedding all logic directly in the triggering resource: a Sensor, CronWorkflow, or manual submission. This works for simple cases but quickly becomes unmaintainable.
Consider a documentation build pipeline. The first version might be a simple script triggered by a GitHub push. But then you need the same build for scheduled refreshes. And manual triggers for debugging. And a "full rebuild" variant that processes all repositories instead of just the changed one.
Without WorkflowTemplates, you end up with four copies of nearly identical YAML. When you fix a bug or add a feature, you update one copy and forget the others. Drift accumulates. Debugging becomes archaeology.
WorkflowTemplates solve this by extracting the workflow logic into a standalone resource. Triggers reference the template by name. Updates happen in one place. The template becomes a contract: "give me these parameters, and I'll do this work."
| Pattern | Description |
|---|---|
| Basic Structure | Fundamental WorkflowTemplate anatomy and parameter handling |
| Retry Strategy | Error handling with exponential backoff |
| Init Containers | Multi-stage pipelines with sequential setup |
| Volume Patterns | Persistent storage, secrets, and configuration |
| RBAC Configuration | Security and permission management |
Start Simple
Begin with basic structure and retry strategy. Add init containers and custom volumes only when the simpler approach proves insufficient.
| Pattern | Description |
|---|---|
| Basic Structure | Fundamental WorkflowTemplate anatomy and parameter handling |
| Retry Strategy | Error handling with exponential backoff |
| Init Containers | Multi-stage pipelines with sequential setup |
| Volume Patterns | Persistent storage, secrets, and configuration |
| RBAC Configuration | Security and permission management |
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.