What problem does it solve? Choosing between Salesforce's Mobile SDK and Agentforce SDK across iOS and Android is confusing, and picking the wrong starting point wastes setup time. This Skill disambiguates the user's intent and routes them to the correct platform- and SDK-specific child skill. ## Core Features & Use Cases - SDK family routing: Distinguishes Mobile SDK needs (authentication, MobileSync, SmartStore offline storage, push, biometrics) from Agentforce SDK needs (embedded agent chat, conversational UI). - Platform routing: Directs iOS (Swift) requests to ios-mobile-sdk or integrate-agentforce-ios, and Android (Kotlin) requests to android-mobile-sdk or integrate-agentforce-android. - Combined workflows: Sequences Mobile SDK scaffolding first, then layers the Agentforce SDK agent surface, without interleaving their setup steps. - Use Case: A user says "add Salesforce login and offline storage to my Android app" — the Skill routes to android-mobile-sdk, installs it via npx skills add if missing, and hands off the step-by-step implementation. ## Quick Start Ask the assistant to build a Salesforce iOS app with Mobile SDK authentication and offline sync, and it will route you to the right child skill.