clerk-android

Implements Clerk authentication in native Android apps using Kotlin and Jetpack Compose.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/Rajaryan1726/ai-code-review-system --skill clerk-android-rajaryan1726
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clerk-android
Source: https://github.com/Rajaryan1726/ai-code-review-system/tree/main/client/.agents/skills/clerk-android
Command: npx skills add https://github.com/Rajaryan1726/ai-code-review-system --skill clerk-android-rajaryan1726

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Adding authentication to a native Android app requires correctly wiring the Clerk Android SDK, choosing between prebuilt UI components and custom API-driven flows, and matching dashboard-configured capabilities like MFA and social providers. This Skill guides that implementation with source-grounded patterns so the setup is correct on the first pass. ## Core Features & Use Cases - Prebuilt Flow: Integrates Clerk's AuthView and UserButton Compose components via the clerk-android-ui artifact for fast sign-in/sign-up UI. - Custom Flow: Builds multi-step, capability-driven auth flows with the clerk-android-api artifact, separating UI, state orchestration, and Clerk API integration. - Quickstart Compliance: Verifies Native API enablement, minimum SDK/Java targets, manifest internet permission, and app-level Clerk.initialize(...) before finishing. - Use Case: A developer building a Kotlin/Jetpack Compose app asks to add Clerk login; the Skill confirms prebuilt vs custom flow, collects the publishable key, installs the right Gradle artifact, and implements the flow following the matching reference checklist. ## Quick Start Add Clerk authentication to my native Android app using the prebuilt AuthView flow with my publishable key.

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 app?▼

Add the clerk-android Gradle dependency, call Clerk.initialize with your publishable key in the Application startup path, and gate UI on Clerk.isInitialized. Then choose prebuilt AuthView/UserButton components or a custom API-driven flow depending on how much control you need.

What is the difference between clerk-android-ui and clerk-android-api?▼

clerk-android-ui provides prebuilt Compose components like AuthView and UserButton and includes the API artifact transitively. clerk-android-api is for custom flows where you build your own UI and orchestrate sign-in/sign-up steps directly against Clerk APIs.

Can I use Clerk Android with Expo or React Native?▼

No, this Skill explicitly does not apply to Expo or React Native projects. It targets native Android only, detected via build.gradle files, AndroidManifest.xml, and Compose sources; cross-platform projects should use the general Clerk setup skill instead.

Why is my Clerk Android auth UI not rendering?▼

The most common cause is rendering before SDK initialization completes. Gate your signed-in/signed-out UI on Clerk.isInitialized and Clerk.userFlow, and confirm Clerk.initialize is called from the Application startup path with a valid publishable key.

How do I handle MFA and social providers in a custom Clerk Android flow?▼

Drive flow branches from Clerk runtime capability fields such as enabledFirstFactorAttributes, socialProviders, isGoogleOneTapEnabled, and mfaIsEnabled rather than hardcoding factors. This keeps the flow aligned with your Clerk Dashboard configuration.