workos-widgets

Implement WorkOS Widgets with access-token flows across frontend and backend stacks.

Updated Dec 20, 2025
One-click install
npx skills add https://github.com/iqbal125/typescript_projects --skill workos-widgets-iqbal125
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workos-widgets
Source: https://github.com/iqbal125/typescript_projects/tree/main/nestjs-react-monorepo-nx/.agents/skills/workos-widgets
Command: npx skills add https://github.com/iqbal125/typescript_projects --skill workos-widgets-iqbal125

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Widgets integration and migration across diverse stacks require correct token handling and API wiring to work with the WorkOS OpenAPI spec.

Core Features & Use Cases

  • Detect stack and implement widget integration with proper access-token flow for user-management, user-profile, admin portal SSO, and domain verification across JS/TS and server frameworks.
  • Load only stack-specific references and ensure correct route/component wiring, token surface, and elevated-access handling when needed.
  • Support for both frontend and backend integration patterns, enabling End-to-end widget usage in monorepos and multi-app architectures.

Quick Start

Configure your app to fetch a widget token with the proper scope and render the WorkOS widget using the existing UI components.

Frequently Asked Questions about workos-widgets

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

FAQPage Schema
How do I integrate WorkOS Widgets into a Next.js or React Router application?

To integrate WorkOS Widgets, you must fetch a widget token with the proper scope and render the widget using your existing UI components. This skill detects your specific stack and guides the correct route and component wiring.

What is the correct access-token flow for WorkOS admin portal and user profile widgets?

The correct access-token flow requires fetching a widget token with the proper scope for user-management and admin portal SSO. The skill ensures correct token handling, token surface, and elevated-access handling when needed.

Can I use WorkOS Widgets with backend frameworks like Python, Go, or Ruby?

Yes, WorkOS Widgets support both frontend and backend integration patterns across Python, Go, Ruby, PHP, and Java. The skill guides stack-specific OpenAPI usage and ensures adherence to host project routing and error-handling conventions.

How do I handle WorkOS Widget integration and migration in a monorepo architecture?

For monorepo architectures, the skill supports end-to-end widget usage by loading only stack-specific references. It ensures correct API wiring and token handling to work with the WorkOS OpenAPI spec across multiple apps.

Does WorkOS Widget integration require elevated-access handling for domain verification?

Yes, domain verification and admin portal SSO widgets often require elevated-access handling. The skill ensures proper token surface and elevated-access logic when implementing these features across JS/TS and server frameworks.