← Back to Skills Marketplace
rudrankriyam

ASC Release Flow

by rudrankriyam · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
1947
Downloads
1
Stars
6
Active Installs
1
Versions
Install in OpenClaw
/install asc-release-flow
Description
End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store.
README (SKILL.md)

Release flow (TestFlight and App Store)

Use this skill when you need to get a new build into TestFlight or submit to the App Store.

Preconditions

  • Ensure credentials are set (asc auth login or ASC_* env vars).
  • Use a new build number for each upload.
  • Prefer ASC_APP_ID or pass --app explicitly.

Preferred end-to-end commands

  • TestFlight:
    • asc publish testflight --app \x3CAPP_ID> --ipa \x3CPATH> --group \x3CGROUP_ID>[,\x3CGROUP_ID>]
    • Optional: --wait, --notify, --platform, --poll-interval, --timeout
  • App Store:
    • asc publish appstore --app \x3CAPP_ID> --ipa \x3CPATH> --version \x3CVERSION>
    • Optional: --wait, --submit --confirm, --platform, --poll-interval, --timeout

Manual sequence (when you need more control)

  1. Upload the build:
    • asc builds upload --app \x3CAPP_ID> --ipa \x3CPATH>
  2. Find the build ID if needed:
    • asc builds latest --app \x3CAPP_ID> [--version \x3CVERSION>] [--platform \x3CPLATFORM>]
  3. TestFlight distribution:
    • asc builds add-groups --build \x3CBUILD_ID> --group \x3CGROUP_ID>[,\x3CGROUP_ID>]
  4. App Store attach + submit:
    • asc versions attach-build --version-id \x3CVERSION_ID> --build \x3CBUILD_ID>
    • asc submit create --app \x3CAPP_ID> --version \x3CVERSION> --build \x3CBUILD_ID> --confirm
  5. Check or cancel submission:
    • asc submit status --id \x3CSUBMISSION_ID> or --version-id \x3CVERSION_ID>
    • asc submit cancel --id \x3CSUBMISSION_ID> --confirm

Notes

  • Always use --help to verify flags for the exact command.
  • Use --output table / --output markdown for human-readable output; default is JSON.
Usage Guidance
This skill appears to be a legitimate App Store Connect release flow, but its metadata omits important requirements. Before installing or invoking it: 1) Verify you have the asc CLI installed and that the agent will not read or transmit secrets you don't want shared. 2) Confirm which ASC_* environment variables are required (e.g., API key ID, issuer ID, private key) and prefer using short-lived or scoped credentials. 3) Only run uploads from a trusted environment and double-check the skill source/owner (no homepage provided). 4) If you plan to allow autonomous invocation, consider the blast radius since uploads and submissions will use your App Store credentials. If anything is unclear, request the skill author add explicit required env vars and documentation before use.
Capability Analysis
Type: OpenClaw Skill Name: asc-release-flow Version: 1.0.0 The skill bundle provides instructions for an AI agent to use the `asc` command-line tool for Apple App Store Connect release workflows. All commands listed in `SKILL.md` are standard operations for uploading builds, distributing to TestFlight, and submitting to the App Store. There is no evidence of prompt injection, data exfiltration, malicious execution, persistence mechanisms, or obfuscation. The requirement for `ASC_*` environment variables is for the legitimate operation of the `asc` tool, not for exfiltration.
Capability Assessment
⚠ Purpose & Capability
The name/description match the instructions (App Store Connect release flows). However the skill metadata declares no required binaries or env vars while the runtime instructions clearly assume the 'asc' CLI is available and that Apple credentials (asc auth or ASC_* env vars, ASC_APP_ID) are provided. The missing declarations are disproportionate to the stated purpose.
⚠ Instruction Scope
SKILL.md instructs the agent to run asc commands that upload IPAs, attach builds, and submit apps — actions that require access to credentials and local IPA files. The instructions mention ASC_* env vars and using 'asc auth login' but those env vars are not declared. Otherwise the instructions stay within App Store Connect scope and do not ask to exfiltrate unrelated files or send data to unexpected endpoints.
✓ Install Mechanism
This is an instruction-only skill with no install spec and no code files, which is low-risk from an installation perspective. There is nothing being downloaded or written by an installer.
⚠ Credentials
The SKILL.md references sensitive environment variables (ASC_* and ASC_APP_ID) and implies the need for Apple credentials, but requires.env and primary credential fields are empty. That mismatch is a red flag: the skill will need secrets to operate but doesn't declare them or explain which specific variables are required.
✓ Persistence & Privilege
The skill is not marked always:true and does not request any persistent system-wide privileges. Autonomous invocation is allowed (platform default) but there is no indication the skill modifies other skills or system settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install asc-release-flow
  3. After installation, invoke the skill by name or use /asc-release-flow
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
asc-release-flow 1.0.0 - Initial release introducing end-to-end workflows for distributing builds to TestFlight and the App Store using asc CLI commands. - Supports both streamlined and manual release flows, with detailed step-by-step instructions. - Includes preconditions for credentials, build numbering, and app identification. - Documents recommended commands and important optional flags for tailored automation. - Provides tips for checking command usage and output formatting.
Metadata
Slug asc-release-flow
Version 1.0.0
License —
All-time Installs 6
Active Installs 6
Total Versions 1
Frequently Asked Questions

What is ASC Release Flow?

End-to-end release workflows for TestFlight and App Store using asc publish, builds, versions, and submit commands. Use when asked to upload a build, distribute to TestFlight, or submit to App Store. It is an AI Agent Skill for Claude Code / OpenClaw, with 1947 downloads so far.

How do I install ASC Release Flow?

Run "/install asc-release-flow" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is ASC Release Flow free?

Yes, ASC Release Flow is completely free (open-source). You can download, install and use it at no cost.

Which platforms does ASC Release Flow support?

ASC Release Flow is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created ASC Release Flow?

It is built and maintained by rudrankriyam (@rudrankriyam); the current version is v1.0.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments