skills.rest
mqzkim
mqzkimCOMMUNITY
Explore all skills by this author →
GitHub

Android Keystore Setup

Generate, verify, and upload Android keystore files as base64 secrets to GitHub.

Updated Mar 1, 2026
Search Tags:#automation#ci/cd#android#github secrets#signing#keystore
One-click install
npx skills add https://github.com/mqzkim/trading --skill android-keystore-setup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Android Keystore Setup
Source: https://github.com/mqzkim/trading/tree/main/.agents/skills/android-keystore-setup
Command: npx skills add https://github.com/mqzkim/trading --skill android-keystore-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation and secure management of Android keystores, essential for app signing and deployment, and integrates them with GitHub Secrets for CI/CD pipelines.

Core Features & Use Cases

  • Keystore Generation: Creates a new .keystore file with specified parameters using keytool.
  • Keystore Verification: Allows verification of the generated keystore's details.
  • GitHub Secrets Integration: Automates the setup of necessary secrets in GitHub for seamless CI/CD integration.
  • Use Case: Streamline your Android app's build and release process by automating the setup of signing keys and their secure storage in your CI/CD environment.

Quick Start

Automate the setup of GitHub secrets for Android keystore by running the setup-github-secrets.sh script after configuring your .env file.

Frequently Asked Questions about Android Keystore Setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Android keystore creation and upload it to GitHub secrets?▼

To automate Android keystore creation and GitHub secrets upload, a script generates a `.keystore` file using `keytool`, encodes it as base64, and stores it in your repository via the `gh` CLI.

What do I need to generate an Android keystore for CI/CD signing?▼

To generate an Android keystore for CI/CD signing, you need Java JDK installed for `keytool` execution and the `gh` CLI to interact with GitHub repositories and configure the necessary secrets.

How can I verify the contents of a generated Android keystore?▼

You can verify the contents of a generated Android keystore by running a verification script that checks the keystore details, ensuring the signing credentials are correctly generated before deployment.

Does this keystore setup process support GitHub Actions pipelines?▼

Yes, the keystore setup process supports GitHub Actions pipelines by automating the secure storage of your base64 encoded signing keys as GitHub Secrets for seamless CI/CD integration.

Why encode an Android keystore as base64 for GitHub secrets?▼

Encoding an Android keystore as base64 for GitHub secrets allows the binary signing file to be securely stored as a text string, enabling CI/CD pipelines to decode and use it for automated app signing.

Related Skills

Explore More Software Engineering Skills→
KarlinskySKarlinskyS

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI login.

Community
Intermediate
decentpastedecentpaste
232

android-release

Build, sign, and align Android APKs and AABs for GitHub and Play Console releases.

Official
Intermediate
heximaoheximao

github-repo-management

Clone, create, fork, and configure GitHub repositories via the GitHub API.

Community
Intermediate
VGonPaVGonPa
2

deploying-flutter-android

Deploy Flutter Android apps to Google Play Store with signing and automation.

Community
Advanced