Asc Wall Submit
Add or update your app on the App-Store-Connect-CLI Wall of Apps using asc apps wall submit with dry-run then confirm.
Overview
asc-wall-submit is an agent skill for the Launch phase that runs the App Store Connect CLI Wall of Apps submission flow with dry-run preview and confirmed PR updates.
Install
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills --skill asc-wall-submitWhat is this skill?
- Standard path: App Store app ID via asc apps wall submit
- Manual/pre-release path: TestFlight link plus display name
- Mandatory dry-run preview before --confirm apply
- PR-based change to docs/wall-of-apps.json without touching unrelated entries
- Guardrails: fix invalid inputs and rerun CLI rather than hand-editing the wall file
- 2 input paths: app ID or link plus name
- 2-step apply: dry-run then --confirm
Adoption & trust: 1.4k 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 ASC CLI Wall of Apps but do not know the exact asc apps wall submit flags, inputs, or guardrails.
Who is it for?
Indie iOS developers already using App-Store-Connect-CLI who want a repeatable wall listing for App Store or TestFlight apps.
Skip if: Android listings, full App Store release automation, or editing wall JSON by hand outside the CLI flow.
When should I use this skill?
User says submit to wall of apps, add my app to the wall, or wall-of-apps; or wants to add/update a Wall of Apps entry.
What do I get? / Deliverables
You produce a validated dry-run plan and a confirmed submission that updates only your Wall of Apps entry via the CLI’s PR workflow.
- Dry-run preview of wall submission
- Confirmed PR plan updating docs/wall-of-apps.json
Recommended Skills
Journey fit
Launch is the right shelf because Wall of Apps is a public distribution showcase tied to App Store or TestFlight visibility, not core app implementation. Distribution fits community wall listings, PR-based docs/wall-of-apps.json updates, and indie discoverability beyond ASO keywords.
How it compares
CLI workflow skill for one community wall—not App Store Connect API metadata management or ASO keyword research.
Common Questions / FAQ
Who is asc-wall-submit for?
Mobile indie builders contributing to the App-Store-Connect-CLI repo who want a scripted Wall of Apps entry with maintainer-friendly PRs.
When should I use asc-wall-submit?
At Launch when you are ready to showcase distribution—after you have an App Store app ID or a TestFlight join link and display name.
Is asc-wall-submit safe to install?
It runs local CLI commands against a known repo path; review the Security Audits panel on this Prism page and confirm you trust the ASC CLI source.
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`