agentleFS
Sign inStart free
VelimirMuellerVelimirMueller/ai-development-skills/skills/swift/asc-wall-submit/SKILL.md

asc-wall-submit

Skill7 starsChanged 16 days agoMITView on GitHub

Use when the user says "submit to wall of apps", "add my app to the wall", or "wall-of-apps". Submit or update a Wall of Apps entry in the App-Store-Connect-CLI repository using asc apps wall submit.

6 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 4 are common, 0 are distinctive, and 2 are very specific to this project.

  • 4

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill to add or update a Wall of Apps entry with the built-in CLI flow.

    line 8
  2. Common:

    Use one of these input paths:

    line 18
  3. Very specific:

    Run commands from the App-Store-Connect-CLI repository root.

    line 25
  4. Very specific:

    Do not modify unrelated entries in docs/wall-of-apps.json.

    line 36
  5. Common:

    If submission fails due to invalid input, fix the inputs and rerun the CLI command.

    line 37
  6. Common:

    Keep submission path PR-based unless maintainers define an issue-based intake flow.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free