Asc Wall Submit
Add or update your iOS app on the App-Store-Connect-CLI Wall of Apps via dry-run then confirmed `asc apps wall submit`.
Overview
asc-wall-submit is an agent skill for the Launch phase that submits or updates a Wall of Apps entry using `asc apps wall submit` with dry-run and confirmed apply.
Install
npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-wall-submitWhat is this skill?
- Two input paths: App Store `app` ID or manual `link` plus `name` for TestFlight/pre-release
- Mandatory dry-run preview before `--confirm` apply
- Changes limited to `docs/wall-of-apps.json` via PR plan—no unrelated entry edits
- Commands run from App-Store-Connect-CLI repository root
- Guardrails: fix invalid inputs and rerun; PR-based intake unless maintainers define issues
- 4-step submission workflow: repo root, dry-run, --confirm apply, review PR plan
Adoption & trust: 838 installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want your iOS app on the ASC CLI Wall of Apps but are unsure of the exact flags, repo root, and PR-safe submission flow.
Who is it for?
Solo iOS devs already using App-Store-Connect-CLI who want Wall of Apps visibility for a live app ID or TestFlight link.
Skip if: Android listings, full App Store Connect metadata overhauls, or issue-only intake when your fork does not use the PR workflow.
When should I use this skill?
User says submit to wall of apps, add my app to the wall, or wall-of-apps.
What do I get? / Deliverables
You run previewed CLI commands and land a focused PR updating docs/wall-of-apps.json without corrupting neighboring entries.
- Dry-run output reviewed
- PR changing docs/wall-of-apps.json for one wall entry
Recommended Skills
Journey fit
Wall of Apps is a public discovery surface for shipped or beta iOS apps—canonical Launch → distribution. Submission is PR-based marketing visibility in the ASC CLI ecosystem, not store metadata editing or ASO keyword work.
How it compares
Single-purpose ASC CLI wall submit workflow—not App Store Optimization keyword research or generic release-notes writing.
Common Questions / FAQ
Who is asc-wall-submit for?
Indie iOS builders using rudrankriyam’s App-Store-Connect-CLI who want a documented dry-run and confirm path onto the Wall of Apps.
When should I use asc-wall-submit?
At Launch when you are ready to publicize a shipped App Store app or a pre-release TestFlight link on the community wall.
Is asc-wall-submit safe to install?
Review the Security Audits panel on this page; the skill runs local CLI and git operations against your clone—confirm repo and credentials yourself.
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`