From ping-identity-agent-plugins
Use this skill whenever the task involves writing code or wiring an SDK to integrate Ping Identity into an application. Triggers: Android, iOS, or React/JavaScript SDK integration; embedding DaVinci flows or AIC journeys in a web or mobile app; OIDC authorization code + PKCE flow wiring; server-side backend OIDC (Node.js, Java, Python, .NET); token validation, refresh, and session management; client credentials (M2M) and token exchange patterns; redirect_uri_mismatch, CORS, token refresh failures, push MFA not delivering; migrating from ForgeRock SDK to Ping SDK; embedding a Ping service SDK (Protect JavaScript signals SDK, Verify mobile SDK) in app code; on-prem PingFederate or PingAccess agent integration. NOT for: configuring or invoking PingOne Verify, Protect, IGA, or Authorize at the service/policy level (use ping-universal-services); platform admin (use ping-foundation); flow design (use ping-orchestration). Also invoke with /ping-app-integration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ping-identity-agent-plugins:ping-app-integrationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Implementation skill for integrating Ping Identity into web, mobile, and application SDK experiences.
ping-marketplace.jsonreferences/curated/app-integration-overview.mdreferences/curated/integration-troubleshooting-basics.mdreferences/curated/mobile-integration-basics.mdreferences/curated/server-side-integration-basics.mdreferences/curated/web-integration-basics.mdreferences/runtime/mcp-preflight.mdImplementation skill for integrating Ping Identity into web, mobile, and application SDK experiences.
Invoke explicitly with /ping-app-integration or by saying "use ping-app-integration to...".
ping-foundation.ping-orchestration.ping-quickstart.A complete app integration spans three layers — all are required for a production outcome:
| Layer | Skill | Typical tasks |
|---|---|---|
| 1. Platform setup + app registration | ping-foundation | Tenant setup, redirect URI registration, sign-on policy |
| 2. Journey or flow design | ping-orchestration | Journey nodes, DaVinci flows, MFA policy |
| 3. SDK / app-side implementation | ping-app-integration (this skill) | SDK install, init, auth flow, token storage |
Complete platform setup first, then flow design, then hand off to this skill for SDK wiring.
End-to-end example (Android + DaVinci on PingOne):
ping-foundation to register an OIDC application in PingOne, configure the redirect URI (myapp://callback), and note the client ID and environment ID.ping-orchestration to build and test a DaVinci login flow with username/password and push MFA nodes.ping-app-integration) to add the com.pingidentity.sdks:davinci and com.pingidentity.sdks:oidc dependencies, initialize PingOne.init(context) with the client ID and discovery endpoint, call PingOne.startAuthentication(activity), and handle the AuthResult.| Task | Curated reference |
|---|---|
| Overview: skill positioning, SDK landscape, integration lifecycle | references/curated/app-integration-overview.md |
| Android SDK integration (Journey or DaVinci) | references/curated/mobile-integration-basics.md |
| iOS Swift SDK integration (Journey or DaVinci) | references/curated/mobile-integration-basics.md |
| React / JavaScript web integration | references/curated/web-integration-basics.md |
| Generic OIDC web app or SAML integration | references/curated/web-integration-basics.md |
| Browser-based redirect / hosted login | references/curated/web-integration-basics.md |
| On-prem app integration (PingFederate, PingAccess) | references/curated/web-integration-basics.md |
| Server-side / backend OIDC, M2M client_credentials, token exchange, CIBA, retry/429 | references/curated/server-side-integration-basics.md |
| Troubleshooting, migration (ForgeRock → Ping SDK) | references/curated/integration-troubleshooting-basics.md |
See references/runtime/mcp-preflight.md for MCP config and Cursor preflight steps.
references/curated/) — load 1–3 max. Stop if sufficient.ping-sdk-agent-skillsFor deep implementation work (full code scaffolding, collector rendering, migration automation), delegate to the specialist skills in the pingidentity/ping-sdk-agent-skills plugin:
| Specialist skill | Platform |
|---|---|
ping-orchestration-sdk-router | Detects platform (Android/iOS/JS) and routes — use first when platform is ambiguous |
ping-orchestration-android-sdk | Android Kotlin / Jetpack Compose — Journey + DaVinci |
ping-orchestration-ios-sdk | iOS Swift / SwiftUI — Journey + DaVinci |
ping-orchestration-reactjs-journey-sdk | React + AIC Journey flows |
ping-orchestration-reactjs-davinci-sdk | React + PingOne DaVinci flows |
ping-orchestration-javascript-sdk | Angular / Vue / Vanilla JS |
forgerock-to-ping-journey-migration | ForgeRock SDK → Ping SDK automated migration |
Install: https://github.com/pingidentity/ping-sdk-agent-skills
npx claudepluginhub pingidentity/agent-plugins --plugin ping-identityProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.