Skip to content
FunCoding

Search

Search docs, Skills and MCP

asc-wall-submit

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".

DevOps 与云1.1kskills/asc-wall-submit/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/rorkai/app-store-connect-cli-skills/asc-wall-submit/install.md ,按里面的步骤帮我安装这个 Skill。

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

Similar Skills

shipping-and-launch
addyosmani/agent-skills103k

shipping-and-launch

Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

DevOps & cloud

publish
code-yeongyu/oh-my-openagent70k

publish

Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: <patch|minor|major|explicit-semver>. Triggers: publish, release, deploy, npm publish.

DevOps & cloud

acceptance-orchestrator
sickn33/agentic-awesome-skills47k

acceptance-orchestrator

Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.

DevOps & cloud

event-store-design
wshobson/agents40k

event-store-design

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

DevOps & cloud

arize-ai-provider-integration
github/awesome-copilot40k

arize-ai-provider-integration

Creates, reads, updates, and deletes Arize AI integrations that store LLM provider credentials used by evaluators and other Arize features. Supports any LLM provider (e.g. OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, Vertex AI, Gemini, NVIDIA NIM). Use when the user mentions AI integration, LLM provider credentials, create integration, list integrations, update credentials, delete integration, or connecting an LLM provider to Arize.

DevOps & cloud

appinsights-instrumentation
github/awesome-copilot40k

appinsights-instrumentation

Instrument a webapp to send useful telemetry data to Azure App Insights

DevOps & cloud