clerk

Implement username/password authentication against Clerk's Frontend API for iLEAP adapters.

6|Updated Jun 1, 2025
One-click install
npx skills add https://github.com/way-platform/ileap-go --skill clerk-way-platform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clerk
Source: https://github.com/way-platform/ileap-go/tree/main/.agents/skills/clerk
Command: npx skills add https://github.com/way-platform/ileap-go --skill clerk-way-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides guidance on implementing programmatic username/password authentication against Clerk using the Frontend API (FAPI) for iLEAP authentication server adapters or similar backends that require direct login flows.

Core Features & Use Cases

  • Guides how to use Clerk's Frontend API sign_ins to authenticate a user with an identifier (username or email) and password.
  • Describes handling of common flows including successful sign-in, MFA (needs_second_factor) scenarios, and error conditions.
  • Explains how to integrate with iLEAP by proxying credentials, optionally activating an organization, and returning the session token as an iLEAP-compatible token.

Quick Start

Proxy incoming username and password to Clerk's Frontend API sign_ins endpoint and return the Clerk session token for use as an iLEAP token.

Frequently Asked Questions about clerk

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

FAQPage Schema
How do I implement username and password authentication using the Clerk Frontend API?

To implement username/password authentication with the Clerk Frontend API, proxy incoming credentials to the sign_ins endpoint, handle the response statuses, and extract the session token for your backend.

How does Clerk Frontend API handle MFA during a sign_in flow?

Clerk FAPI handles MFA by returning a needs_second_factor status during the sign_ins flow, requiring your authentication adapter to process the additional verification step before finalizing the login.

Can I use Clerk session tokens for an iLEAP authentication server adapter?

Yes, you can use Clerk session tokens for an iLEAP adapter by proxying credentials through the Clerk Frontend API sign_ins endpoint and returning the extracted session token as an iLEAP-compatible token.

How do I activate an organization when authenticating users via Clerk FAPI?

You can optionally activate an organization during the Clerk FAPI authentication flow by including the organization parameters when proxying credentials to the sign_ins endpoint.

What error conditions should I handle when proxying login requests to Clerk's sign_ins endpoint?

When proxying login requests to Clerk's sign_ins endpoint, your backend must handle successful sign-ins, MFA needs_second_factor scenarios, and standard error conditions to ensure robust authentication.

Does programmatic authentication against Clerk require browser-based JavaScript?

No, programmatic authentication against Clerk via the Frontend API does not require browser-based JavaScript, as it is designed for direct backend login flows and iLEAP authentication server adapters.