agentleFS
The-Artificer-of-Ciphers-LLCThe-Artificer-of-Ciphers-LLC/skills-from-the-artificer/asc-wall-submit/SKILL.md

asc-wall-submit

Skill6 starsChanged 34 days agoMITView on GitHub

Submit or update a Wall of Apps entry in the App-Store-Connect-CLI repository using the existing generate-and-PR flow. Use when the user says "submit to wall of apps", "add my app to the wall", "wall-of-apps", or asks for make generate app + PR help.

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

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 2 are common, 5 are distinctive, and 2 are very specific to this project.

  • 2

    Common

    Most of the 6 edited versions we read keep these.

  • 5

    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. Distinctive:

    Use this skill to add or update a Wall of Apps entry without introducing new CLI surface area.

    line 8
  2. Distinctive:

    If any value is missing, ask for it first.

    line 25
  3. Very specific:

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

    line 29
  4. Distinctive:

    Verify generated changes include:

    line 32
  5. Distinctive:

    Do not hand-edit the Wall snippet in README.md.

    line 42
  6. Very specific:

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

    line 43
  7. Common:

    If generation fails due to invalid input, fix inputs and rerun the generator.

    line 44
  8. Common:

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

    line 45
  9. Distinctive:

    Update existing app (same app name updates in place):

    line 53

“Common” is measured: kept by at least 6 in 10 of the 6 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 without introducing new CLI surface area.

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

Collect and confirm all fields before running commands:

  • app: app name
  • link: app URL (http/https, usually App Store URL)
  • creator: GitHub handle or creator name
  • platform: comma-separated labels (for example: iOS,macOS)

If any value is missing, ask for it first.

Submission workflow

  1. Run commands from the App-Store-Connect-CLI repository root.
  2. Run: make generate app APP="Your App Name" LINK="https://apps.apple.com/app/id1234567890" CREATOR="your-handle" PLATFORM="iOS,macOS"
  3. Verify generated changes include:
    • docs/wall-of-apps.json
    • README.md
  4. Review diff and confirm:
    • The JSON entry is added or updated correctly.
    • The README wall snippet is regenerated from markers.
  5. Open a focused PR with only the Wall-related generated changes.

Guardrails

  • Do not hand-edit the Wall snippet in README.md.
  • Do not modify unrelated entries in docs/wall-of-apps.json.
  • If generation fails due to invalid input, fix inputs and rerun the generator.
  • Keep submission path PR-based unless maintainers define an issue-based intake flow.

Examples

Add new app:

make generate app APP="My App" LINK="https://apps.apple.com/app/id1234567890" CREATOR="my-handle" PLATFORM="iOS"

Update existing app (same app name updates in place):

make generate app APP="My App" LINK="https://apps.apple.com/app/id1234567890" CREATOR="my-handle" PLATFORM="iOS,macOS"

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.