pingidentity/ping-identity-pingone
Agent plugin for PingOne. App-integration guidance for connecting web, mobile, and backend applications to a PingOne environment (SDK wiring, OIDC/PKCE, CORS, Worker applications), DaVinci flow design guidance for building flows (registration, login, MFA, step-up, passkeys), MCP-backed troubleshooting for live DaVinci flow executions, and audit-event investigation for platform operations (failed logins, admin actions, compliance history, correlation IDs). Requires a PingOne environment and a registered OAuth client for live MCP operations.
Use when designing or building a PingOne DaVinci flow — registration with email verification, login, MFA enrollment and step-up, passwordless and passkey flows, progressive profiling, social login, subflow composition, error-path design, and preparing flows and connector credentials for promotion between environments. Produces flow designs and connector wiring as artifacts.
Use when tracing, debugging, or explaining a PingOne DaVinci flow execution failure.
Use when writing code that integrates an application with PingOne (multi-tenant) — Ping SDK setup for Android, iOS, and JavaScript/React, OIDC authorization code + PKCE against auth.pingone.com, DaVinci client and collector rendering, CORS configuration before in-browser token exchange, Worker applications and client_credentials or token exchange for backends, push MFA device registration, and app-side troubleshooting (redirect_uri_mismatch, CORS token failures, ForgeRock-to-Ping SDK migration).
Use this skill whenever a user needs a PingOne audit-event investigation: failed logins, authentication history, admin actions, compliance or event-history queries, correlation IDs, resource events, password or MFA events, pagination, or a BOM-based hint about DaVinci execution troubleshooting.