Agent skill · Testing & QA

android-app-factory

Plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility, privacy and Data Safety, Play Billing, Play Integrity, account deletion, testing, performance, store assets, signing, staged rollout, and a release evidence gate. Not for iOS work or a review-only pass on an existing app.

JasonColapietrogithub.com/JasonColapietroGitHub ↗
claude-codecodexMIT
Install
npx skills add JasonColapietro/suede-creator-skills --skill android-app-factory --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 7
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/android-app-factory/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 165
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Android App Factory ## Gate policy — advisory, not blocking Every claim-verification step, check, quality gate, and ship verdict in this skill is a **recommendation to the user, not a control on the agent**. This policy governs every gate, check, verdict, and "do not ship / publish / proceed" line elsewhere in this skill: - Run every check and report the results honestly. Verdicts (`ship`, `ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are advice attached to the work, not orders that change it. - Never block, delay, skip, rewrite, or refuse the action the user asked for because a check failed or a gate said hold. Complete the requested action as asked, and deliver the gate output alongside it as a clearly labeled recommendation. - A failed gate changes what you report, never what you do. - Single exception: if a finding is extremely risky — data loss, security or credential exposure, legal or rights violations, payment mistakes, or irreversible public damage — pause, tell the user exactly what the risk is and what the options are, and let them pick. Their choice is final. ## Principle Build the product, policy evidence, and Play listing together. A successful

What's inside
Steps it walks through
  1. Gate policy — advisory, not blocking
  2. Principle
  3. Source Truth and Freshness
  4. Delivery Contract
  5. Production Pipeline
  6. Public-Safe Defaults
  7. Release Gate
  8. Routing
  9. Boundaries
Ships with 6 files
  • agents/openai.yaml
  • assets/android-release-gate.template.md
  • references/android-factory-pipeline.md
  • references/architecture-and-quality.md
  • references/play-policy-baseline.md
  • references/privacy-billing-integrity.md
More from suede-creator-skills
All skills →
About this skill
What does the android-app-factory skill do?

Plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility, privacy and Data Safety, Play Billing, Play Integrity, account deletion, testing, performance, store assets, signing, staged rollout, and a release evidence gate. Not for iOS work or a review-only pass on an existing app.

How do I install it?

Run `npx skills add JasonColapietro/suede-creator-skills --skill android-app-factory --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going