argo-workflows
Skill2 starsChanged 28 days agoApache-2.0View on GitHub
Architects, defines, and executes Kubernetes-native DAG workflows, artifact passing, container steps, retry strategies, and CronWorkflows using Argo Workflows.
In this repository108 other files it gives its agents.
- AGENTS.mdAGENTS.md
- everything-gemini-maintainerSkill
- adversarial-fuzz-generatorSkill
- agent-evalsSkill
- ai-first-engineeringSkill
- alloydb-omni-vectorSkill
- apache-kafka-streamsSkill
- api-craftsmanSkill
- architecture-designerSkill
- argon-3d-game-engineSkill
- argon-3d-scene-architectSkill
- argon-procedural-asset-generatorSkill
- argon-visual-critique-loopSkill
- autonomous-incident-healerSkill
- axum-web-serviceSkill
- bigquery-vector-searchSkill
- browser-qa-testerSkill
- chromadb-vector-storeSkill
- cilium-ebpf-networkingSkill
- clickhouse-analyticsSkill
- cloud-deploy-canarySkill
- cloudflare-r2-object-storageSkill
- cloudflare-workersSkill
- cloud-run-agentsSkill
- context-cachingSkill
- context-distillation-compressorSkill
- context-warmerSkill
- continuous-learningSkill
- cost-oracle-finopsSkill
- cross-repo-swarm-syncSkill
- cve-remediation-orchestratorSkill
- database-architectSkill
- dataproc-spark-analyticsSkill
- dbt-transformationSkill
- debezium-cdcSkill
- devops-pipelineSkill
- distributed-rate-limitingSkill
- docker-compose-orchestratorSkill
- duckdb-local-olapSkill
- dynamic-thinking-allocationSkill
- ebpf-microvm-sandboxSkill
- ebpf-sandbox-enforcerSkill
- elephant-goldfish-modelSkill
- envoy-ai-gatewaySkill
- ephemeral-swarm-orchestratorSkill
- fastapi-productionSkill
- fullstack-nextjsSkill
- game-audio-synthesizerSkill
- game-studioSkill
- gemini-function-callingSkill
- gemini-groundingSkill
- gemini-live-audio-transcriberSkill
- gemini-live-multimodalSkill
- gemini-live-screen-visionSkill
- gemini-multimodalSkill
- genetic-prompt-cross-pollinatorSkill
- git-craftsmanSkill
- github-opsSkill
- google-axSkill
- google-flow-orchestratorSkill
- The first 60 shown.
The file
Files
Argo Workflows & Kubernetes-Native DAG Orchestration
This skill provides operational patterns for designing, testing, and deploying Kubernetes-native workflow orchestration via Argo Workflows, powering parallel data pipelines, machine learning training graphs, and automated batch processing.
⚡ Core Architecture & CRDs
Workflow: Ephemeral, single-run execution specification.WorkflowTemplate: Reusable workflow definitions stored inside the Kubernetes cluster.CronWorkflow: Time-triggered recurring workflows (cron schedule).- DAGs vs Steps: DAGs declare declarative dependency graphs (
dependencies: [taskA, taskB]), whereas Steps declare sequential matrix execution. - Artifacts: Input/output binary blobs, model weights, and logs backed by S3, GCS, or MinIO.
🏗️ Production DAG Workflow Specification (workflow-dag.yaml)
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
generateName: ml-pipeline-dag-
namespace: argo
spec:
entrypoint: ml-pipeline
serviceAccountName: argo-workflow-executor
shutdown: "Stop" # Graceful termination support
onExit: pipeline-cleanup-handler
templates:
- name: ml-pipeline
dag:
tasks:
- name: ingest-data
template: data-ingestion-step
arguments:
parameters:
- name: dataset-version
value: "v2026.10"
- name: validate-schema
dependencies: [ingest-data]
template: schema-validator-step
arguments:
artifacts:
- name: raw-dataset
from: "{{tasks.ingest-data.outputs.artifacts.dataset}}"
- name: train-model
dependencies: [validate-schema]
template: model-training-step
arguments:
artifacts:
- name: validated-data
from: "{{tasks.validate-schema.outputs.artifacts.clean-dataset}}"
- name: data-ingestion-step
inputs:
parameters:
- name: dataset-version
container:
image: python:3.11-slim
command: [python, -c]
args: ["import json; open('/tmp/dataset.csv', 'w').write('id,score\\n1,0.95\\n')"]
outputs:
artifacts:
- name: dataset
path: /tmp/dataset.csv
- name: schema-validator-step
inputs:
artifacts:
- name: raw-dataset
path: /inputs/dataset.csv
container:
image: python:3.11-slim
command: [python, -c]
args: ["import shutil; shutil.copy('/inputs/dataset.csv', '/outputs/clean.csv')"]
outputs:
artifacts:
- name: clean-dataset
path: /outputs/clean.csv
- name: model-training-step
inputs:
artifacts:
- name: validated-data
path: /data/clean.csv
retryStrategy:
limit: "3"
retryPolicy: "Always"
backoff:
duration: "10s"
factor: 2
container:
image: python:3.11-slim
resources:
requests:
cpu: "2"
memory: "4Gi"
limits:
cpu: "4"
memory: "8Gi"
command: [python, -c]
args: ["print('Model trained successfully')"]
- name: pipeline-cleanup-handler
container:
image: alpine:latest
command: [sh, -c]
args: ["echo Pipeline finished with status: {{workflow.status}}"]🛠️ CLI Operations & Debugging Runbook
# Submit a workflow and follow real-time execution
argo submit --watch workflow-dag.yaml -n argo
# List active and completed workflows
argo list -n argo
# Stream logs of a specific DAG task step
argo logs @latest -c main -n argo
# Resubmit a failed workflow with memoized step caching
argo resubmit --memoized @latest -n argo
# Terminate or suspend a runaway workflow
argo terminate @latest -n argo🛡️ Best Practices & Anti-Patterns
| Category | ❌ Anti-Pattern | ✅ Production Best Practice |
| Artifacts | Storing giant datasets directly inside pod disk | Use external artifact repositories (S3 / GCS) with lifecycle policies |
| Retries | Unbounded retries without exponential backoff | Set explicit retryStrategy.limit and exponential backoff.factor |
| Resources | Omitting CPU/Memory resource constraints | Always specify requests and limits to prevent node OOM crashes |
| Secrets | Hardcoding API keys or database URLs in YAML | Reference Kubernetes Secrets via env.valueFrom.secretKeyRef |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

