agentsclimarketplace
Sign in

Ping app integration

Skill pingidentity/agent-plugins/plugins/ping-identity/skills/ping-app-integration

Use when writing code or wiring an SDK to integrate Ping Identity into a web, mobile, or backend app — Android/iOS/JavaScript SDK installation, OIDC authorization code + PKCE flows, token management, ForgeRock-to-Ping SDK migration, and app-side troubleshooting (redirect_uri_mismatch, CORS, token refresh failures).From its SKILL.md

Install
npx -y skills add pingidentity/agent-plugins --skill ping-app-integration

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.1 KB, ~1.2k tokens by cl100k_base, as published. Nobody here has run it

ping-app-integration

Implementation skill for integrating Ping Identity into web, mobile, and application SDK experiences.

What this skill does for you: Generates app-side integration code — SDK wiring, OIDC/PKCE flows, token handling — and guides you through the SDK docs and troubleshooting where code generation alone is not enough. Primarily an artifact-generating skill.

Invocation

Invoke explicitly with /ping-app-integration or by saying "use ping-app-integration to...".

When to use this skill

  • "Integrate Ping into my React app using the orchestration SDK"
  • "Use the iOS SDK with AIC journeys"
  • "Wire OIDC redirect into a mobile app"
  • "Embed a journey in a webview"
  • "Migrate from the ForgeRock SDK to the Ping SDK"
  • "Add browser-based login to my web application"
  • "Connect my Android app to a DaVinci flow"
  • "App-side OIDC / OAuth configuration for PingFederate"
  • "Redirect URI mismatch error in my app"
  • "CORS error on the token endpoint"

When NOT to use this skill

  • Platform setup or app registration (no code): use ping-foundation.
  • Designing the flow or journey itself: use ping-orchestration.
  • General onboarding orientation: use ping-quickstart.

Multi-skill use cases

A complete app integration spans three layers — all are required for a production outcome:

LayerSkillTypical tasks
1. Platform setup + app registrationping-foundationTenant setup, redirect URI registration, sign-on policy
2. Journey or flow designping-orchestrationJourney nodes, DaVinci flows, MFA policy
3. SDK / app-side implementationping-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):

  1. Use ping-foundation to register an OIDC application in PingOne, configure the redirect URI (myapp://callback), and note the client ID and environment ID.
  2. Use ping-orchestration to build and test a DaVinci login flow with username/password and push MFA nodes.
  3. Use this skill (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.

Step 1: What are you trying to do?

TaskCurated reference
Overview: skill positioning, SDK landscape, integration lifecyclereferences/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 integrationreferences/curated/web-integration-basics.md
Generic OIDC web app or SAML integrationreferences/curated/web-integration-basics.md
Browser-based redirect / hosted loginreferences/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/429references/curated/server-side-integration-basics.md
Troubleshooting, migration (ForgeRock → Ping SDK)references/curated/integration-troubleshooting-basics.md

MCP execution

See references/runtime/mcp-preflight.md for MCP config and Cursor preflight steps.

Step 2: Retrieval escalation

  1. Curated anchors (references/curated/) — load 1–3 max. Stop if sufficient.
  2. For deep implementation work, delegate to the companion SDK skills below.

Companion SDK skills — ping-sdk-agent-skills

For deep implementation work (full code scaffolding, collector rendering, migration automation), delegate to the specialist skills in the pingidentity/ping-sdk-agent-skills plugin:

Specialist skillPlatform
ping-orchestration-sdk-routerDetects platform (Android/iOS/JS) and routes — use first when platform is ambiguous
ping-orchestration-android-sdkAndroid Kotlin / Jetpack Compose — Journey + DaVinci
ping-orchestration-ios-sdkiOS Swift / SwiftUI — Journey + DaVinci
ping-orchestration-reactjs-journey-sdkReact + AIC Journey flows
ping-orchestration-reactjs-davinci-sdkReact + PingOne DaVinci flows
ping-orchestration-javascript-sdkAngular / Vue / Vanilla JS
forgerock-to-ping-journey-migrationForgeRock SDK → Ping SDK automated migration

Install: https://github.com/pingidentity/ping-sdk-agent-skills

What ships with it: 8 files

76.8 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.