SkillsAdd

krutikjain/android-agent-skills

android-ci-cd-release-playstore

Automate Android CI, versioning, signing boundaries, release channels, and Play-ready delivery workflows.

First seen Mar 7, 2026

Installation

$ npx skills add krutikjain/android-agent-skills --skill android-ci-cd-release-playstore
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from krutikjain/android-agent-skills · top by installs.

npx skills add krutikjain/android-agent-skills
android-di-hilt 335 android-kotlin-core 304 android-gradle-build-logic 303 android-testing-unit 294 android-compose-foundations 292 android-architecture-clean 289 android-coroutines-flow 257 android-networking-retrofit-okhttp 254 android-material3-design-system 147 android-room-database 121

Browse all from krutikjain/android-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 14
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.0
More metadata
version
0.1.0
category
quality-release
tags
["android","ci","cd","release"]
triggers
{"include":["android ci cd pipeline","play store release automation","android signing and release","canary stable release android","github actions android build"],"exclude":["compose semantics only","fragment back stack only","datastore migration only"]}
owners
["@android-agent-skills\/maintainers"]
test_targets
["examples\/orbittasks-compose","examples\/orbittasks-xml","benchmarks\/triggers.jsonl"]

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,477 B
  • docs SUMMARY.md 144 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 43 installs

SKILL.md

Android CI CD Release PlayStore

When To Use

  • Use this skill when the request is about: android ci cd pipeline, play store release automation, android signing and release.
  • Primary outcome: Automate Android CI, versioning, signing boundaries, release channels, and Play-ready delivery workflows.
  • Handoff skills when the scope expands:
  • android-gradle-build-logic
  • android-security-best-practices

Workflow

  1. Scope the risk surface: correctness, security, performance, test depth, or release automation.
  2. Pick the narrowest verification strategy that still catches the likely regressions.
  3. Instrument the workflow so failures are actionable rather than just red.
  4. Run the relevant checks on the showcase apps and packaging outputs.
  5. Capture any residual risk with explicit follow-up work and owner skills.

Guardrails

  • Prefer reproducible checks in CI over one-off local heroics.
  • Fail with a precise remediation path instead of a vague quality gate.
  • Keep secrets, signing material, and production credentials out of examples and fixtures.
  • Treat performance and security work as engineering tasks with evidence, not folklore.

Anti-Patterns

  • Adding more tests without increasing signal.
  • Shipping benchmarks or security scans that no one can reproduce.
  • Hard-coding release credentials into build logic.
  • Using synthetic metrics with no user-impact interpretation.

Examples

Happy path

  • Scenario: Validate the repo CI workflow, adapter generation, and version metadata flow.
  • Command: python3 scripts/validate_repo.py

Edge case

  • Scenario: Check canary and stable release script behavior before tagging.
  • Command: python3 scripts/release.py --channel canary --dry-run

Failure recovery

  • Scenario: Avoid routing pure build-logic or security work into release automation.
  • Command: python3 scripts/eval_triggers.py --skill android-ci-cd-release-playstore

Done Checklist

  • The implementation path is explicit, minimal, and tied to the right Android surface.
  • Relevant example commands and benchmark prompts have been exercised or updated.
  • Handoffs to adjacent skills are documented when the request crosses boundaries.
  • Official references cover the chosen pattern and the main migration or troubleshooting path.

Official References