android-playstore-publishing
Complete workflow generation - orchestrates internal, beta, and production deployment workflows
Best use case
android-playstore-publishing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Complete workflow generation - orchestrates internal, beta, and production deployment workflows
Teams using android-playstore-publishing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/android-playstore-publishing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How android-playstore-publishing Compares
| Feature / Agent | android-playstore-publishing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Complete workflow generation - orchestrates internal, beta, and production deployment workflows
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Android Play Store Publishing
This skill orchestrates complete GitHub Actions workflow generation by running three atomic skills in sequence.
## What This Does
Generates all GitHub Actions workflows for Play Store deployment:
1. **Internal Workflow** - Automatic deployment on push
2. **Beta Workflow** - Manual deployment to alpha/beta tracks
3. **Production Workflows** - Deployment and rollout management
## Prerequisites
- Play Console setup complete (run `android-playstore-setup` first)
- SERVICE_ACCOUNT_JSON_PLAINTEXT in GitHub Secrets
- Signing secrets configured
- Package name known
## Process
This skill runs three sub-skills in order:
### Step 1: Generate Internal Testing Workflow
Follow the skill at: `~/claude-devtools/skills/android-workflow-internal/SKILL.md`
**What it does:**
- Creates deploy-internal.yml
- Triggers on push to main/develop
- Deploys automatically to internal track
- Preserves build artifacts
**Verify before continuing:**
```bash
yamllint .github/workflows/deploy-internal.yml
```
---
### Step 2: Generate Beta Testing Workflow
Follow the skill at: `~/claude-devtools/skills/android-workflow-beta/SKILL.md`
**What it does:**
- Creates deploy-beta.yml
- Manual trigger with track selection (alpha/beta)
- Configurable rollout percentage
- Artifact preservation
**Verify before continuing:**
```bash
yamllint .github/workflows/deploy-beta.yml
```
---
### Step 3: Generate Production Workflows
Follow the skill at: `~/claude-devtools/skills/android-workflow-production/SKILL.md`
**What it does:**
- Creates deploy-production.yml (deployment)
- Creates manage-rollout.yml (rollout control)
- Requires manual approval via environment
- Staged rollout with configurable percentages
**Verify before continuing:**
```bash
yamllint .github/workflows/deploy-production.yml
yamllint .github/workflows/manage-rollout.yml
```
---
## Final Verification (MANDATORY)
After all three skills complete, verify the complete setup:
```bash
# 1. Verify all workflows exist
ls .github/workflows/deploy-*.yml .github/workflows/manage-rollout.yml
# 2. Validate all YAML files
yamllint .github/workflows/deploy-*.yml .github/workflows/manage-rollout.yml
# 3. Verify package names are correct
grep "packageName:" .github/workflows/deploy-*.yml
# 4. Verify workflows use correct secrets
grep "secrets\." .github/workflows/deploy-*.yml
```
**All checks must pass** before marking this skill as complete.
## Completion Criteria
Do NOT mark complete unless ALL are verified:
✅ **Workflows created**
- [ ] .github/workflows/deploy-internal.yml exists
- [ ] .github/workflows/deploy-beta.yml exists
- [ ] .github/workflows/deploy-production.yml exists
- [ ] .github/workflows/manage-rollout.yml exists
✅ **Validation**
- [ ] All YAML files are valid
- [ ] Package names are correct in all files
- [ ] Workflows reference correct secrets
✅ **Documentation**
- [ ] .github/workflows/README.md created
- [ ] Environment setup documented
✅ **GitHub Setup**
- [ ] "production" environment created
- [ ] Required reviewers configured
## Summary Report
After completion, provide this summary:
```
✅ Android Play Store Publishing Setup Complete!
📦 Workflows Created:
✓ deploy-internal.yml (auto on push)
✓ deploy-beta.yml (manual, alpha/beta)
✓ deploy-production.yml (staged rollout)
✓ manage-rollout.yml (rollout control)
📋 Next Steps:
1. Create GitHub Environment:
Repository → Settings → Environments
Create "production" with required reviewers
2. Add GitHub Secrets:
- SERVICE_ACCOUNT_JSON_PLAINTEXT (from Play Console setup)
- SIGNING_KEY_STORE_BASE64
- SIGNING_KEY_ALIAS
- SIGNING_STORE_PASSWORD
- SIGNING_KEY_PASSWORD
3. First Deployment:
git push origin main
→ Deploys to internal automatically
4. Production Deployment:
git tag v1.0.0
git push origin v1.0.0
→ Requires approval, deploys with 5% rollout
📊 Deployment Workflow:
Development → Internal (auto) → Beta (manual) → Production (approval + staged)
⚠️ CRITICAL:
- Create "production" environment BEFORE first production deploy
- Test in internal track before beta/production
- Use staged rollouts (start at 5%)
- Monitor crash-free rate before increasing rollout
```
## Integration with Other Skills
This skill completes the deployment pipeline:
- Requires: `android-playstore-setup` - Service account and API
- Requires: `android-release-build-setup` - Signing configuration
- Used by: `android-playstore-pipeline` - Complete orchestration
## Troubleshooting
If any skill fails:
1. Fix the specific issue in that skill
2. Re-run that skill until it completes
3. Continue with remaining skills
4. Run final verification
Common issues:
- **YAML validation fails** → Check indentation (use spaces, not tabs)
- **Package name mismatch** → Verify package name in all workflows
- **Missing secrets** → Add all 5 required secrets to GitHub
- **Environment not found** → Create "production" environment firstRelated Skills
implementing-android-code
This skill should be used when implementing Android code in Bitwarden. Covers critical patterns, gotchas, and anti-patterns unique to this codebase. Triggered by "How do I implement a ViewModel?", "Create a new screen", "Add navigation", "Write a repository", "BaseViewModel pattern", "State-Action-Event", "type-safe navigation", "@Serializable route", "SavedStateHandle persistence", "process death recovery", "handleAction", "sendAction", "Hilt module", "Repository pattern", "implementing a screen", "adding a data source", "handling navigation", "encrypted storage", "security patterns", "Clock injection", "DataState", or any questions about implementing features, screens, ViewModels, data sources, or navigation in the Bitwarden Android app.
android-agent-skills
Production-ready Agent Skills framework for Android Kotlin development. Provides Clean Architecture patterns, Jetpack Compose best practices, validation DSL, MVI state management, error handling, and AI-powered code generation. Use when building Android apps with quality standards, generating ViewModels, Repositories, UseCases, Compose screens, or writing pure Kotlin Agent Skills.
android-workflow-beta
Generate GitHub Actions workflow for beta testing track deployment
android-screenshot-automation
Setup automated screenshot capture for Play Store using Fastlane Screengrab
android-emulator-skill
Production-ready scripts for Android app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and emulator lifecycle management. Optimized for AI agents with minimal token output. Android equivalent of ios-simulator-skill.
adb-android-control
Comprehensive Android device control via ADB (Android Debug Bridge). Use when user asks about: Android device management, app installation/uninstallation, APK operations, package management, file transfer (push/pull), screenshots, screen recording, input simulation (tap/swipe/text/keyevents), shell commands, logcat viewing, device info (battery/memory/storage), automation scripts, wireless ADB connection, scrcpy mirroring. Keywords: adb, android, phone, tablet, device, apk, install app, uninstall app, screenshot, screen record, tap, swipe, type text, keyevent, logcat, push file, pull file, shell, package, activity, intent, broadcast, dumpsys, getprop, settings, input, sendevent, monkey, am start, pm list, device info, battery status, wireless adb, connect device.
android-restart-app
Restart the Android app on connected device without rebuilding. Force-stops and relaunches the app remotely. Use when testing changes that don't require rebuild, or refreshing app state.
android-qa-verification
This skill is used to verify Android features against acceptance criteria, catch regressions and define tests that reflect real device behaviour.
android-playstore-api-validation
Create and run validation script to test Play Store API connection
publishing
Content strategy for external platforms (X, LinkedIn, etc.). Voice, style, and growth strategies.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
mcp-create-declarative-agent
Skill converted from mcp-create-declarative-agent.prompt.md