asc-release-flow

What This Skill Does

The asc-release-flow skill is a powerful automation utility for OpenClaw that streamlines the complex lifecycle of iOS application releases. It acts as an interface for App Store Connect, allowing users to programmatically handle build uploads, TestFlight distribution, and formal App Store submission processes. By abstracting the repetitive command-line interactions required by the asc utility, this skill ensures that release workflows are consistent, repeatable, and less prone to manual error.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/rudrankriyam/asc-release-flow

Ensure that you have the asc CLI tool installed and configured with valid authentication credentials (either via asc auth login or by exporting ASC_* environment variables) before attempting to run these commands.

Use Cases

This skill is ideal for developers and CI/CD engineers looking to automate their release cadence. Common scenarios include:

• Automated Nightly Builds: Pushing fresh builds to internal QA teams via TestFlight without manual intervention.
• Production Releases: Initiating the submission process to App Store Review immediately after a build is validated.
• Hotfix Distribution: Rapidly deploying critical patches by combining build upload and distribution steps into a single request.
• Environment Syncing: Using the manual sequence commands to attach specific builds to designated version tracks when granular control is required.

Example Prompts

1. "Upload the build at ./builds/release.ipa to TestFlight for app ID 12345678 and notify the testers in the 'Beta-Group'."
2. "Please publish the build from the latest version to the App Store for app 12345678 and submit it for review automatically."
3. "Can you check the current submission status for the latest version of my application?"

Tips & Limitations

• Preconditions: Always verify your App Store Connect credentials are active before execution. Failures in authentication are the most common cause of workflow interruptions.
• Build Numbers: The App Store requires a unique build number for every upload. Ensure your CI system increments these numbers before triggering the skill.
• Output Format: By default, the skill returns JSON. If you are interacting via the chat interface, append --output markdown to your command to receive a human-readable summary.
• Safety: Always use the --wait flag for long-running processes like App Store submission to ensure the agent reports final success or failure rather than just the initiation of the task.