auth-clerk

Manage user authentication and authorization with Clerk for the RRQ Content Factory.

3|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/GunjanGrunge/rrq --skill auth-clerk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-clerk
Source: https://github.com/GunjanGrunge/rrq/tree/main/skills/auth-clerk
Command: npx skills add https://github.com/GunjanGrunge/rrq --skill auth-clerk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust authentication and user management system for the RRQ Content Factory, ensuring secure access and personalized user experiences.

Core Features & Use Cases

  • User Authentication: Handles sign-in, sign-up, and session management.
  • Third-Party Integrations: Supports YouTube OAuth connections and Stripe for plan gating.
  • User Management: Manages user metadata, including subscription plans and settings.
  • Route Protection: Secures application routes based on authentication status.
  • Use Case: A new user signs up for the RRQ Content Factory, connects their YouTube account, and is automatically assigned a 'free' plan, with their data securely stored and accessible only to them.

Quick Start

Implement Clerk authentication by following the setup instructions in the SKILL.md file.

Frequently Asked Questions about auth-clerk

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

FAQPage Schema
How do I add Clerk authentication and user management to a Next.js application?

Clerk authentication handles sign-in, sign-up, and session management for Next.js applications. It provides pre-built components and route protection to secure application features and user data without building auth flows from scratch.

Can I connect a YouTube OAuth account and assign a subscription plan using Clerk?

Yes, Clerk supports third-party OAuth integrations like YouTube and connects with Stripe for subscription management. New users can connect external accounts and be automatically assigned a 'free' plan with data stored in dynamic user metadata.

What's the best way to implement plan-based access control with Stripe in Next.js?

Plan-based access control is implemented by integrating Clerk with Stripe for subscription gating. This combination manages user metadata, tracks subscription tiers, and dynamically restricts access to application features based on the user's current plan.

Does Clerk support dynamic user metadata for personalized Next.js application experiences?

Yes, Clerk supports dynamic user metadata to enable personalized experiences. It securely stores individual user settings and subscription plan details, allowing the application to tailor content and feature availability based on the stored metadata.

How do I secure application routes based on authentication status in Next.js?

Route protection secures application routes by checking authentication status via Clerk. It prevents unauthenticated users from accessing protected pages, ensuring only authorized sessions can view sensitive application features and user data.