asc-workflow

Define, validate, run, and resume repo-local asc workflow automations for TestFlight and App Store releases.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-workflow-dustinober1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: asc-workflow
Source: https://github.com/dustinober1/sundee-fundee-ios/tree/main/SundeeFundeeApp/.agents/skills/asc-workflow
Command: npx skills add https://github.com/dustinober1/sundee-fundee-ios --skill asc-workflow-dustinober1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing multi-step App Store Connect release tasks manually is error-prone and repetitive. This Skill lets you define trusted, version-controlled automation workflows in .asc/workflow.json and execute them reliably with the asc workflow CLI, including validation, dry runs, and resumable failures. ## Core Features & Use Cases - Workflow Authoring & Validation: Define workflows with steps, hooks, env vars, conditionals, and JSON outputs, then validate structure before running. - Safe Execution: Preview runs with --dry-run, execute with runtime params, and resume failed runs by run ID without re-entering parameters. - Release Automation: Chain TestFlight distribution, App Store validation, staging, and review submission into repeatable workflows. - Use Case: You need to distribute the latest iOS build to a TestFlight group. Define a beta workflow that resolves the latest build, lists groups, and conditionally adds the build to a group, then run it with asc workflow run beta. ## Quick Start Ask the assistant to validate the repo's .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> with optional KEY:VALUE or KEY=VALUE params, for example asc workflow run beta BUILD_ID:123 GROUP_ID:grp_abc. Validate first with asc workflow validate and preview with --dry-run before executing.

How do I resume a failed asc workflow run?▼

Use asc workflow run <name> --resume with the run ID from the failed run's JSON result, such as asc workflow run release --resume "release-20260312T120000Z-deadbeef". Do not pass extra KEY:VALUE params; saved params and persisted outputs are reused.

Where is the asc workflow file located and what format does it use?▼

The default path is .asc/workflow.json, overridable with asc workflow run --file ./path/to/workflow.json. It supports JSONC comments, top-level hooks (before_all, after_all, error), and workflow keys like description, private, env, and steps.

How do step outputs work in asc workflows?▼

Run steps can declare an outputs map that extracts values from the command's JSON stdout, referenced later as ${steps.step_name.OUTPUT_NAME}. The command must emit JSON, so pass --output json for asc commands, and output names must be unique across the run graph.

Can I run workflow steps conditionally?▼

Yes, add an "if": "VAR_NAME" field to a step. Truthy values are 1, true, yes, y, and on (case-insensitive), resolved from merged workflow env and params first, then the process environment.

Is it safe to run workflows from untrusted pull requests?▼

No. Treat .asc/workflow.json like code and only run trusted workflow files, since workflows execute shell commands. Avoid running workflows from untrusted PRs with secrets, and keep workflow files in version control.