clerk-android

Implement Clerk authentication in native Android apps with Kotlin and Jetpack Compose.

66|4|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/clerk/skills --skill clerk-android
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-android
Source: https://github.com/clerk/skills/tree/main/skills/mobile/clerk-android
Command: npx skills add https://github.com/clerk/skills --skill clerk-android

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes uncertainty and manual work when adding Clerk authentication to native Android projects by providing clear, source-driven patterns, flow choices (prebuilt vs custom), and mandatory verification checks so developers can integrate auth correctly and safely.

Core Features & Use Cases

  • Prebuilt and Custom Flows: Guides integration using prebuilt Compose views (AuthView/UserButton) or a custom API-driven implementation with clerk-android-api.
  • Safety and Verification Gates: Enforces asking for flow choice and a real publishable key, SDK initialization checks, correct artifact selection, and runtime capability gating to avoid misconfiguration.
  • Use Case: Add sign-in and profile UIs to a Kotlin + Jetpack Compose app using AuthView for fastest path or implement a multi-step custom flow that respects dashboard-driven factors and MFA.

Quick Start

Set up Clerk on my native Android Kotlin app by confirming it's a native project, choosing prebuilt or custom flow, providing the publishable key, and following the matching reference file (references/prebuilt.md or references/custom.md).

Frequently Asked Questions about clerk-android

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

FAQPage Schema
How do I add Clerk authentication to a native Android Kotlin app?

To add Clerk authentication to a native Android Kotlin app, you need Android Studio, the clerk-android Gradle artifacts, and a real publishable key wired into Clerk.initialize to set up either prebuilt or custom auth flows.

What is the difference between prebuilt and custom Clerk auth flows for Jetpack Compose?

Prebuilt Clerk auth flows use ready-made Compose views like AuthView and UserButton for quick setup, while custom flows use clerk-android-api to implement multi-step API-driven authentication that respects dashboard-driven factors and MFA.

Can I use Clerk for authentication on Android without Jetpack Compose?

Clerk authentication on Android is designed for native Kotlin projects using Jetpack Compose, providing prebuilt Compose views or custom API-driven implementations using the clerk-android-api artifact.

What publishable key is required to initialize the Clerk Android SDK?

Initializing the Clerk Android SDK requires a real publishable key wired into Clerk.initialize, which is verified through mandatory checks to prevent misconfiguration and ensure safe auth integration.

How do I implement a custom multi-step sign-in flow with the Clerk Android API?

Implement a custom multi-step sign-in flow using the clerk-android-api artifact, which enables API-driven authentication that respects dashboard-driven factors and MFA settings configured in your Clerk dashboard.

Why does my Clerk Android integration require runtime capability gating?

Runtime capability gating is enforced during Clerk Android initialization to avoid misconfiguration, verify correct artifact selection, and ensure the publishable key is properly wired before auth flows execute.