asc-wall-submit
Submit or update Wall of Apps entries via App-Store-Connect-CLI with dry-run preview and confirmation flow.
Works with
What it does
Supports two submission paths: standard App Store flow using app ID, or manual flow using TestFlight link and app name
Includes dry-run mode to preview changes before applying with --confirm flag
Generates PR-based submissions that modify docs/wall-of-apps.json with built-in guardrails against unrelated entry changes
Run commands from the App-Store-Connect-CLI repository roo
Installation Guide
How to use asc-wall-submit on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your machine
- ›Node.js 16+ with npm — verify with
node --version - ›Active project directory where you want to add
asc-wall-submit
Run the install command
Execute the skills CLI command in your project's root directory to begin installation:
Fetches asc-wall-submit from rudrankriyam/app-store-connect-cli-skills and configures it for Cursor.
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate asc-wall-submit. Access via /asc-wall-submit in your agent's command palette.
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Documentation
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:
appID - Manual/pre-release flow:
linkplusname
Submission workflow
- Run commands from the
App-Store-Connect-CLIrepository root. - 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
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale