Back to Skills

asc-workflow

Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.

841stars46forksUpdated 6/4/2026

Security Assessment

Low Risk(80/100)

Detected risks:

Sensitive File Access([SKILL.md] .env)
Security Score80/100

About asc-workflow

The asc-workflow skill provides a structured way to define, validate, execute, resume, and audit repository-local automation workflows using the `asc workflow` command set and a `.asc/workflow.json` configuration file. It is designed to support multi-step automation processes that resemble lane-style workflows, enabling teams to organize complex operational tasks into reusable workflow definitions. The skill helps ensure workflow consistency by validating configuration structure and references before execution, while maintaining machine-readable JSON output on stdout and streaming step execution details to stderr.

Key capabilities include workflow validation, workflow discovery, dry-run execution previews, workflow execution, and recovery through resume functionality. Workflows are defined in JSON or JSONC format and support top-level lifecycle hooks such as `before_all`, `after_all`, and `error`. Individual steps can execute shell commands, invoke sub-workflows, apply conditional execution rules, override environment variables, and extract structured outputs from JSON-producing commands. The skill also supports runtime parameters, environment variable precedence rules, persisted workflow outputs, and conditional step execution based on workflow variables or environment settings.

This skill is intended for developers, release engineers, CI/CD operators, and teams managing repeatable automation tasks within a repository. Common use cases include release orchestration, TestFlight distribution workflows, build management, validation pipelines, and multi-step operational processes that require reusable execution logic, parameterization, and failure recovery. It is especially useful when workflow state, outputs, and execution history need to be preserved across runs and resumed after recoverable failures.

FAQ

How do I validate a workflow before running it?

Use `asc workflow validate` to check workflow structure and references before execution.

Can I preview workflow execution without making changes?

Yes. Use `asc workflow run --dry-run <workflow-name>` along with any required parameters to preview execution.

Can a failed workflow be resumed?

Yes. Recoverable workflow runs can be resumed using `asc workflow run <name> --resume <run-id>`, which reuses the saved workflow state, parameters, and outputs.

What file format is supported for workflow definitions?

Workflow definitions are stored in `.asc/workflow.json` by default, and JSONC comments are supported.

Are outputs available from all step types?

No. Outputs can only be declared on `run` steps that emit JSON to stdout. Workflow-call steps do not support outputs.

Install asc-workflow

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill