Automated summary
This skill walks through the `asc apps wall submit` subcommand of the App-Store-Connect-CLI repository to add or update a Wall of Apps entry.
Strengths
- Covers both supported input paths: an App Store app ID, or a TestFlight link paired with a name
- Enforces a `--dry-run` preview before applying with `--confirm`, reducing accidental changes
- States clear guardrails: leave unrelated entries in `docs/wall-of-apps.json` alone and keep intake PR-based
- Gives exact copy-ready commands, including for non-App-Store entries
Limitations
- Tightly coupled to the App-Store-Connect-CLI repo and its `asc` command; not reusable elsewhere
- Assumes the user is at the repository root with the CLI already set up
- Does not describe what an entry's fields should contain or how maintainers review the resulting PR
Use it when someone wants to add or refresh their app in the App-Store-Connect-CLI Wall of Apps through the `asc` command.
Don't use it to submit an app to the App Store, manage App Store Connect listings, or work in a different repository.
Security analysis
SafeThe skill only documents invoking a first-party CLI (`asc apps wall submit`) with dry-run and confirmation flags, plus review of a docs JSON file. It contains no destructive commands, credential handling, network exfiltration, obfuscated payloads, or safety-disabling instructions.
No concerns found
How this analysis is madeExamples
Submit my app 1234567890 to the wall of apps, preview it first with a dry run.Add my TestFlight beta to the wall of apps: https://testflight.apple.com/join/ABCDEFG, name it "My Beta App".Update my app's wall-of-apps entry using the asc CLI and show me the PR plan before confirming.name: asc-wall-submit
description: Submit or update a Wall of Apps entry in the App-Store-Connect-CLI repository using asc apps wall submit. Use when the user says "submit to wall of apps", "add my app to the wall", or "wall-of-apps".
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
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/submit-to-wall-of-apps-ms47vqjf/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/submit-to-wall-of-apps-ms47vqjf' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/submit-to-wall-of-apps-ms47vqjf/download' --output '.skill-downloads/submit-to-wall-of-apps-ms47vqjf/SKILL.md.part' && mv '.skill-downloads/submit-to-wall-of-apps-ms47vqjf/SKILL.md.part' '.skill-downloads/submit-to-wall-of-apps-ms47vqjf/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/submit-to-wall-of-apps-ms47vqjf/SKILL.md' && test -s '.skill-downloads/submit-to-wall-of-apps-ms47vqjf/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/asc-wall-submit' && cp -R '.skill-downloads/submit-to-wall-of-apps-ms47vqjf' '.claude/skills/asc-wall-submit'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/submit-to-wall-of-apps-ms47vqjf'openskills read 'submit-to-wall-of-apps-ms47vqjf'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/submit-to-wall-of-apps-ms47vqjf/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.