asc-workflow

Define, validate, run, and resume repo-local asc workflow automations with step outputs.

70|4|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/AlexW00/Zettel --skill asc-workflow-alexw00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-workflow
Source: https://github.com/AlexW00/Zettel/tree/main/.agents/skills/asc-workflow
Command: npx skills add https://github.com/AlexW00/Zettel --skill asc-workflow-alexw00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing multi-step App Store Connect operations like TestFlight distribution and release submission requires running many CLI commands in the right order with the right parameters, which is error-prone and hard to repeat. ## Core Features & Use Cases - Workflow Definition and Validation: Author .asc/workflow.json files with steps, hooks, env vars, and conditionals, then validate them before execution. - Step Outputs and Chaining: Capture JSON output from named run steps and reference values like ${steps.resolve_build.BUILD_ID} in later steps. - Dry-Run, Resume, and Auditing: Preview runs with --dry-run, execute with runtime params, and resume failed runs by run ID without re-entering parameters. - Use Case: Define a beta workflow that resolves the latest build, lists TestFlight groups, and conditionally adds the build to a group, then run it with asc workflow run beta GROUP_ID:grp_abc. ## Quick Start Ask the assistant to validate the .asc/workflow.json file and then dry-run the beta workflow with a build ID and group ID before executing it.

Frequently Asked Questions about asc-workflow

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

FAQPage Schema
How do I run an asc workflow from the command line?▼

Run `asc workflow run <name> KEY:VALUE` after validating with `asc workflow validate`. Use `--dry-run` to preview execution and `--file` to override the default `.asc/workflow.json` path.

How do I pass outputs between steps in an asc workflow?▼

Declare an `outputs` map on a named run step whose command emits JSON on stdout, using JSONPath expressions like `$.data.id`. Reference values in later steps with `${steps.step_name.OUTPUT_NAME}`.

Can I resume a failed asc workflow run?▼

Yes, use `asc workflow run <name> --resume <run-id>` with the run ID from the failed run's JSON result. Do not pass extra KEY:VALUE params, since saved params and persisted outputs are reused.

How do conditional steps work in asc workflow files?▼

Add `"if": "VAR_NAME"` to a step. The step runs when the variable is truthy (`1`, `true`, `yes`, `y`, `on`, case-insensitive), resolved from merged workflow env and params first, then the process environment.

What are the limitations of workflow step outputs?▼

Outputs are only allowed on run steps, not workflow-call steps, and the step must have a reference-safe unique name. Persisted outputs are stored in run state, so secrets must never be mapped into outputs.