agentleFS
Sign inStart free
moasqmoasq/ios-dev-agent/.agents/skills/asc/SKILL.md

asc

Skill4 starsChanged 6 months agoMITView on GitHub

Use when managing App Store Connect with the asc CLI: authentication, metadata, screenshots, TestFlight, builds, validation, review submission, pricing, subscriptions, signing, analytics, finance, workflows, and Xcode archive/export. Routes narrow tasks to the current asc-* skills and uses asc 1.4.0 command surfaces.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use asc for App Store Connect operations.

    line 8
  2. Distinctive:

    Run these before any ASC workflow:

    line 12
  3. Very specific:

    If commands need an app ID, prefer .agents/config/product.md, .asc/, metadata/app.yaml, or a fresh asc apps list/asc apps info lookup:

    line 20
  4. Distinctive:

    Use the narrowest skill that matches the task:

    line 28
  5. Very specific:

    Do not use removed legacy shortcuts such as submit preflight, submit-create, or release-run.

    line 67
  6. Very specific:

    Prefer --output json --pretty for machine-readable inspection and --output markdown for reports.

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

App Store Connect

Use asc for App Store Connect operations. Current local version target: asc 1.4.0.

First Checks

Run these before any ASC workflow:

asc --version
asc doctor
asc auth status

If commands need an app ID, prefer .agents/config/product.md, .asc/, metadata/app.yaml, or a fresh asc apps list/asc apps info lookup:

  • asc_app_id: <numeric app id>
  • bundle_id: com.example.app
  • primary_locale: en-US

Route To Narrow Skills

Use the narrowest skill that matches the task:

TaskSkill
CLI syntax, flags, output, pagination, authasc-cli-usage
Resolve app/version/build/group/tester IDsasc-id-resolver
Build, archive, export, uploadasc-xcode-build
Signing, bundle IDs, certs, profilesasc-signing-setup
Submission readiness and review statusasc-submission-health
End-to-end release prep/submissionasc-release-flow
TestFlight groups, testers, What to Testasc-testflight-orchestration
Build processing and retentionasc-build-lifecycle
Metadata pull/push/localizationsasc-metadata-sync
YAML metadata source of truthasc-metadata-yaml
What’s New release notesasc-whats-new-writer
Screenshots upload/capture/frameasc-shots-pipeline
Screenshot resizing/size validationasc-screenshot-resize
ASO metadata auditasc-aso-audit
Subscription/IAP localizationasc-subscription-localization
ASC ↔ RevenueCat catalog syncasc-revenuecat-catalog-sync
Regional / PPP pricingasc-ppp-pricing
Crash, feedback, diagnosticsasc-crash-triage
App creation via web UIasc-app-create-ui
macOS notarizationasc-notarization
Repo-local release automationsasc-workflow
Wall of Apps submissionasc-wall-submit

Current Readiness Commands

asc validate is the canonical App Store readiness surface.

asc validate --app "<APP_ID>" --version "1.0" --platform IOS --output markdown
asc validate --app "<APP_ID>" --version "1.0" --platform IOS --strict --output json --pretty
asc validate testflight --app "<APP_ID>" --build "<BUILD_ID>" --output markdown
asc validate iap --app "<APP_ID>" --output markdown
asc validate subscriptions --app "<APP_ID>" --output markdown

Do not use removed legacy shortcuts such as submit preflight, submit-create, or release-run.

Common Operations

asc apps list
asc builds list --app "<APP_ID>"
asc versions list --app "<APP_ID>"
asc metadata pull --app "<APP_ID>" --dir ./metadata
asc screenshots upload --app "<APP_ID>" --version "1.0" --dir ./metadata/screenshots
asc publish testflight --app "<APP_ID>" --build "<BUILD_ID>"
asc publish appstore --app "<APP_ID>" --version "1.0" --submit

Prefer --output json --pretty for machine-readable inspection and --output markdown for reports.

Embedded References

Open these only when needed:

  • reference/cli-reference-1.4.0.md - current command reference from asc docs show reference
  • reference/workflows-1.4.0.md - release, TestFlight, Xcode workflow recipes
  • reference/api-notes-1.4.0.md - App Store Connect API quirks
  • reference/setup-guide.md - credential setup

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