install
source · Clone the upstream repo
git clone https://github.com/ComeOnOliver/skillshub
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ComeOnOliver/skillshub "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/rudrankriyam/app-store-connect-cli-skills/asc-wall-submit" ~/.claude/skills/comeonoliver-skillshub-asc-wall-submit && rm -rf "$T"
manifest:
skills/rudrankriyam/app-store-connect-cli-skills/asc-wall-submit/SKILL.mdsource content
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:
IDapp - Manual/pre-release flow:
pluslinkname
Submission workflow
- Run commands from the
repository root.App-Store-Connect-CLI - 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
- 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
- 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