PingOne CIAM -> Descope Migration Skill

This skill guides migrations from PingOne for Customers / PingOne CIAM to Descope. It runs in three parts:

1. MCP Check - confirm whether the Descope MCP Server is available
2. Migration Plan - confirm CIAM scope, triage PingOne surfaces, analyze the codebase, and write MIGRATION-PLAN.md
3. Execution - only after the user reviews the plan, execute with MIGRATION-STATE.md continuity

Do not collapse these parts or skip ahead. The plan must be reviewed before code changes begin.

Primary references in this skill (detailed in Reference Files at the end):

• references/pingone-detection-patterns.md - what to search for and optional PingOne API discovery routes
• references/implementation-nuances.md - how to implement each path

Scope