argo-workflows

Author, lint, and debug Argo Workflows and WorkflowTemplates for Kubernetes CI pipelines.

11|9|Updated May 25, 2026
One-click install
npx skills add https://github.com/projectbluefin/lab --skill argo-workflows-projectbluefin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: argo-workflows
Source: https://github.com/projectbluefin/lab/tree/main/docs/skills/argo-workflows
Command: npx skills add https://github.com/projectbluefin/lab --skill argo-workflows-projectbluefin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing Argo Workflows YAML by hand is error-prone: parameters silently fail to propagate, semaphores deadlock pipelines, and GitOps-managed templates get overwritten by manual kubectl applies. This Skill encodes the lab's hard-won rules so workflows are correct, lint-clean, and safe to run on the cluster. ## Core Features & Use Cases - Template authoring rules: Enforces explicit parameter passing, onExit teardown hooks, resource limits, file-name/metadata-name matching, and ArgoCD ownership conventions for WorkflowTemplates and CronWorkflows. - Pattern reference: Provides proven patterns for image digest pollers, semaphore topology, GitHub Contents API result publishing, DAG conditional chains, and BuildStream remote-execution pipelines. - Failure diagnosis: Catalogs red flags such as hostPID crashes, distroless image shell failures, when/Skipped output traps, and queue starvation from missing activeDeadlineSeconds. - Use Case: When a QA pipeline workflow hangs or a new CronWorkflow needs to be added, load this Skill to check the verification checklist and avoid the documented failure modes before committing. ## Quick Start Use the argo-workflows skill to review my new WorkflowTemplate in argo/workflow-templates/ and tell me what will break before I push it.

Frequently Asked Questions about argo-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pass parameters between Argo Workflow templates?▼

Sub-templates never inherit workflow parameters, so pass every value explicitly through an `arguments:` block at the steps or dag call site. Referencing `{{workflow.parameters.x}}` inside a leaf template without passing it leaves the value unresolved.

Why is my Argo workflow stuck or failing after submission?▼

Common causes include missing `activeDeadlineSeconds` causing queue starvation, semaphores held at workflow scope deadlocking child tasks, distroless images lacking bash, and templates snapshotted at submit time before ArgoCD synced a fix. Verify the live template before resubmitting.

Should I use semaphores or Kubernetes scheduling for VM concurrency in Argo?▼

VM concurrency should rely on the Kubernetes scheduler via virt-launcher memory requests, not workflow-level semaphores. Reserve ConfigMap-backed template-level semaphores for documented cross-workflow contention on scarce node-pinned resources.

Can I kubectl apply WorkflowTemplates managed by ArgoCD?▼

No. Templates under argo/workflow-templates/ are managed by an ArgoCD Application with selfHeal and prune enabled, so manual applies are overwritten within minutes. Commit changes to git and let ArgoCD reconcile, then verify the live template.

How do I publish workflow results back to a GitHub repository?▼

Use curl plus jq against the GitHub Contents API for simple single-file writes, including the file SHA for updates. For complex result merging, clone the repo with a token and run a standalone Python script; never embed heredoc Python inside YAML block scalars.

Why does my Argo script step fail with bash not found?▼

The image is likely distroless, such as registry.k8s.io/kubectl, which contains no shell or core utilities. Switch to a shell-capable image like cgr.dev/chainguard/kubectl:latest-dev or an org-published runner image that carries the required tools.