{
  "markdown": "# Descope Skills\n\nA collection of AI agent skills for integrating Descope authentication into your applications. Skills follow the [Agent Skills](https://agentskills.io/) format and work with any compatible AI coding assistant.\n\n## Available Skills\n\n<details>\n<summary><b>descope-auth</b> — Integrate Descope authentication into applications</summary>\n\nIntegrate 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.\n\n**Use when:**\n- \"Add authentication to my app\"\n- \"Implement login with Descope\"\n- \"Set up passwordless auth\"\n- \"Add OAuth/SSO to my application\"\n- \"Integrate passkeys\"\n\n**Frameworks supported:**\n- Next.js (App Router with middleware)\n- React (SPA with protected routes)\n- Node.js (backend session validation)\n- Python (backend session validation)\n\n**Features:**\n- **Framework detection** - Automatically routes to appropriate integration guide\n- **Security guardrails** - Prevents common authentication mistakes\n- **Skills.sh compliant** - Follows official specification\n- **Copy-paste ready** - All code examples use correct SDK imports\n\n**Authentication methods covered:**\n- OTP (Email/SMS) - Quick verification codes\n- Magic Link - Passwordless email links\n- Passkeys - Biometric/WebAuthn (most secure)\n- OAuth - Social login (Google, GitHub, etc.)\n- SSO - Enterprise SAML/OIDC\n- TOTP - Authenticator app MFA\n- Passwords - Traditional auth (fallback)\n\n</details>\n\n<details>\n<summary><b>auth-review</b> — Static security review for authentication and authorization vulnerabilities</summary>\n\nFramework- 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.\n\n**Use when:**\n- \"/auth-review\"\n- \"Audit authentication in my app\"\n- \"Find authorization bugs / IDOR / BOLA\"\n- \"Review access control\"\n- \"Identity security review before release\"\n\n**Covers:**\n- Broken authentication (missing auth, weak password handling, SQLi-in-login, enumeration)\n- JWT / token flaws (`alg:none`, algorithm confusion, unverified decode, missing claim validation)\n- Session management (cookie flags, fixation, logout invalidation, predictable IDs)\n- Broken access control (IDOR / BOLA, BFLA, tenant crossing, client-trusted input)\n- Privilege escalation & mass assignment\n- OAuth / OIDC / SAML (state/PKCE, open redirect, ID-token validation, SAML XSW)\n- Password reset & account recovery (predictable/non-expiring tokens, host poisoning, MFA bypass)\n- MFA bypass and step-up gaps\n- Rate limiting & enumeration on auth surfaces\n- CSRF, CORS, identity-adjacent SSRF\n\n**Output:**\n- Triage report in `./auth-review/report-YYYY-MM-DD.md`\n- Endpoint inventory and authorization matrix\n- Findings with severity (High/Medium/Low), CWE, `file:line`, evidence, remediation\n- Pre-formatted issue bodies ready to paste into GitHub\n\n**Scope:** static and read-only. Does not run the target application, make network probes, modify code, or file issues directly.\n\n</details>\n\n<details>\n<summary><b>descope-terraform</b> — Manage Descope projects as infrastructure-as-code</summary>\n\nManage Descope projects as infrastructure-as-code using the official [Terraform provider](https://registry.terraform.io/providers/descope/descope/latest/docs). Generates valid HCL configurations for authentication methods, RBAC, connectors, and project settings.\n\n**Use when:**\n- \"Set up Terraform for my Descope project\"\n- \"Manage Descope authentication config as code\"\n- \"Create roles and permissions with Terraform\"\n- \"Add connectors to my Descope Terraform config\"\n- \"Deploy Descope project settings across environments\"\n\n**Resources managed:**\n- `descope_project` - Full project configuration (auth methods, RBAC, connectors, flows, settings)\n- `descope_management_key` - Management keys with RBAC scoping\n- `descope_descoper` - Console user accounts with role assignments\n\n**Covers:**\n- Provider setup and management key configuration\n- Authentication methods (OTP, Magic Link, Passkeys, OAuth, SSO, Password, TOTP)\n- Authorization (roles and permissions)\n- 60+ connector types (email, SMS, HTTP, observability, fraud detection, CRM, etc.)\n- Project settings, applications (OIDC/SAML), flows, JWT templates, and custom attributes\n\n**Requirements:**\n- Terraform CLI installed\n- Paid Descope License (Pro +)\n- Management Key from [Company Settings](https://app.descope.com/company)\n\n</details>\n\n<details>\n<summary><b>auth0-to-descope</b> — Migrate applications from Auth0 to Descope</summary>\n\nGuides 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.\n\n**Use when:**\n- \"Migrate my app from Auth0 to Descope\"\n- \"Replace Auth0 with Descope\"\n- \"Our app uses nextjs-auth0 / express-openid-connect / auth0-fastapi — switch to Descope\"\n- \"How do Auth0 Actions / Organizations / Token Vault map to Descope?\"\n- \"We're moving off Auth0\"\n\n**Covers:**\n- SDK replacement for all major frameworks (Next.js, React, Express, Python, etc.)\n- Auth0 feature mappings: Actions → Descope flows, Organizations → Tenants, Token Vault, CIBA\n- Descope Flow and Widget setup (console-first approach)\n- SSO and OIDC compatibility\n- Session validation patterns\n\n**Output:**\n- `MIGRATION-PLAN.md` for human review before any code changes\n- SDK replacement across all auth touchpoints in the codebase\n- Descope Flow and Widget integration\n\n**Workflow:** MCP check → migration plan (human review) → execution. Never skips ahead.\n\n</details>\n\n<details>\n<summary><b>okta-cis-to-descope</b> — Migrate applications from Okta CIS to Descope</summary>\n\nGuides 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.\n\n**Use when:**\n- \"Migrate my app from Okta to Descope\"\n- \"Replace Okta CIS with Descope\"\n- \"Our app uses okta-auth-js / @okta/okta-react / @okta/oidc-middleware / okta-jwt-verifier — switch to Descope\"\n- \"How do Okta Sign-On Policies / Authorization Servers / Authenticators / Log Streams map to Descope?\"\n- \"We're moving off Okta\"\n\n**Covers:**\n- SDK replacement for all major frameworks (React, Angular, Vue, Next.js, Express, Python, Java, and more)\n- OIDC compatibility path for hosted/redirect login (swap issuer config, keep redirect flow intact)\n- Okta CIS feature mappings: Sign-On Policies → Flows, Authorization Servers → Resources/Inbound Apps, Authenticators → Auth Methods, Identity Providers → Tenant SSO, Log Streams → Audit Connectors\n- Inbound Apps vs. Federated Apps decision (scope-enforcing vs. identity-only)\n- `scp` → `scope` claim migration\n- Session validation patterns and dual-token validation for phased rollouts\n\n**Output:**\n- `MIGRATION-PLAN.md` for human review before any code changes\n- SDK replacement across all auth touchpoints in the codebase\n- Descope Flow and Console configuration guidance\n\n**Workflow:** MCP check → migration plan (human review) → execution. Never skips ahead.\n\n</details>\n\n<details>\n<summary><b>workos-to-descope</b> — Migrate applications from WorkOS to Descope</summary>\n\nGuides 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.\n\n**Use when:**\n- \"Migrate my app from WorkOS to Descope\"\n- \"Replace WorkOS with Descope\"\n- \"Our app uses @workos-inc/node / @workos-inc/authkit-nextjs / AuthKit — switch to Descope\"\n- \"How do WorkOS Organizations / Enterprise SSO / Directory Sync / Admin Portal map to Descope?\"\n- \"We're moving off WorkOS\"\n\n**Covers:**\n- SDK replacement for all major frameworks (Next.js, React, Express, Python, Go, Ruby, etc.)\n- 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\n- Tenant routing / home realm discovery (domain-based vs. explicit tenant slug)\n- Descope Flow, Widget, and SSO Setup Suite setup (console-first approach)\n- OIDC compatibility path for incremental migration\n- Session validation patterns and WorkOS-specific gotchas (JWT claims, sealed sessions, SCIM lifecycle)\n\n**Output:**\n- `MIGRATION-PLAN.md` for human review before any code changes\n- SDK replacement across all auth touchpoints in the codebase\n- Descope Flow, Widget, and Console configuration guidance\n\n**Workflow:** MCP check → migration plan (human review) → execution. Never skips ahead.\n\n</details>\n\n<details>\n<summary><b>stytch-to-descope</b> — Migrate applications from Stytch to Descope</summary>\n\nGuides 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.\n\n**Use when:**\n- \"Migrate my app from Stytch to Descope\"\n- \"Replace Stytch with Descope\"\n- \"Our app uses stytch / @stytch/nextjs / Stytch UI / Stytch SSO / Connected Apps / SCIM — switch to Descope\"\n- \"How do Stytch Organizations / Enterprise SSO / SCIM / Connected Apps / Admin Portal map to Descope?\"\n- \"We're moving off Stytch\"\n\n**Covers:**\n- SDK replacement for all major frameworks (Next.js, React, Python, Go, Ruby, etc.)\n- 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\n- Descope Flow, Widget, and SSO Setup Suite setup (console-first approach)\n- User/org export from Stytch and password hash migration\n- Session validation patterns and Stytch-specific gotchas (session_token vs. session_jwt, organization_id claims, Approved Domains)\n\n**Output:**\n- `MIGRATION-PLAN.md` for human review before any code changes\n- SDK replacement across all auth touchpoints in the codebase\n- Descope Flow, Widget, and Console configuration guidance\n\n**Workflow:** MCP check → migration plan (human review) → execution. Never skips ahead.\n\n</details>\n\n<details>\n<summary><b>pingone-to-descope</b> — Migrate PingOne CIAM to Descope</summary>\n\nGuides 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.\n\n**Use when:**\n- \"Migrate PingOne to Descope\" / \"PingOne CIAM to Descope\"\n- \"Replace PingOne for Customers with Descope\"\n- \"Move DaVinci flows to Descope\"\n- \"How do PingOne populations / Protect / Verify / customer SSO map to Descope?\"\n- \"We're moving off PingOne\"\n\n**Covers:**\n- Path selection: Federated App / protocol-config swap, Descope SDK + Flow, or journey/config (DaVinci/policies) migration — mixed paths supported\n- 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\n- Client orchestration SDK replacement where present (Swift/iOS, Kotlin/Android, JS/TS, React Native) and protocol/token validation updates for backends without Ping SDKs\n- User export/import with password cutover (no PingOne password/hash export — first-login reset or passwordless)\n- Console-first setup: Flows, Widgets, JWT Templates, SSO Setup Suite, tenants\n\n**Output:**\n- `MIGRATION-PLAN.md` for human review before any code changes\n- Code/config changes across confirmed auth touchpoints\n- Descope Flow, Federated App, and Console configuration guidance\n\n**Workflow:** MCP check → CIAM scope guard → migration plan (human review) → execution. Never skips ahead.\n\n</details>\n\n\n<details>\n<summary><b>descope-fga-schema</b> — Author and apply Descope FGA authorization schemas</summary>\n\nAuthor, 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.\n\n**Use when:**\n- \"/descope-fga-schema\"\n- \"Set up authorization / define roles and permissions\"\n- \"Add team-based access control\"\n- \"Create a new FGA schema\"\n- \"Update my authorization model\"\n- \"Add types/relations/permissions/conditions to my schema\"\n\n**Covers:**\n- Full DSL grammar (`model AuthZ 1.0`, types, relations, permissions, conditions)\n- ReBAC (relationship-based) and ABAC (attribute-based) patterns\n- Dry-run validation before applying\n- Data loss detection and warnings\n- Reading current schema before edits\n\n**Requirements:**\n- Descope Management MCP installed and authorized\n\n</details>\n\n<details>\n<summary><b>descope-byos-builder</b> — Build React BYOS custom UI on top of Descope flows</summary>\n\nTranslate 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.\n\n**Use when:**\n- \"Build custom UI over my Descope flow\"\n- \"My BYOS button does nothing\" / \"session is still anonymous after sign-in\"\n- \"no handler for screen\" errors at runtime\n- \"passkey ceremony aborts\" / \"WebAuthn hangs\"\n- Updating a BYOS implementation after the flow changed in the Descope console\n- Adding post-auth promotion subflows (e.g. passkey enrollment after login)\n\n**What the skill does:**\n- Asks for exported flow JSONs (main flow + every subflow) before generating anything\n- Runs `parse-flow.mjs` to extract screen names, interaction IDs, input `name` props, next-rules, and subflow loaders\n- Generates per-screen React components with correct `state.next(interactionId, payload)` signatures\n- Detects shared screen-name collisions and writes router components with documented disambiguation heuristics\n- References the failure catalog before diagnosing any \"doesn't work\" symptom\n\n**Required inputs (skill asks for these before starting):**\n- Flow JSON exports — main flow + every invoked subflow, including post-auth promotion subflows\n- Descope Project ID + base URL\n- Mount point in the React app\n- Existing BYOS code paths (if modifying)\n\n**Iron rule:** Ground every BYOS component in the exported flow JSON. Do not guess interaction IDs, output key names, or screen names.\n\n</details>\n\n## Installation\n\n<details>\n<summary><b>Using skills CLI</b></summary>\n\n```bash\nnpx skills add descope/skills\n```\n\n</details>\n\n<details open>\n<summary><b>Using Claude Code</b></summary>\n\nAdd the marketplace and install the plugin:\n\n```\n/plugin marketplace add descope/skills\n/plugin install descope-skills\n```\n\n</details>\n\n<details>\n<summary><b>Using Cursor</b></summary>\n\nInstall from the Cursor Marketplace. In Cursor, run:\n\n```\n/add-plugin descope-skills\n```\n\nOr open the Marketplace panel (or visit [cursor.com/marketplace](https://cursor.com/marketplace)), search for **Descope**, and install.\n\nThe repo ships a Cursor plugin manifest (`.cursor-plugin/`), so it installs as a single `descope-skills` plugin that bundles every skill under `skills/`.\n\n</details>\n\n## Usage\n\nSkills are automatically loaded by compatible AI agents once installed. Simply describe what you need:\n\n<details>\n<summary><b>descope-auth examples</b></summary>\n\n```\nAdd Descope authentication to my Next.js app\n```\n\n```\nHelp me implement passkey login with Descope\n```\n\n```\nSet up backend session validation for my Node.js API\n```\n\n```\nAdd OAuth login (Google and GitHub) using Descope\n```\n\n</details>\n\n<details>\n<summary><b>auth0-to-descope examples</b></summary>\n\n```\nMigrate my Next.js app from nextjs-auth0 to Descope\n```\n\n```\nHow do I replace Auth0 Actions with Descope?\n```\n\n```\nHelp me migrate our Auth0 Organizations setup to Descope\n```\n\n```\nOur Express API uses express-openid-connect — how do we switch to Descope?\n```\n\n</details>\n\n<details>\n<summary><b>okta-cis-to-descope examples</b></summary>\n\n```\nMigrate my React app from @okta/okta-react to Descope\n```\n\n```\nOur Express app uses @okta/oidc-middleware — how do we switch to Descope?\n```\n\n```\nHow do Okta Sign-On Policies and Authorization Servers map to Descope?\n```\n\n```\nHelp me migrate our Okta Identity Providers (per-tenant SSO) to Descope\n```\n\n</details>\n\n<details>\n<summary><b>descope-terraform examples</b></summary>\n\n```\nSet up Terraform to manage my Descope project\n```\n\n```\nCreate a Descope project with password auth and RBAC using Terraform\n```\n\n```\nAdd an HTTP connector and S3 audit logging to my Descope Terraform config\n```\n\n</details>\n\n<details>\n<summary><b>descope-byos-builder examples</b></summary>\n\n```\nBuild custom login screens over my Descope sign-up-or-in flow\n```\n\n```\nMy BYOS submit button does nothing — no errors in the console\n```\n\n```\nGetting \"no handler for screen\" after the user clicks Forgot Password\n```\n\n```\nSession is still anonymous after onSuccess fires\n```\n\n```\nAdd passkey promotion screens that run after the user logs in\n```\n\n</details>\n\n<details>\n<summary><b>auth-review examples</b></summary>\n\n```\n/auth-review\n```\n\n```\nAudit my app for authentication and authorization vulnerabilities\n```\n\n```\nFind IDOR and broken access control bugs in this repo\n```\n\n```\nRun an identity security review before I ship\n```\n\n</details>\n\n<details>\n<summary><b>descope-fga-schema examples</b></summary>\n\n```\n/descope-fga-schema\n```\n\n```\nDefine an FGA schema with users, organizations, and resource-level permissions\n```\n\n```\nAdd a condition to my FGA schema that checks attribute values\n```\n\n```\nUpdate my authorization model to support team-based access control\n```\n\n</details>\n\n## Compatible Agents\n\nWorks with any agent supporting the Agent Skills format:\n\n- [Claude Code](https://code.claude.com) (Anthropic)\n- [OpenCode](https://opencode.ai) (OhMyOpenCode)\n- [Cursor](https://cursor.com)\n- [Cline](https://cline.bot)\n- [GitHub Copilot](https://github.com/features/copilot)\n- [Windsurf](https://windsurf.com)\n- And [36+ more agents](https://github.com/vercel-labs/skills#supported-agents)\n\n<details>\n<summary><b>Skill Structure</b></summary>\n\n```\nskills/\n├── descope-auth/\n│   ├── SKILL.md - Main instructions with framework detection\n│   └── references/\n│       ├── nextjs.md - Next.js App Router patterns\n│       ├── react.md - React SPA patterns\n│       └── backend.md - Node.js/Python validation\n├── auth0-to-descope/\n│   ├── SKILL.md - Three-phase migration workflow (MCP check, plan, execution)\n│   └── references/\n│       ├── implementation-nuances.md - Per-framework migration patterns and gotchas\n│       └── flows-and-widgets.md - Descope terminology, Flow/Widget guides, console-vs-code\n├── okta-cis-to-descope/\n│   ├── SKILL.md - Three-phase migration workflow (MCP check, plan, execution)\n│   └── references/\n│       ├── implementation-nuances.md - Per-framework patterns, OIDC path, scp/scope, gotchas\n│       ├── flows-and-widgets.md - Okta→Descope lingo map, Flow/Widget guides, console-vs-code\n│       └── backend-sdks.md - Python and Java backend migration patterns\n├── descope-terraform/\n│   ├── SKILL.md - Provider setup, common configurations, and guardrails\n│   └── references/\n│       ├── project-resource.md - Full descope_project schema\n│       ├── other-resources.md - descope_management_key and descope_descoper schemas\n│       └── connectors.md - All 60+ supported connector types\n├── auth-review/\n│   ├── SKILL.md - Four-phase workflow, severity scale, guardrails\n│   └── references/\n│       ├── enumeration.md - Entrypoint patterns across HTTP/GraphQL/WebSocket/RPC/serverless/queues\n│       ├── vulnerability-catalog.md - AuthN, tokens, sessions, IDOR/BOLA, OAuth, recovery, MFA, CSRF/CORS\n│       ├── authz-matrix.md - Matrix schema and expected-principal inference rules\n│       └── report-template.md - Exact report structure and issue-ready finding format\n├── descope-fga-schema/\n│   └── SKILL.md - DSL grammar, dry-run workflow, data loss guards\n└── descope-byos-builder/\n    ├── SKILL.md - Workflow, iron rule, critical rules, collision heuristics, red flags\n    ├── parse-flow.mjs - Node parser: extracts screen tasks, interaction IDs, form-key name props, subflow loaders\n    └── references/\n        ├── byos-component-patterns.md - Core wiring, screen router, skeleton, and common screen examples\n        └── gotchas.md - 19 silent-failure modes with symptom → root cause → fix, plus pre-ship checklist\n```\n\n</details>\n\n## Getting Started with Descope\n\n1. **Create a free account** on our [Sign Up page](https://www.descope.com/sign-up)\n2. **Get your Project ID** from [Settings → Project](https://app.descope.com/settings/project)\n3. **Install the skills** via `npx skills add descope/skills` or the `/plugin` command in Claude Code\n4. **Ask your AI agent** to integrate Descope authentication or set up Terraform\n\n## Documentation\n\n- [Descope Documentation](https://docs.descope.com)\n- [Descope Flows Guide](https://docs.descope.com/flows)\n- [Authentication Methods](https://docs.descope.com/auth-methods)\n- [API Reference](https://docs.descope.com/api)\n- [Terraform Provider](https://registry.terraform.io/providers/descope/descope/latest/docs)\n- [Managing Environments with Terraform](https://docs.descope.com/managing-environments/terraform)\n- [BYOS (Bring Your Own Screen)](https://docs.descope.com/build/guides/byos/)\n- [BYOS Sample App](https://github.com/descope-sample-apps/byos-sample-app)\n\n## Contributing\n\nContributions are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.\n\n## License\n\nMIT License - see [LICENSE](LICENSE) file for details.\n\n## About Descope\n\n[Descope](https://www.descope.com) provides passwordless authentication and user management for developers. Build secure, frictionless authentication flows with our no-code Flow Builder and developer-friendly SDKs.\n\n## Support\n\n- [Descope Community Slack](https://www.descope.com/community)\n- [Email Support](mailto:support@descope.com)\n\n---\n\nMade with 💜 by [Descope](https://www.descope.com)\n",
  "bytes": 23995,
  "sha": "a1ff9a42a5e4c38fb416c56859ce5e7a93a8bf0198be344e8b1f6ef29952970f",
  "repo_slug": "descope/skills",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_descope_skills_descope_skills_034d6afb/readme"
}