agentleFS
Sign inStart free
SUDARSHANCHAUDHARISUDARSHANCHAUDHARI/DroidForge/skills/keystore-conventions/SKILL.md

keystore-conventions

Skill1 starsChanged 9 days agoMITView on GitHub

Android keystore generation standards for DroidForge users — RSA 2048, 10000-day validity, consistent alias and password conventions. Loaded when creating a keystore, signing config, or new Android app.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never commit .jks or .keystore files — always in .gitignore as *.jks and *.keystore

    line 48
  2. Distinctive:

    Never store keystore password in any tracked file

    line 49
  3. Distinctive:

    Keep keystores in a secure, backed-up location outside the git repo

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Android Keystore Standards

Standard parameters

FieldValue
AlgorithmRSA
Key size2048 bits
Validity10000 days (~27 years)
Key alias[appname_lowercase] (e.g. taskmaster)
Key passenv var DROIDFORGE_KEYSTORE_PASSWORD (never stored by DroidForge)
Store passsame as key pass (consistent for simplicity)
CN{config.android.keystore_cn}
OUMobile
O{config.android.keystore_cn}
L{config.developer.city}
ST{config.developer.city}
C{config.android.keystore_country_code}

Filename convention

[appname_lowercase].jks

Example: app "TaskMaster" → taskmaster.jks, alias taskmaster

Standard keytool command

keytool -genkeypair \
  -alias [appname_lowercase] \
  -keypass:env DROIDFORGE_KEYSTORE_PASSWORD \
  -storepass:env DROIDFORGE_KEYSTORE_PASSWORD \
  -keystore [appname_lowercase].jks \
  -keyalg RSA \
  -keysize 2048 \
  -validity 10000 \
  -dname "CN={config.android.keystore_cn}, OU=Mobile, O={config.android.keystore_cn}, L={config.developer.city}, ST={config.developer.city}, C={config.android.keystore_country_code}"

Security rules

  • Never commit .jks or .keystore files — always in .gitignore as *.jks and *.keystore
  • Never store keystore password in any tracked file
  • Keep keystores in a secure, backed-up location outside the git repo
  • Back up to encrypted cloud storage immediately after creation

Critical warning

Losing a keystore = cannot update the app on Play Store. The only option is to publish a new app listing and lose all existing installs and reviews. Always back up.

Play App Signing (recommended)

Google Play App Signing adds a second layer of protection:

  • Your .jks becomes the upload key — used only to upload the AAB
  • Google generates and manages the app signing key — used to sign APKs delivered to users
  • Even if you lose the upload key, Google can generate a new one
  • Enroll via: Play Console → [App] → Release → Setup → App signing

Verification after creation

keytool -list -v -keystore [appname_lowercase].jks -storepass:env DROIDFORGE_KEYSTORE_PASSWORD

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free