agentsclimarketplace
Sign in

Store preflight compliance

Skill MaTriXy/StoreReady/skills/store-preflight-compliance

This skill should be used when the user asks to "run a play store and app store checkup", "review mobile app submission readiness", "check Google Play policy compliance", "check Apple App Store compliance", "audit store submission risks", or "prepare a mobile app for store submission".From its SKILL.md

Install
npx -y skills add MaTriXy/StoreReady --skill store-preflight-compliance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, as published. Nobody here has run it

Store Preflight Compliance

Run a full pre-submission compliance checkup for mobile apps targeting Google Play and Apple App Store.

Purpose

Use this skill to produce a release-readiness report without requiring any binary build/install step. Perform static repository checks directly from source files and produce store-specific findings plus manual console review items.

No-Build Workflow

Do not require go build, make build, or tool installation to run this skill.

If the storeready CLI is already available in PATH, it may be used as an optional accelerator. If it is not available, continue with source-only checks.

Step 1: Detect Platform Scope

Identify which store targets are present in the repo:

  • Android indicators: AndroidManifest.xml, build.gradle, build.gradle.kts.
  • Apple indicators: Info.plist, app.json with expo.ios, PrivacyInfo.xcprivacy, iOS project files.

If only one platform is present, review that platform and still include a note that the other platform was not detected.

Step 2: Run Google Play Source Checks

Use the Play checklist in references/play-checklist.md.

At minimum, check:

  • Manifest release flags (debuggable, cleartext traffic, backup behavior).
  • High-risk permissions requiring Play declarations.
  • Gradle release metadata (applicationId, targetSdk, versionCode).
  • Policy-sensitive areas requiring manual Play Console review (Data safety, account deletion, payments disclosures, listing accuracy).

Step 3: Run Apple Source Checks

Use the Apple checklist in references/apple-checklist.md.

At minimum, check:

  • Metadata completeness risks (app name, bundle identifier, privacy policy references).
  • Privacy manifest and required-reason API consistency.
  • Common rejection patterns in code and copy (placeholder text, insecure URLs, platform-reference mistakes).
  • Account and authentication policy pitfalls (for example social login patterns needing Apple Sign in support where applicable).

Step 4: Produce Report

Produce output in this structure:

  1. Scope detected
  2. Google Play findings
  3. Apple findings
  4. Manual console checklist items
  5. Release recommendation (READY / NOT READY)

For each finding include:

  • Severity (CRITICAL, WARN, INFO)
  • Title
  • Evidence (file path + short snippet/observation)
  • Fix recommendation

Optional Fast Path

If storeready is installed, optionally run:

storeready playstore-checkup .
storeready appstore-checkup .

Still validate manual policy checklist items from reference files, because not every store requirement is automatable.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.