authentication-authorization

Implement authentication and authorization with Clerk and RBAC across microservices.

1|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/splits-network/splits --skill authentication-authorization-splits-network
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authentication-authorization
Source: https://github.com/splits-network/splits/tree/main/.github/skills/authentication-authorization
Command: npx skills add https://github.com/splits-network/splits --skill authentication-authorization-splits-network

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the complexities of implementing secure authentication and authorization across a distributed system, ensuring only authorized users can access specific resources and data.

Core Features & Use Cases

  • Centralized Authentication: Integrates with Clerk for user sign-up and sign-in.
  • Role-Based Access Control (RBAC): Enforces permissions at API Gateway (route-level) and service (data-level) layers.
  • V2 Access Context: Standardizes how user roles and permissions are resolved and applied within V2 services.
  • Use Case: A new feature requires that only users with the 'company_admin' role can create new job postings. This skill provides the patterns to enforce this restriction both at the API endpoint and within the job creation service logic.

Quick Start

Implement authentication and authorization for your application using Clerk and RBAC patterns.

Frequently Asked Questions about authentication-authorization

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

FAQPage Schema
How do I implement role-based access control in microservices?

Role-based access control in microservices is implemented by enforcing permissions at the API Gateway for route-level protection and within individual services for data-level filtering using a standardized access context.

What's the best way to secure API gateway routes with Clerk authentication?

Securing API gateway routes with Clerk authentication involves integrating centralized sign-in flows and applying RBAC checks at the gateway layer to restrict endpoint access based on resolved user roles.

How does service-level data filtering work with RBAC?

Service-level data filtering with RBAC works by passing a standardized access context through microservices, allowing each service to filter query results and restrict operations based on the user's resolved permissions.

How do I restrict frontend UI elements based on user roles?

Frontend UI elements are restricted based on user roles by resolving the authenticated user's role hierarchy from Clerk and conditionally rendering components or routes that require specific permissions like 'company_admin'.

Can I enforce permissions at both the API endpoint and service logic layers?

Permissions can be enforced at both the API endpoint and service logic layers by applying route-level RBAC checks at the gateway and validating the access context within the downstream service implementation.

When do I need a standardized access context for user authorization?

A standardized access context for user authorization is needed when distributed microservices must consistently resolve user roles and permissions to apply uniform data-level filtering and secure system access.