mcpField
A
app-store-distribution-readiness

app-store-distribution-readiness

github.com/sylphxaiDevelopment154 installsUpdated today
Repository

About app-store-distribution-readiness

app-store-distribution-readiness is a skill for preparing software for distribution channels. It maps channel requirements, platform integrations, launch blockers, review risks, and the owners and evidence needed for release.

Key features

  1. 01Identifies product type and channels
  2. 02Maps channel-specific readiness requirements
  3. 03Checks OS integration requirements
  4. 04Reviews subscription disclosures and states
  5. 05Produces blockers, risks, and release checklist

Use cases

  1. 01Preparing an app for store submission
  2. 02Assessing platform permissions and update needs
  3. 03Reviewing subscription purchase and restore readiness
  4. 04Assigning evidence and owners for launch tasks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill app-store-distribution-readiness

After installing, type/app-store-distribution-readinessin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/distribution-channel-matrix.md

Details

From the project README

App Store Distribution Readiness

Use this skill to prepare software for real-world distribution channels, not just a local build.

Workflow

  1. Identify product type and target channels.
  2. Read references/distribution-channel-matrix.md.
  3. Build channel-specific readiness: metadata, screenshots, payments, privacy, testing, review, release, support.
  4. Identify OS integration requirements: permissions, notifications, storage, backup, update, file associations, startup behavior.
  5. For subscription apps, map subscription disclosures, restore/refund/revoke states, server entitlement truth, reviewer evidence, and support ownership before submission.
  6. Produce launch blockers, review risks, release checklist, and owner/evidence map.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not submit subscription apps without exact price, duration, renewal, trial end, cancellation, restore, and refund/support wording matched across app, store metadata, and screenshots.
  • Do not treat local client state as entitlement truth; subscription entitlement must reconcile with App Store / Play events and server validation.
  • Do not rely on store review notes alone; attach test accounts, sandbox products, reviewer steps, screenshots, support URLs, privacy evidence, and owner sign-off.
  • Do not roll out broadly until crash, purchase, restore, refund/revoke, notification permission, and support-contact telemetry are readable.

Output format

Channels:
Product type:

Readiness matrix:
- <channel> — metadata, policy, payments, testing, release, support

OS/platform details:
- <detail>

Subscription and entitlement evidence:
- <item> -> owner, proof link/artifact

Review package:
- Apple:
- Google:

Launch blockers:
- <blocker and owner>

Comments

Markdown supported