Orchestrieren Sie die iOS-Screenshot-Automatisierung mit xcodebuild/simctl für Build-und-Run, AXe für UI-Aktionen, JSON-Einstellungen und -Plan-Dateien, Koubou-basierter Rahmung („asc screenshots frame“) und Screenshot-Upload („asc screenshots upload“).
Dieses Skill orchestriert eine vollständige iOS-Screenshot-Automatisierungspipeline. Es verwendet xcodebuild und simctl, um Apps zu bauen und auf Simulatoren zu starten. Mit dem AXe-Tool werden UI-Aktionen (Tippen, Wischen) automatisiert, um verschiedene Screenshots aus verschiedenen Zuständen der App zu erfassen. Die Konfiguration erfolgt über JSON-Einstellungs- und -Plan-Dateien, die die gewünschten Screenshots definieren. Nach der Erfassung können Screenshots mit dem Koubou-basierten Befehl `asc screenshots frame` gerahmt werden, um sie für den App Store vorzubereiten. Abschließend können die gerahmten Screenshots mit dem Befehl `asc screenshots upload` hochgeladen werden. Das Skill ist nützlich für Entwickler, die wiederkehrende Screenshot-Erstellungs-Workflows automatisieren möchten, und es unterstützt typische CI/CD-Pipelines sowie manuelle Ausführung. Es ist speziell für iOS-Entwickler konzipiert, die mit xcodebuild, simctl und Befehlszeilenwerkzeugen vertraut sind.
npx skills add https://github.com/rudrankriyam/app-store-connect-cli-skills/tree/main/skills/asc-shots-pipelineOrchestrieren Sie die iOS-Screenshot-Automatisierung mit xcodebuild/simctl für Build-und-Run, AXe für UI-Aktionen, JSON-Einstellungen und -Plan-Dateien, Koubou-basierter Rahmung (asc screenshots frame) und Screenshot-Upload (asc screenshots upload). Verwenden Sie dieses Skill, wenn Benutzer nach automatisierter Screenshot-Erfassung, AXe-gesteuerten Simulator-Abläufen, Rahmenkomposition oder Screenshot-zu-Upload-Pipelines fragen.
This repo contains 20 individual skills — each has its own dedicated page.
Create a new App Store Connect app record via browser automation. Use when there is no public API for app creation and you need an agent to drive the New App form.
Run an offline ASO audit on canonical App Store metadata under `./metadata` and surface keyword gaps using Astro MCP. Use after pulling metadata with `asc metadata pull`.
Track build processing, find latest builds, and clean up old builds with asc. Use when managing build retention or waiting on processing.
Guidance for using asc cli in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.
Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
Archive, export, and notarize macOS apps using xcodebuild and asc. Use when you need to prepare a macOS app for distribution outside the App Store with Developer ID signing and Apple notarization.
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.
Determine whether an app is ready to submit, then drive the current App Store release flow with asc, including validation, staging, review submission, first-time availability, subscriptions, IAP, Game Center, and App Privacy checks.
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
Set up bundle IDs, capabilities, signing certificates, provisioning profiles, and encrypted signing sync with the asc cli. Use when onboarding a new app, rotating signing assets, or sharing them across a team.
Validate App Store submission readiness, submit prepared versions, and monitor review status with current asc commands. Use when shipping or troubleshooting review submissions.
Bulk-localize subscription and in-app purchase display names across all App Store locales using asc. Use when you want to fill in subscription/IAP names for every language without clicking through App Store Connect manually.
Orchestrate TestFlight distribution, groups, testers, and What to Test notes using asc. Use when rolling out betas.
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".
Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under `./metadata`. Optionally pairs with promotional text updates.
Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.
Build, archive, export, upload, and manage Xcode version/build numbers with the current asc xcode helpers before App Store Connect upload or submission. Use when creating an IPA or PKG for upload.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".