Code Signing Android

Community

khadinakbarlabs

code-signing-android

Manage Android signing keys: upload key (you), signing key (Play), keystore generation, EAS credentials, SHA hash extraction. Use when the user says 'android signing', 'keystore', 'signing key android'.

Overview

Publisher	khadinakbarlabs
Repository	`expo-mobile-app-builder`
Skill name	`code-signing-android`
Stars	3
Forks	0
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by khadinakbarlabs on GitHub. Read the source before you install it.

Installation

Install the Code Signing Android AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/code-signing-android
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/code-signing-android

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/khadinakbarlabs/expo-mobile-app-builder.git /tmp/expo-mobile-app-builder
mkdir -p .claude/skills
cp -r /tmp/expo-mobile-app-builder/skills/code-signing-android .claude/skills/code-signing-android

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Code Signing Android in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Code Signing Android on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Code Signing Android is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Code Signing (Android)

Keystore management.

Credential and external action gate

An Android keystore and its password are private signing credentials. Do not generate, import, download, replace, or expose a keystore; run eas credentials; or alter Play App Signing without explicit owner confirmation of the exact developer account, app, and recovery plan. Keep keystores and passwords out of the repository, prompts, screenshots, and logs.

Two keys with Play App Signing

Key	Holder	Use
Upload key	You (EAS)	Sign AAB before upload
Signing key	Google	Sign APKs delivered to users

Lose upload key → Google reissues (Play App Signing benefit). Lose signing key → not possible (Google has it).

EAS-managed keystore after confirmation

bash
eas credentials
# → Android → set up new keystore

EAS generates keystore (.jks), stores on their servers. Download anytime.

DIY keystore (if migrating, after confirmation)

bash
keytool -genkey -v -keystore upload-key.jks \
  -keyalg RSA -keysize 2048 -validity 25000 \
  -alias upload-key

Upload to EAS only after the owner has approved the account and credential-storage plan:

bash
eas credentials
# → Android → use existing keystore

Extract SHA-1/SHA-256 (for Firebase)

bash
# From keystore (upload key)
keytool -list -v -keystore upload-key.jks -alias upload-key

# From Play Console (signing key)
# Play Console → Setup → App integrity → copy SHA values

Add to Firebase

Firebase Console → Project Settings → Your apps → Android app → Add fingerprint:

Both upload key SHA-1 + signing key SHA-1
Both upload key SHA-256 + signing key SHA-256

This makes Google Sign-In and Dynamic Links work in dev + production.

Common gotchas

"DEVELOPER_ERROR" on Google Sign-In → SHA-1 not in Firebase
Different SHA in dev (your keystore) vs production (Play's) → add BOTH
Keystore password lost → can't recover unless using Play App Signing reissue
".jks vs .keystore" → same format, just naming

Pair with

set-up-play-app-signing
add-google-signin-credential-manager

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Code Signing Android AI skill do?

Why use Code Signing Android on TypingMind?

Because you install it once and use it with any model. Code Signing Android is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Code Signing Android in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/khadinakbarlabs/expo-mobile-app-builder/tree/main/skills/code-signing-android. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Code Signing Android?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Code Signing Android?

As many as you like. As long as a model supports skills, you can use Code Signing Android with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Code Signing Android AI skill free?

Yes. It is published on GitHub by khadinakbarlabs under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Adr Verify

ruvnet

CommunityPopular

Read back adr-patterns + adr-edges namespaces, surface dangling refs / supersede cycles / status mismatches; exit 1 on cycles

Wasm Gallery

Browse, publish, and install WASM agents from the community gallery

Browser Extract

Extract structured data via stored browser-templates or one-shot DOM queries, with mandatory AIDefence PII + prompt-injection gates before content reaches the model

Browser Record

Open a named, traced browser session into an RVF cognitive container with a ruvector trajectory recording every action

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Code Signing (Android)

Credential and external action gate

Two keys with Play App Signing

EAS-managed keystore after confirmation

DIY keystore (if migrating, after confirmation)

Extract SHA-1/SHA-256 (for Firebase)

Add to Firebase

Common gotchas

Pair with

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now