Agent skill · software engineering · workos
workos-widgets
Use when the user is implementing, embedding, or debugging a WorkOS Widget — specifically the User Management, User Profile, Admin Portal SSO Connection, or Admin Portal Domain Verification widgets. Handles the full stack — detecting the frontend (Next.js, React, React Router, TanStack Start, Vite, SvelteKit), generating access tokens via the backend SDK in use (Node, Python, Go, Ruby, PHP, Java, .NET), and wiring up the widget component correctly per the bundled OpenAPI spec. Also use when code imports from @workos-inc/widgets or the user pastes <UserManagement /> or <UserProfile /> JSX.
Why this skill is useful
Adds executable scripts for integrating WorkOS widgets across various frontend frameworks and backend SDKs, which the AI cannot generate from existing knowledge.
What it needs
Requires workos installed locally. About 4k tokens when loaded. Last updated 2026-08-06. 43 stars on the source repository.
What this skill does
WorkOS Widgets Workflow Overview 1. Identify widget target from the user request (user-management, user-profile, admin-portal-sso-connection, admin-portal-domain-verification). 2. Scan project files in this order: package/dependency manifests framework/router entrypoints auth/token utilities styling/component patterns 3. Detect stack, data-layer style, styling, component system, and package manager using references/detection.md. 4. Check for AuthKit/WorkOS presence: if detected, continue; if not detected, ask the user to run WORKOSMODE=agent npx workos@latest install. Wait for confirmation, then continue. 5. If detection is ambiguous or conflicting, ask one focused question, then continue. 6. Load only the relevant reference files for the detected stack and widget. 7. Implement integration based on stack shape: frontend route/page + widget component when widget UI lives in the same app token endpoint/service + client integration surface when backend-first/multi-app architecture is detected 8. Validate routing/wiring, imports, and token/API usage before finishing. Canonical Inputs Accept these inputs from the user request when available: widget type (or infer from request intent) optional component path optional page/route path optional token endpoint/service preference optional constraints (for example: avoid broad refactors) When input is missing, infer from existing project conventions and detected stack. Detection and Ambiguity Protocol Apply detection heuristics from references/detection.md. Explore before asking. Ask only when ambiguity remains after checking manifests and route/auth entrypoints. Ask a single concrete question that resolves one decision. Default to the strongest detected ownership signals when no user response is available. When installs are required, use the package manager detected from project files/lockfiles. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills workos/workos-widgets