swamp-workflow

Create, validate, run, and inspect YAML-defined automation workflows via the swamp CLI.

Updated May 27, 2026
One-click install
npx skills add https://github.com/alvagante/swamp-construction-kit --skill swamp-workflow-alvagante
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swamp-workflow
Source: https://github.com/alvagante/swamp-construction-kit/tree/main/.agents/skills/swamp-workflow
Command: npx skills add https://github.com/alvagante/swamp-construction-kit --skill swamp-workflow-alvagante

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multi-step automation across models, scripts, and services requires manual orchestration, dependency tracking, and error handling. This Skill lets you define jobs and steps in YAML, wire them together with dependency conditions, validate the DAG, execute runs, and inspect run history and logs through the swamp CLI. ## Core Features & Use Cases - Workflow lifecycle management: Search, create, edit, validate, evaluate, run, and delete workflows, with auto-assigned IDs and schema-first scaffolding. - Dependency orchestration: Define job and step dependencies with trigger conditions, forEach iteration, concurrency limits, allow-failure steps, and nested workflow calls (max depth 10). - Run observability: Query run history, fetch the latest run, and view per-step logs for debugging failures. - Use Case: Build a deploy pipeline where a build job compiles code, a deploy job runs only on success with environment inputs, and a scheduled cron trigger re-runs the workflow automatically via swamp serve. ## Quick Start Ask the AI to create a new swamp workflow named my-deploy, add build and deploy jobs to the generated YAML, validate it, and run it with an environment input.

Frequently Asked Questions about swamp-workflow

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

FAQPage Schema
How do I create a workflow with the swamp CLI?▼

Run `swamp workflow create <name> --json`, which returns an auto-assigned ID and a YAML file path. Edit that file to add jobs and steps, then validate with `swamp workflow validate <name> --json` before running. Never generate IDs manually or write workflow YAML from scratch.

How do I run a workflow with input parameters?▼

Pass inputs with `swamp workflow run <name> --input key=value`, repeated for multiple values. You can also pipe JSON, NDJSON, or YAML via `--stdin`, use `--input-file` for YAML files, or pass a single JSON object to `--input`.

Can swamp workflows run on a schedule?▼

Yes. Add a `trigger` section with a `schedule` cron expression to the workflow YAML. When `swamp serve` starts, it registers cron entries for all scheduled workflows and watches for file changes, with overlap prevention and no catch-up for missed runs.

How do I debug a failed workflow run?▼

Use `swamp workflow history search --json` to find runs, `swamp workflow history get <workflow> --json` for the latest run details, and `swamp workflow history logs <run> --json` for step-level logs including exit codes.

What are the limitations of nested workflows in swamp?▼

Nested workflows invoked via `type: workflow` tasks have a maximum nesting depth of 10 and cycle detection that rejects A-calls-B-calls-A patterns. Each child workflow run is tracked separately in run history.

How do I stop one failing step from failing the whole workflow?▼

Mark the step with `allowFailure: true`. The step is still recorded as failed, but the failure does not propagate to the job or workflow. Downstream steps with `dependsOn: succeeded` will skip, while `completed` conditions still run.