Guides and TutorialsAI Assistants

Descope Agent Skills

Descope Agent Skills are instruction packs that teach AI coding agents Descope-specific workflows. They cover correct SDK patterns, Console setup steps, migration mappings, and guardrails that reduce hallucinated APIs and insecure auth code. The skills work with Cursor, Claude Code, GitHub Copilot, Windsurf, OpenCode, and 36+ compatible tools.

Descope Skills follow the open Agent Skills format. Each skill is a directory with a SKILL.md file that describes when to use the skill and what steps to follow, plus any supporting files. Because the format is an open standard, the same skill works in every agent that supports it.

Why Agent Skills

An MCP tool gives your agent one action, such as reading a user or importing a flow. Most Descope work takes several of those actions in a set order, with checks between them. A migration from Auth0, for example, needs a plan, an SDK swap, and a mapping of Actions to Flows before any code changes.

A skill carries that procedure. Your agent loads the skill only when the task matches its description, so the instructions don't take up context the rest of the time.

Skills + MCP

Skills encode how to do Descope work: multi-step workflows, framework detection, and safety checks.

The Descope MCP Server gives your agent live access. Your agent can search docs, query your project, manage users and flows, and (for some skills) apply FGA schema changes.

Migration and FGA skills call the MCP server when it is available, to check SDK method names and option shapes against current documentation.

Getting the Skills

You can get Descope Agent Skills in two ways. The MCP server delivers them with no install step, and a local install works in any agent that supports Agent Skills.

Over the Descope MCP Server

The Descope MCP Server supports the Skills over MCP standard, the official MCP extension io.modelcontextprotocol/skills. If your MCP client supports the extension, it discovers Descope skills with skills/list when it connects to the server. Your agent then loads the skill that matches the task.

With this option you don't install or update anything locally. See Agent Skills on the MCP server page for details.

Local Install

If your client doesn't support Skills over MCP yet, you can install the full collection from the official descope/skills repository:

npx skills add descope/skills

In Claude Code, you can add the marketplace plugin instead:

/plugin marketplace add descope/skills
/plugin install descope-skills

Once installed, skills load automatically. You describe what you need in natural language, and you don't need slash commands unless a skill below says so.

Available Skills

The skills fall into four groups: authentication and custom UI, migration, authorization and infrastructure, and security review.

Authentication & Custom UI

SkillUse for
descope-authAdd Descope login to your app with passwordless OTP, magic link, passkeys, OAuth, SSO, MFA, and passwords. The skill detects Next.js, React, Node.js, and Python and routes to the right integration guide.
descope-byos-builderBuild Bring Your Own Screen (BYOS) React UI on top of Descope Flows. The skill parses exported flow JSON for real interaction IDs and form keys, which avoids silent BYOS failures.

Example prompts

  • "Add Descope authentication to my Next.js app"
  • "Help me implement passkey login with Descope"
  • "My BYOS submit button does nothing, and there are no errors in the console"
  • "Build custom login screens over my Descope sign-up-or-in flow"

Migration

Each migration skill is self-service and produces a MIGRATION-PLAN.md for you to review before it changes any code.

SkillUse for
auth0-to-descopeMigrate from Auth0: SDK replacement, Actions → Flows, Organizations → Tenants, Token Vault, CIBA, and SSO.
okta-cis-to-descopeMigrate from Okta Customer Identity Service (CIS): hosted OIDC and embedded widget paths, Sign-On Policies → Flows, Authorization Servers → Resources/Inbound Apps, and scp → scope claim updates.
workos-to-descopeMigrate from WorkOS: AuthKit → Flows, Organizations → Tenants, Enterprise SSO → Tenant SSO, Directory Sync/SCIM → Descope SCIM, and Admin Portal → SSO Setup Suite / Widgets.
stytch-to-descopeMigrate from Stytch: Consumer/B2B auth → Flows, Organizations/Members → Tenants/Users, Enterprise SSO → Tenant SSO, SCIM, Connected Apps → Federated/Inbound Apps, and M2M → Access Keys.
pingone-to-descopeMigrate from PingOne CIAM: DaVinci flows → Descope Flows and connectors, Populations/Groups → Tenants/Roles, External IdPs → tenant SSO, OIDC/SAML Web Apps → Federated Apps, and Worker Apps → Management Keys.

Example prompts

  • "Migrate my Next.js app from nextjs-auth0 to Descope"
  • "How do Auth0 Actions map to Descope?"
  • "Our Express app uses @okta/oidc-middleware. How do we switch to Descope?"
  • "How do Okta Authorization Servers map to Descope Resources?"
  • "Migrate my app from WorkOS to Descope. We use @workos-inc/authkit-nextjs"
  • "How do WorkOS Organizations, Enterprise SSO, and Directory Sync map to Descope?"
  • "Migrate my Next.js app from stytch/nextjs to Descope"
  • "How do Stytch Organizations, Connected Apps, and RBAC map to Descope?"
  • "How do PingOne Environments, Populations, and Groups map to Descope?"
  • "Migrate my iOS Swift app from using Ping SDKs to Descope."

Authorization & Infrastructure

SkillUse for
descope-fga-schemaAuthor and apply FGA schemas using the ReBAC/ABAC DSL. The skill runs dry-run validation, warns about data loss, and asks for your confirmation before live changes. Requires the Descope MCP Server.
descope-terraformManage Descope projects as code with the Terraform provider. The skill covers auth methods, RBAC, connectors, flows, and project settings across environments.

Example prompts

  • "Define an FGA schema with users, organizations, and resource-level permissions"
  • "Set up Terraform to manage my Descope project"
  • "Create roles and permissions with Terraform"

Security Review

SkillUse for
auth-reviewRun a static identity security review. The skill lists routes, builds an authorization matrix, and triages auth and authz findings (IDOR, JWT flaws, session issues, OAuth gaps). It writes ./auth-review/report-YYYY-MM-DD.md and doesn't change code.

Example prompts

  • "/auth-review"
  • "Audit my app for authentication and authorization vulnerabilities"
  • "Find IDOR and broken access control bugs in this repo"

For the best experience working with Descope in an AI-powered IDE, you would set up three things:

  1. Connect the Descope MCP Server. It gives your agent project management, docs search, and live API access. If your client supports Skills over MCP, this step also delivers the skills.
  2. Install Descope Skills locally if your client doesn't support Skills over MCP. The skills add structured workflows for integration, migration, FGA, Terraform, and security review.
  3. Create a Descope project. You can find your Project ID in Settings → Project.

Skills handle implementation patterns, and MCP fills in current docs and project state. Migration skills check for MCP availability before they run, so SDK calls stay accurate.

Was this helpful?

On this page