This skill provides expert knowledge on submitting Android apps to the Google Play Store via Play Console.
/plugin marketplace add rahulkeerthi/expo-toolkit/plugin install expo-toolkit@withqwertyThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides expert knowledge on submitting Android apps to the Google Play Store via Play Console.
Google Play provides multiple testing tracks before production release:
| Track | Testers | Review Time | Use Case |
|---|---|---|---|
| Internal | Up to 100 | Instant | Quick smoke testing, core team |
| Closed | Limited list | 3-5 days | Beta testers, stakeholder review |
| Open | Anyone can join | 3-5 days | Public beta, wide feedback |
| Production | All users | 1-7 days | Full public release |
Manual AAB Upload Required
eas build --platform android --profile production--auto-submit worksComplete Store Listing
Complete App Content
Google requires additional verification for new personal accounts:
Testing Requirement
Device Verification
Timeline Impact
Organisation accounts are EXEMPT from the 14-day testing requirement.
| Field | Max Length | Required |
|---|---|---|
| App name | 30 chars | Yes |
| Short description | 80 chars | Yes |
| Full description | 4000 chars | Yes |
Content Rules:
| Asset | Size | Format | Required |
|---|---|---|---|
| App icon | 512x512 | PNG | Yes |
| Feature graphic | 1024x500 | PNG/JPG | Yes |
| Phone screenshots | Varies | PNG/JPG | Min 2 |
| Tablet screenshots | Varies | PNG/JPG | If tablet support |
Screenshot Guidelines:
Complete the IARC questionnaire:
Declare your target age group:
If targeting children:
Declare your app's data practices:
Must be accurate - Google may verify against actual app behaviour.
Required for ALL apps that:
Requirements:
| Type | Description | Use Case |
|---|---|---|
| One-time | Single purchase, permanent | Premium features, remove ads |
| Subscription | Recurring payment | Premium access, content |
| Consumable | Can be purchased multiple times | Credits, virtual currency |
Base Plans:
Offers:
Grace Period:
| Status | Meaning |
|---|---|
| Active | Available for purchase |
| Inactive | Not available (draft or disabled) |
| Pending | Awaiting review |
Required for closed/open testing and production:
For production releases, you can:
Recommended for major updates:
Deceptive Behaviour
Privacy Issues
Content Issues
API Level
64-bit Requirement
Signing Issues
| Scenario | Typical Timeline |
|---|---|
| Internal testing | Instant |
| Closed/Open testing (first) | 3-5 days |
| Closed/Open testing (updates) | 1-3 days |
| Production (first app) | 7+ days |
| Production (updates) | 1-3 days |
| Policy appeal | 7-14 days |
Note: Holiday periods may extend review times.
Base: https://play.google.com/console/u/0/developers/{dev_id}/app/{app_id}
Store listing: .../store-listing
Content rating: .../content-rating
Data safety: .../data-safety
In-app products: .../managed-products
Subscriptions: .../subscriptions
Internal testing: .../tracks/internal-testing
Closed testing: .../tracks/closed-testing
Open testing: .../tracks/open-testing
Production: .../production
# 1. Build production AAB
eas build --platform android --profile production
# 2. Download from EAS dashboard
# 3. Manually upload to Play Console
# 4. Complete store listing and content
# 5. Submit for review
# Auto-submit to internal track
eas build --platform android --profile production --auto-submit
# Or specify track in eas.json
# submit.production.android.track: "internal"
eas.json:{
"submit": {
"production": {
"android": {
"serviceAccountKeyPath": "./play-store-credentials.json",
"track": "internal"
}
}
}
}
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.