Mobile Apps Create

This is a router skill that figures out which Salesforce mobile SDK you need and hands you off to the right platform-specific guide. It disambiguates between Mobile SDK (for auth, offline sync, SmartStore) and Agentforce SDK (for embedding conversational agents), then routes you to iOS or Android child skills that do the actual work. If you're building a data-driven app with an embedded agent, it sequences both SDKs in the right order. The skill itself doesn't implement anything, it just asks clarifying questions and loads the correct downstream skill from GitHub repos. Honest take: this is workflow plumbing, not magic, but it saves you from guessing wrong and restarting with a different SDK halfway through setup.

skills.sh installs: 4.8K
GitHub stars: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill mobile-apps-create --agent claude-code

Installs into .claude/skills of the current project.

Files

Salesforce Mobile

Route the user to the right SDK-family skill for building Salesforce-connected mobile apps. Do not implement features here; child skills own scenario detection and step-by-step instructions.

Before routing

Disambiguate on two dimensions: SDK family (Mobile SDK vs. Agentforce SDK) and platform (iOS vs. Android). They are not mutually exclusive — an app can use both SDKs.

If the user's intent could plausibly map to either SDK, ask before routing. Guessing wrong wastes the user's time because the child skills are platform- and SDK-specific.

Routing — which SDK family?

User's situation	SDK
Authenticating end users to Salesforce, syncing records (MobileSync), storing data offline (SmartStore), biometric login, push notifications, REST integration	Mobile SDK
Embedding an Agentforce agent — chat UI, agent conversations, conversational features as the primary surface	Agentforce SDK
Both (data-driven app with an embedded agent)	Mobile SDK first, then Agentforce SDK layered on top