A collection of AI agent skills for integrating Descope authentication into your applications. Skills follow the Agent Skills format and work with any compatible AI coding assistant.
descope-auth — Integrate Descope authentication into applications
Integrate Descope authentication into applications with support for passwordless auth, OAuth, SSO, and MFA. Uses a smart router pattern to detect your framework and provide targeted integration guidance.
Use when:
- "Add authentication to my app"
- "Implement login with Descope"
- "Set up passwordless auth"
- "Add OAuth/SSO to my application"
- "Integrate passkeys"
Frameworks supported:
- Next.js (App Router with middleware)
- React (SPA with protected routes)
- Kotlin / Android (Native Flows with session management)
- Swift / iOS (Native Flows with session management)
- Node.js (backend session validation)
- Python (backend session validation)
Features:
- Framework detection - Automatically routes to appropriate integration guide
- Security guardrails - Prevents common authentication mistakes
- Skills.sh compliant - Follows official specification
- Copy-paste ready - All code examples use correct SDK imports
Authentication methods covered:
- OTP (Email/SMS) - Quick verification codes
- Magic Link - Passwordless email links
- Passkeys - Biometric/WebAuthn (most secure)
- OAuth - Social login (Google, GitHub, etc.)
- SSO - Enterprise SAML/OIDC
- TOTP - Authenticator app MFA
- Passwords - Traditional auth (fallback)
auth-review — Static security review for authentication and authorization vulnerabilities
Framework- and vendor-agnostic static review that enumerates every route/endpoint in a codebase, builds an authorization matrix, applies a vulnerability catalog (OWASP Web + API Top 10 identity categories), and writes a triage report ready to slice into GitHub issues or PRs.
Use when:
- "/auth-review"
- "Audit authentication in my app"
- "Find authorization bugs / IDOR / BOLA"
- "Review access control"
- "Identity security review before release"
Covers:
- Broken authentication (missing auth, weak password handling, SQLi-in-login, enumeration)
- JWT / token flaws (
alg:none, algorithm confusion, unverified decode, missing claim validation) - Session management (cookie flags, fixation, logout invalidation, predictable IDs)
- Broken access control (IDOR / BOLA, BFLA, tenant crossing, client-trusted input)
- Privilege escalation & mass assignment
- OAuth / OIDC / SAML (state/PKCE, open redirect, ID-token validation, SAML XSW)
- Password reset & account recovery (predictable/non-expiring tokens, host poisoning, MFA bypass)
- MFA bypass and step-up gaps
- Rate limiting & enumeration on auth surfaces
- CSRF, CORS, identity-adjacent SSRF
Output:
- Triage report in
./auth-review/report-YYYY-MM-DD.md - Endpoint inventory and authorization matrix
- Findings with severity (High/Medium/Low), CWE,
file:line, evidence, remediation - Pre-formatted issue bodies ready to paste into GitHub
Scope: static and read-only. Does not run the target application, make network probes, modify code, or file issues directly.
descope-terraform — Manage Descope projects as infrastructure-as-code
Manage Descope projects as infrastructure-as-code using the official Terraform provider. Generates valid HCL configurations for authentication methods, RBAC, connectors, and project settings.
Use when:
- "Set up Terraform for my Descope project"
- "Manage Descope authentication config as code"
- "Create roles and permissions with Terraform"
- "Add connectors to my Descope Terraform config"
- "Deploy Descope project settings across environments"
Resources managed:
descope_project- Full project configuration (auth methods, RBAC, connectors, flows, settings)descope_management_key- Management keys with RBAC scopingdescope_descoper- Console user accounts with role assignments
Covers:
- Provider setup and management key configuration
- Authentication methods (OTP, Magic Link, Passkeys, OAuth, SSO, Password, TOTP)
- Authorization (roles and permissions)
- 60+ connector types (email, SMS, HTTP, observability, fraud detection, CRM, etc.)
- Project settings, applications (OIDC/SAML), flows, JWT templates, and custom attributes
Requirements:
- Terraform CLI installed
- Paid Descope License (Pro +)
- Management Key from Company Settings
auth0-to-descope — Migrate applications from Auth0 to Descope
Guides self-service migrations from Auth0 to Descope across any language or framework. Analyzes auth touchpoints, produces a reviewed MIGRATION-PLAN.md, then executes the migration. Uses the Descope Docs MCP when available to verify SDK method names and option shapes.
Use when:
- "Migrate my app from Auth0 to Descope"
- "Replace Auth0 with Descope"
- "Our app uses nextjs-auth0 / express-openid-connect / auth0-fastapi — switch to Descope"
- "How do Auth0 Actions / Organizations / Token Vault map to Descope?"
- "We're moving off Auth0"
Covers:
- SDK replacement for all major frameworks (Next.js, React, Express, Python, etc.)
- Auth0 feature mappings: Actions → Descope flows, Organizations → Tenants, Token Vault, CIBA
- Descope Flow and Widget setup (console-first approach)
- SSO and OIDC compatibility
- Session validation patterns
Output:
MIGRATION-PLAN.mdfor human review before any code changes- SDK replacement across all auth touchpoints in the codebase
- Descope Flow and Widget integration
Workflow: MCP check → migration plan (human review) → execution. Never skips ahead.
okta-cis-to-descope — Migrate applications from Okta CIS to Descope
Guides self-service migrations from Okta Customer Identity Service (CIS) to Descope across any language or framework. Detects whether the app uses hosted/redirect login or an embedded widget and defaults to the appropriate migration path. Analyzes auth touchpoints, produces a reviewed MIGRATION-PLAN.md, then executes the migration. Uses the Descope Docs MCP when available to verify SDK method names and option shapes.
Use when:
- "Migrate my app from Okta to Descope"
- "Replace Okta CIS with Descope"
- "Our app uses okta-auth-js / @okta/okta-react / @okta/oidc-middleware / okta-jwt-verifier — switch to Descope"
- "How do Okta Sign-On Policies / Authorization Servers / Authenticators / Log Streams map to Descope?"
- "We're moving off Okta"
Covers:
- SDK replacement for all major frameworks (React, Angular, Vue, Next.js, Express, Python, Java, and more)
- OIDC compatibility path for hosted/redirect login (swap issuer config, keep redirect flow intact)
- Okta CIS feature mappings: Sign-On Policies → Flows, Authorization Servers → Resources/Inbound Apps, Authenticators → Auth Methods, Identity Providers → Tenant SSO, Log Streams → Audit Connectors
- Inbound Apps vs. Federated Apps decision (scope-enforcing vs. identity-only)
scp→scopeclaim migration- Session validation patterns and dual-token validation for phased rollouts
Output:
MIGRATION-PLAN.mdfor human review before any code changes- SDK replacement across all auth touchpoints in the codebase
- Descope Flow and Console configuration guidance
Workflow: MCP check → migration plan (human review) → execution. Never skips ahead.
workos-to-descope — Migrate applications from WorkOS to Descope
Guides self-service migrations from WorkOS to Descope across any language or framework. WorkOS is a B2B/enterprise-readiness platform — not just auth — so the skill first identifies which WorkOS features are in use, maps each to Descope, analyzes auth touchpoints, produces a reviewed MIGRATION-PLAN.md, then executes the migration. Uses the Descope Docs MCP when available to verify SDK method names and option shapes.
Use when:
- "Migrate my app from WorkOS to Descope"
- "Replace WorkOS with Descope"
- "Our app uses @workos-inc/node / @workos-inc/authkit-nextjs / AuthKit — switch to Descope"
- "How do WorkOS Organizations / Enterprise SSO / Directory Sync / Admin Portal map to Descope?"
- "We're moving off WorkOS"
Covers:
- SDK replacement for all major frameworks (Next.js, React, Express, Python, Go, Ruby, etc.)
- WorkOS feature mappings: AuthKit → Descope Flows, Organizations → Tenants, Enterprise SSO → Tenant SSO, Directory Sync/SCIM → Descope SCIM, Admin Portal → SSO Setup Suite / Widgets, RBAC, FGA → ReBAC/AuthZ, Audit Logs, Radar, Pipes → Outbound Apps
- Tenant routing / home realm discovery (domain-based vs. explicit tenant slug)
- Descope Flow, Widget, and SSO Setup Suite setup (console-first approach)
- OIDC compatibility path for incremental migration
- Session validation patterns and WorkOS-specific gotchas (JWT claims, sealed sessions, SCIM lifecycle)
Output:
MIGRATION-PLAN.mdfor human review before any code changes- SDK replacement across all auth touchpoints in the codebase
- Descope Flow, Widget, and Console configuration guidance
Workflow: MCP check → migration plan (human review) → execution. Never skips ahead.
stytch-to-descope — Migrate applications from Stytch to Descope
Guides self-service migrations from Stytch to Descope across any language or framework. Stytch is an identity platform spanning consumer auth, B2B organizations, enterprise SSO, fraud/risk, and Connected Apps, so the skill first identifies which Stytch product surfaces are in use, maps each to Descope, analyzes auth touchpoints, produces a reviewed MIGRATION-PLAN.md, then executes the migration. Uses the Descope Docs MCP when available to verify SDK method names and option shapes.
Use when:
- "Migrate my app from Stytch to Descope"
- "Replace Stytch with Descope"
- "Our app uses stytch / @stytch/nextjs / Stytch UI / Stytch SSO / Connected Apps / SCIM — switch to Descope"
- "How do Stytch Organizations / Enterprise SSO / SCIM / Connected Apps / Admin Portal map to Descope?"
- "We're moving off Stytch"
Covers:
- SDK replacement for all major frameworks (Next.js, React, Python, Go, Ruby, etc.)
- Stytch feature mappings: Consumer/B2B Auth → Descope Flows, Stytch UI → Flows/Widgets, Organizations/Members → Tenants/Users, Enterprise SSO → Tenant SSO, SCIM → Descope SCIM, Admin Portal → SSO Setup Suite / Widgets, RBAC → Descope RBAC, Connected Apps (first-party → Federated Apps, third-party → Inbound Apps), M2M → Access Keys, Fraud & Risk / Protected Auth → Flow-based security connectors, Trusted Auth Tokens, webhooks → Audit Webhook
- Descope Flow, Widget, and SSO Setup Suite setup (console-first approach)
- User/org export from Stytch and password hash migration
- Session validation patterns and Stytch-specific gotchas (session_token vs. session_jwt, organization_id claims, Approved Domains)
Output:
MIGRATION-PLAN.mdfor human review before any code changes- SDK replacement across all auth touchpoints in the codebase
- Descope Flow, Widget, and Console configuration guidance
Workflow: MCP check → migration plan (human review) → execution. Never skips ahead.
pingone-to-descope — Migrate PingOne CIAM to Descope
Guides self-service migrations from PingOne for Customers / PingOne CIAM to Descope. CIAM-only: it first confirms customer-identity scope, then inventories PingOne surfaces (apps, populations, policies, DaVinci, Protect, Verify, SSO/SCIM), analyzes the codebase, produces a reviewed MIGRATION-PLAN.md, and executes only after approval. Uses the Descope Docs MCP when available to verify SDK method names and option shapes. Stops for workforce IAM, PingFederate, PingDirectory, PingAccess, PingID, or ForgeRock/AIC unless those are explicitly in scope.
Use when:
- "Migrate PingOne to Descope" / "PingOne CIAM to Descope"
- "Replace PingOne for Customers with Descope"
- "Move DaVinci flows to Descope"
- "How do PingOne populations / Protect / Verify / customer SSO map to Descope?"
- "We're moving off PingOne"
Covers:
- Path selection: Federated App / protocol-config swap, Descope SDK + Flow, or journey/config (DaVinci/policies) migration — mixed paths supported
- Feature mappings: Applications → Federated Apps or SDK/Flow; Populations → Tenants / attributes / Flow branches (not automatic tenants); Auth policies & DaVinci → Descope Flows; MFA → Flow MFA/step-up; Protect → fingerprinting
riskInfo+ Fraud & Risk Connectors; Verify → external IDV (e.g. Incode) via Flow; Customer SSO/SCIM → tenant SSO / SCIM; Authorize → RBAC/FGA or app-side authz; Worker apps → Management API or Access Keys/M2M - Client orchestration SDK replacement where present (Swift/iOS, Kotlin/Android, JS/TS, React Native) and protocol/token validation updates for backends without Ping SDKs
- User export/import with password cutover (no PingOne password/hash export — first-login reset or passwordless)
- Console-first setup: Flows, Widgets, JWT Templates, SSO Setup Suite, tenants
Output:
MIGRATION-PLAN.mdfor human review before any code changes- Code/config changes across confirmed auth touchpoints
- Descope Flow, Federated App, and Console configuration guidance
Workflow: MCP check → CIAM scope guard → migration plan (human review) → execution. Never skips ahead.
frontegg-to-descope — Migrate applications from Frontegg to Descope
Guides self-service migrations from Frontegg to Descope across any language or framework. Frontegg is a B2B SaaS identity platform spanning hosted and embedded login, Accounts (tenants), Environments, Applications, a broad end-customer self-service portal, RBAC, ReBAC, entitlements, prehooks, and M2M — so the skill first identifies which Frontegg surfaces are in use, maps each to Descope, analyzes auth touchpoints, produces a reviewed MIGRATION-PLAN.md, then executes the migration. Uses the Descope Docs MCP when available to verify SDK method names and option shapes.
Use when:
- "Migrate my app from Frontegg to Descope"
- "Replace Frontegg with Descope"
- "Our app uses frontegg / @frontegg/react / @frontegg/nextjs / FronteggProvider / the Frontegg admin portal — switch to Descope"
- "How do Frontegg Accounts / entitlements / prehooks / the self-service portal map to Descope?"
- "We're moving off Frontegg"
Covers:
- Hosted vs. embedded login-box detection, driving the Descope-hosted login (
oidcConfig) vs. embedded Flow decision - Feature mappings: login box → Flows, self-service portal → Widgets + SSO Setup Suite, Accounts → Tenants, Environments → Projects, Applications → Projects/Federated Apps/Inbound Apps, RBAC → Descope RBAC, ReBAC (self-hosted SpiceDB) → managed Descope ReBAC, prehooks → Flow steps/Connectors/JWT Templates, security rules → Flow-based security, SCIM → Descope SCIM, M2M → Resources + Inbound Apps + Policies or Access Keys, Frontegg AI integrations → Outbound Apps
- User and account migration via an agent-written export/import script (with the Descope migration tool's Frontegg module as a reference), plus both JIT paths (Generic HTTP Connector to preserve passwords, or Frontegg as a custom OIDC provider) and dual token validation during cutover
- Detection patterns across Frontegg's frontend, backend, and mobile SDKs (React, Next.js, Vue, Angular, JS, Node, Python, Go, Java entitlements, iOS, Android, React Native, Flutter, Ionic) plus .NET apps with no Frontegg SDK
- Frontegg-specific gotchas: no password-hash export,
fe_refresh/fe_sessioncookies,tenantId/tenantIds→dct/tenants,audvalidation,X-API-KEYvs.Authorization, hardcoded public keys, role levels and sub-accounts with no Descope equivalent - Scope guards for entitlements, plans, and feature flags — flagged, not silently rebuilt
Output:
MIGRATION-PLAN.mdfor human review before any code changes- Code/config changes across confirmed auth touchpoints
- Descope Flow, Widget, and Console configuration guidance
Workflow: MCP check → scope guard → migration plan (human review) → execution. Never skips ahead.
azure-ad-b2c-to-descope — Migrate applications from Azure AD B2C to Descope
Guides self-service migrations from Azure AD B2C to Descope across any language or framework. Detects how the app reaches B2C (MSAL redirect/popup, server-side OIDC, embedded iframe sign-in, ROPC), replaces MSAL and Microsoft.Identity.Web with the Descope SDK or a standard OIDC library (hosted login by default), keeps B2C-style scoped API access via Inbound Apps + Resources, optionally reads the B2C tenant through read-only Microsoft Graph, produces a reviewed MIGRATION-PLAN.md, then executes the migration. Uses the Descope Docs MCP when available to verify SDK method names and option shapes.
Use when:
- "Migrate my app from Azure AD B2C to Descope"
- "We're moving off B2C" / "B2C end of sale"
- "Our app uses @azure/msal-react / @azure/msal-angular / Microsoft.Identity.Web with b2clogin.com — switch to Descope"
- "How do B2C user flows / custom policies / API connectors / identity providers map to Descope?"
Covers:
- MSAL replacement for React, Angular, Next.js, Vue, plain JS; server-side web apps (.NET, Node, Python, Java); native apps
- App registrations → Inbound Apps + Resources (same scope names,
scp→scope), client-credentials apps → Inbound Apps - User flows and custom policies → Flows; API connectors / REST technical profiles → HTTP Connectors
- Token claim mapping (
oid,emails,tfp,extension_*) and JWT Templates - User export via Microsoft Graph, password strategies (no hash export; JIT via ROPC), social and enterprise SSO user import without duplicates
- Enterprise IdPs → tenant SSO with a per-connection cutover inventory (custom domain, secrets, certificates, MFA behavior)
Output:
MIGRATION-PLAN.mdfor human review before any code changes- SDK replacement across all auth touchpoints in the codebase
- Descope Flow, Inbound App/Resource, tenant SSO, and Console configuration guidance
Workflow: MCP check → migration plan (human review) → execution. Never skips ahead.
descope-fga-schema — Author and apply Descope FGA authorization schemas
Author, edit, and apply Descope FGA schemas using the ReBAC/ABAC DSL. Validates changes via dry run before applying, warns on data loss, and requires user confirmation before modifying live schema. Requires the Descope Management MCP.
Use when:
- "/descope-fga-schema"
- "Set up authorization / define roles and permissions"
- "Add team-based access control"
- "Create a new FGA schema"
- "Update my authorization model"
- "Add types/relations/permissions/conditions to my schema"
Covers:
- Full DSL grammar (
model AuthZ 1.0, types, relations, permissions, conditions) - ReBAC (relationship-based) and ABAC (attribute-based) patterns
- Dry-run validation before applying
- Data loss detection and warnings
- Reading current schema before edits
Requirements:
- Descope Management MCP installed and authorized
descope-byos-builder — Build React BYOS custom UI on top of Descope flows
Translate Descope flow JSON exports into working React BYOS screens that call state.next(interactionId, form). Parses real interaction IDs, form-key name props, screen names, and subflow loaders from your exported flow JSON — so every generated component is grounded in the actual flow, not guesswork. Includes a 19-entry failure catalog covering every silent-failure mode observed in real BYOS sessions.
Use when:
- "Build custom UI over my Descope flow"
- "My BYOS button does nothing" / "session is still anonymous after sign-in"
- "no handler for screen" errors at runtime
- "passkey ceremony aborts" / "WebAuthn hangs"
- Updating a BYOS implementation after the flow changed in the Descope console
- Adding post-auth promotion subflows (e.g. passkey enrollment after login)
What the skill does:
- Reads the main flow and every subflow through the Descope MCP Server when connected, otherwise asks for exported flow JSONs, before generating anything
- Runs
parse-flow.mjsto extract screen names, interaction IDs, inputnameprops, next-rules, and subflow loaders - Generates per-screen React components with correct
state.next(interactionId, payload)signatures - Detects shared screen-name collisions and writes router components with documented disambiguation heuristics
- References the failure catalog before diagnosing any "doesn't work" symptom
Required inputs (skill asks for these before starting):
- Flow JSON exports — main flow + every invoked subflow, including post-auth promotion subflows
- Descope Project ID + base URL
- Mount point in the React app
- Existing BYOS code paths (if modifying)
Iron rule: Ground every BYOS component in the exported flow JSON. Do not guess interaction IDs, output key names, or screen names.
Using skills CLI
npx skills add descope/skillsUsing Claude Code
Add the marketplace and install the plugin:
/plugin marketplace add descope/skills
/plugin install descope-skills
Using Cursor
Install from the Cursor Marketplace. In Cursor, run:
/add-plugin descope-skills
Or open the Marketplace panel (or visit cursor.com/marketplace), search for Descope, and install.
The repo ships a Cursor plugin manifest (.cursor-plugin/), so it installs as a single descope-skills plugin that bundles every skill under skills/.
Skills are automatically loaded by compatible AI agents once installed. Simply describe what you need:
descope-auth examples
Add Descope authentication to my Next.js app
Help me implement passkey login with Descope
Set up backend session validation for my Node.js API
Add OAuth login (Google and GitHub) using Descope
auth0-to-descope examples
Migrate my Next.js app from nextjs-auth0 to Descope
How do I replace Auth0 Actions with Descope?
Help me migrate our Auth0 Organizations setup to Descope
Our Express API uses express-openid-connect — how do we switch to Descope?
okta-cis-to-descope examples
Migrate my React app from @okta/okta-react to Descope
Our Express app uses @okta/oidc-middleware — how do we switch to Descope?
How do Okta Sign-On Policies and Authorization Servers map to Descope?
Help me migrate our Okta Identity Providers (per-tenant SSO) to Descope
azure-ad-b2c-to-descope examples
Migrate my React app from @azure/msal-react and Azure AD B2C to Descope
Our ASP.NET Core API uses Microsoft.Identity.Web with AzureAdB2C — how do we validate Descope tokens instead?
How do our B2C custom policies and API connectors map to Descope Flows?
We have enterprise customers on SAML through B2C — what changes for their IT admins when we move to Descope?
descope-terraform examples
Set up Terraform to manage my Descope project
Create a Descope project with password auth and RBAC using Terraform
Add an HTTP connector and S3 audit logging to my Descope Terraform config
descope-byos-builder examples
Build custom login screens over my Descope sign-up-or-in flow
My BYOS submit button does nothing — no errors in the console
Getting "no handler for screen" after the user clicks Forgot Password
Session is still anonymous after onSuccess fires
Add passkey promotion screens that run after the user logs in
auth-review examples
/auth-review
Audit my app for authentication and authorization vulnerabilities
Find IDOR and broken access control bugs in this repo
Run an identity security review before I ship
descope-fga-schema examples
/descope-fga-schema
Define an FGA schema with users, organizations, and resource-level permissions
Add a condition to my FGA schema that checks attribute values
Update my authorization model to support team-based access control
Works with any agent supporting the Agent Skills format:
- Claude Code (Anthropic)
- OpenCode (OhMyOpenCode)
- Cursor
- Cline
- GitHub Copilot
- Windsurf
- And 36+ more agents
Skill Structure
skills/
├── descope-auth/
│ ├── SKILL.md - Main instructions with framework detection
│ └── references/
│ ├── nextjs.md - Next.js App Router patterns
│ ├── react.md - React SPA patterns
│ ├── kotlin.md - Kotlin / Android patterns
│ ├── swift.md - Swift / iOS patterns
│ └── backend.md - Node.js/Python validation
├── auth0-to-descope/
│ ├── SKILL.md - Three-phase migration workflow (MCP check, plan, execution)
│ └── references/
│ ├── implementation-nuances.md - Per-framework migration patterns and gotchas
│ └── flows-and-widgets.md - Descope terminology, Flow/Widget guides, console-vs-code
├── okta-cis-to-descope/
│ ├── SKILL.md - Three-phase migration workflow (MCP check, plan, execution)
│ └── references/
│ ├── implementation-nuances.md - Per-framework patterns, OIDC path, scp/scope, gotchas
│ ├── flows-and-widgets.md - Okta→Descope lingo map, Flow/Widget guides, console-vs-code
│ └── backend-sdks.md - Python and Java backend migration patterns
├── frontegg-to-descope/
│ ├── SKILL.md - Three-phase migration workflow (MCP check, plan, execution)
│ └── references/
│ ├── implementation-nuances.md - Per-framework patterns, user export/JIT paths, ReBAC and prehook mapping, gotchas
│ ├── flows-and-widgets.md - Frontegg→Descope lingo map, self-service portal mapping, Flow/Widget guides
│ └── frontegg-detection-patterns.md - Codebase search commands and known Frontegg env vars
├── azure-ad-b2c-to-descope/
│ ├── SKILL.md - Three-phase migration workflow (MCP check, plan, execution)
│ └── references/
│ ├── implementation-nuances.md - B2C feature mapping, claims, user/SSO migration, framework sections
│ ├── flows-and-widgets.md - B2C→Descope lingo map, Flow/Widget guides, console-vs-code
│ ├── backend-sdks.md - .NET, Node.js, Python, Java API validation patterns
│ └── b2c-detection-patterns.md - Code search, read-only Graph discovery, SSO inventory template
├── descope-terraform/
│ ├── SKILL.md - Provider setup, common configurations, and guardrails
│ └── references/
│ ├── project-resource.md - Full descope_project schema
│ ├── other-resources.md - descope_management_key and descope_descoper schemas
│ └── connectors.md - All 60+ supported connector types
├── auth-review/
│ ├── SKILL.md - Four-phase workflow, severity scale, guardrails
│ └── references/
│ ├── enumeration.md - Entrypoint patterns across HTTP/GraphQL/WebSocket/RPC/serverless/queues
│ ├── vulnerability-catalog.md - AuthN, tokens, sessions, IDOR/BOLA, OAuth, recovery, MFA, CSRF/CORS
│ ├── authz-matrix.md - Matrix schema and expected-principal inference rules
│ └── report-template.md - Exact report structure and issue-ready finding format
├── descope-fga-schema/
│ └── SKILL.md - DSL grammar, dry-run workflow, data loss guards
└── descope-byos-builder/
├── SKILL.md - Workflow, iron rule, critical rules, collision heuristics, red flags
├── parse-flow.mjs - Node parser: extracts screen tasks, interaction IDs, form-key name props, subflow loaders
└── references/
├── byos-component-patterns.md - Core wiring, screen router, skeleton, and common screen examples
└── gotchas.md - 19 silent-failure modes with symptom → root cause → fix, plus pre-ship checklist
- Create a free account on our Sign Up page
- Get your Project ID: connect the Descope MCP Server (
https://mcp.descope.com) and your agent can pick or create a project for you, or copy it from Settings → Project - Install the skills via
npx skills add descope/skillsor the/plugincommand in Claude Code - Ask your AI agent to integrate Descope authentication or set up Terraform
- Descope Documentation
- Descope Flows Guide
- Authentication Methods
- API Reference
- Terraform Provider
- Managing Environments with Terraform
- BYOS (Bring Your Own Screen)
- BYOS Sample App
Contributions are welcome! See CONTRIBUTING.md for guidelines.
MIT License - see LICENSE file for details.
Descope provides passwordless authentication and user management for developers. Build secure, frictionless authentication flows with our no-code Flow Builder and developer-friendly SDKs.
Made with 💜 by Descope