clerk-android

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

Updated May 4, 2026
One-click install
npx skills add https://github.com/Endsi3g/Uprising-AOS --skill clerk-android-endsi3g
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk-android
Source: https://github.com/Endsi3g/Uprising-AOS/tree/main/.agents/skills/clerk-android
Command: npx skills add https://github.com/Endsi3g/Uprising-AOS --skill clerk-android-endsi3g

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It removes the guesswork of integrating Clerk authentication into native Android apps by guiding correct setup and flow-specific implementation.

Core Features & Use Cases

  • Native Android Clerk integration: Implements Clerk auth in Kotlin with Jetpack Compose using clerk-android source-aligned patterns.
  • Prebuilt vs custom flows: Supports both AuthView/UserButton (prebuilt) and API-driven multi-step flows (custom) without mixing approaches.
  • Safety guardrails: Prevents implementation for Expo/React Native projects, enforces asking for missing flow choice and a real publishable key, and ensures Android quickstart prerequisites are verified before edits.

Quick Start

Ask the agent to implement Clerk authentication for a native Android Kotlin Jetpack Compose project, choosing prebuilt or custom flow, and providing a real Clerk 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 Kotlin app using Jetpack Compose?

Add Clerk authentication to native Android Kotlin apps by selecting a prebuilt AuthView flow or custom API-driven multi-step sign-in, then applying source-guided patterns with a real publishable key. The integration requires Jetpack Compose UI and native Android project structure.

Can I use Clerk prebuilt AuthView and UserButton components in Jetpack Compose?

Yes, Clerk prebuilt AuthView and UserButton components work directly in Jetpack Compose projects. This Skill guides the implementation of prebuilt UI flows for native Android apps, requiring a confirmed flow choice and verified Android quickstart prerequisites before any edits.

Does Clerk Android authentication work with Expo or React Native projects?

No, Clerk Android authentication does not work with Expo or React Native projects. This Skill includes safety guardrails that prevent implementation for cross-platform setups, enforcing native Android structure with Kotlin and Jetpack Compose before applying authentication patterns.

What is the difference between prebuilt and custom Clerk authentication flows in Android?

Prebuilt Clerk flows use native AuthView and UserButton components for quick integration, while custom flows use API-driven multi-step sign-in and sign-up logic. This Skill enforces choosing one approach without mixing patterns to maintain correct Android authentication implementation.

What prerequisites do I need before implementing Clerk auth in an Android app?

Before implementing Clerk auth, you must verify Android quickstart prerequisites, complete initialization, add artifacts, and ensure Clerk.isInitialized gating passes. A real publishable key and a confirmed prebuilt or custom flow choice are mandatory before any implementation edits.

Why is my Clerk Android authentication not initializing in Jetpack Compose?

Clerk authentication fails to initialize when prerequisites are unmet, missing a real publishable key, or when Clerk.isInitialized gating is not enforced. Verify Android quickstart setup, confirm initialization artifacts are added, and ensure the project uses native Android structure.