Asc Wall Submit
Submit or update your app on the App-Store-Connect-CLI Wall of Apps with dry-run preview and confirmed PR-based flow.
Overview
asc wall submit is an agent skill for the Launch phase that runs asc apps wall submit to add or update a Wall of Apps entry via dry-run and confirm.
Install
npx skills add https://github.com/rorkai/app-store-connect-cli-skills --skill asc-wall-submitWhat is this skill?
- Two input paths: App Store app ID or manual TestFlight link plus display name
- Mandatory dry-run before --confirm apply
- PR plan review targeting docs/wall-of-apps.json only
- Guardrail: do not edit unrelated wall entries on failure recovery
- 4-step submission workflow with dry-run and --confirm
Adoption & trust: 596 installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want your app on the App-Store-Connect-CLI Wall of Apps but are unsure of the exact CLI flags, dry-run step, and which JSON file the PR will touch.
Who is it for?
Indie iOS devs already in the App-Store-Connect-CLI repo who need a repeatable wall submission without breaking neighboring entries.
Skip if: App Store metadata editing, ASC API automation outside this wall flow, or Android listing distribution.
When should I use this skill?
User says submit to wall of apps, add my app to the wall, or wall-of-apps and needs asc apps wall submit from App-Store-Connect-CLI repo root.
What do I get? / Deliverables
You produce a reviewed, confirm-gated PR that adds or updates only your Wall of Apps row in docs/wall-of-apps.json.
- Dry-run output reviewed
- Confirmed wall submit change and PR plan for docs/wall-of-apps.json
Recommended Skills
Journey fit
Wall of Apps is a distribution and discovery surface for shipped or beta apps, which maps to Launch rather than in-repo Build work. The skill automates a public showcase listing via asc apps wall submit, a classic distribution subphase task.
How it compares
Use for this repo’s Wall of Apps PR workflow—not as a general App Store Connect listing or ASO skill.
Common Questions / FAQ
Who is asc-wall-submit for?
Builders maintaining or contributing to App-Store-Connect-CLI who want a scripted, PR-safe path onto the Wall of Apps.
When should I use asc-wall-submit?
Use it at Launch when you say submit to wall of apps, add my app to the wall, or need the exact asc apps wall submit dry-run and --confirm sequence.
Is asc-wall-submit safe to install?
Check the Security Audits panel on this Prism page; the skill only drives local CLI commands in a cloned repo but still modifies tracked JSON via PR.
SKILL.md
READMESKILL.md - Asc Wall Submit
# asc wall submit Use this skill to add or update a Wall of Apps entry with the built-in CLI flow. ## When to use - User wants to submit an app to the Wall of Apps - User wants to update an existing Wall of Apps entry - User asks for the exact Wall submission flow ## Required inputs Use one of these input paths: - Standard App Store flow: `app` ID - Manual/pre-release flow: `link` plus `name` ## Submission workflow 1. Run commands from the `App-Store-Connect-CLI` repository root. 2. Preview first: - `asc apps wall submit --app "1234567890" --dry-run` - or `asc apps wall submit --link "https://testflight.apple.com/join/ABCDEFG" --name "My Beta App" --dry-run` 3. Apply with confirmation: - `asc apps wall submit --app "1234567890" --confirm` - or `asc apps wall submit --link "https://testflight.apple.com/join/ABCDEFG" --name "My Beta App" --confirm` 4. Review the generated PR plan and resulting change to `docs/wall-of-apps.json`. ## Guardrails - Do not modify unrelated entries in `docs/wall-of-apps.json`. - If submission fails due to invalid input, fix the inputs and rerun the CLI command. - Keep submission path PR-based unless maintainers define an issue-based intake flow. ## Examples Add new app: `asc apps wall submit --app "1234567890" --confirm` Submit a non-App-Store/TestFlight entry: `asc apps wall submit --link "https://testflight.apple.com/join/ABCDEFG" --name "My Beta App" --confirm`