asc-wall-submit

Submit or update Wall of Apps entries via the App-Store-Connect-CLI generate flow.

4|Updated Dec 8, 2019
One-click install
npx skills add https://github.com/Detrous/dotfiles --skill asc-wall-submit-detrous
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: asc-wall-submit
Source: https://github.com/Detrous/dotfiles/tree/main/claude/skills/asc-wall-submit
Command: npx skills add https://github.com/Detrous/dotfiles --skill asc-wall-submit-detrous

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Submit or update a Wall of Apps entry in the App-Store-Connect-CLI repository using the existing generate-and-PR flow. This avoids adding new CLI surface area and ensures a consistent submission process.

Core Features & Use Cases

  • Add new Wall of Apps entries for new apps and update existing entries with a repeatable, PR-driven workflow.
  • Validate that generated changes include docs/wall-of-apps.json and README snippets, keeping the repository in sync.
  • Provide clear guardrails and inputs so users only proceed when app, link, creator, and platform are present.

Quick Start

Submit or update a Wall of Apps entry by running the generate flow with APP, LINK, CREATOR, and PLATFORM inputs.

Frequently Asked Questions about asc-wall-submit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit a new entry to the Wall of Apps via a pull request?

To submit a Wall of Apps entry, you must provide the app, link, creator, and platform inputs to execute the App-Store-Connect-CLI generate flow. This creates a PR-driven workflow that validates generated docs and README updates for repository synchronization.

What inputs are required to update an existing Wall of Apps entry?

Updating an existing Wall of Apps entry requires four specific inputs: APP, LINK, CREATOR, and PLATFORM. The submission process applies these inputs through the generate flow to ensure the updated entry validates correctly before opening a pull request.

How does the PR-driven workflow keep the Wall of Apps repository in sync?

The PR-driven workflow keeps the repository in sync by validating that generated changes include both the wall-of-apps.json file and README snippets. This ensures all new app submissions or modifications maintain consistent documentation across the repository.

Can I use this submission process without adding new CLI surface area?

Yes, this submission process leverages the existing generate-and-PR flow specifically to avoid adding new CLI surface area. It provides a repeatable workflow for adding or modifying Wall of Apps entries while maintaining the current CLI structure.

What happens if I try to submit a Wall of Apps entry without all required inputs?

The submission process enforces clear guardrails and only proceeds when app, link, creator, and platform inputs are present. If any required input is missing, the generate flow will halt to prevent invalid entries from entering the pull request validation.

Is this Wall of Apps submission method suitable for bulk app updates?

This method is designed for adding new apps or updating existing entries through a repeatable, PR-driven workflow. It validates generated docs and README snippets for each submission, making it better suited for individual entry updates rather than bulk modifications.