Mobile Apps Create

OrganizationPopular

forcedotcom

mobile-apps-create

The entry point for building any Salesforce native mobile app on iOS or Android. TRIGGER when the user says: "build a Salesforce iOS app", "add Salesforce login to my Android app", "set up Mobile SDK", "add MobileSync / SmartStore offline storage", "embed an Agentforce agent in my mobile app", "add Agentforce chat to iOS/Android", or otherwise asks to create, extend, or integrate a Salesforce mobile experience in Swift or Kotlin (MSDK, Agentforce SDK, or both). SKIP when the user is building a non-Salesforce mobile app, using React Native / Flutter / Ionic without Salesforce integration, asking about generic mobile UI design, or working on a Salesforce-adjacent web/desktop surface (LWC, Experience Cloud, Mobile Publisher branding-only).

Overview

Publisher	forcedotcom
Repository	`sf-skills`
Skill name	`mobile-apps-create`
Stars	1.1K
Forks	351
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by forcedotcom on GitHub. Read the source before you install it.

Installation

Install the Mobile Apps Create AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/forcedotcom/sf-skills/tree/main/plugins/builder/mobile-development/skills/mobile-apps-create
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/forcedotcom/sf-skills/tree/main/plugins/builder/mobile-development/skills/mobile-apps-create

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/forcedotcom/sf-skills.git /tmp/sf-skills
mkdir -p .claude/skills
cp -r /tmp/sf-skills/plugins/builder/mobile-development/skills/mobile-apps-create .claude/skills/mobile-apps-create

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mobile Apps Create in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Mobile Apps Create on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Mobile Apps Create is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Tiebreakers when both seem to apply

Is the agent the primary surface (chat-first app), or a feature inside an otherwise data-driven app?
- Primary → Agentforce SDK
- Feature → Mobile SDK; embed the agent via Agentforce SDK alongside it
Are end users authenticating into Salesforce data?
- Yes → Mobile SDK is required (Agentforce SDK can be added on top).
- No → Agentforce SDK alone is likely sufficient (it uses guest auth).
Asking about offline storage, sync, REST, push, or biometrics? → Mobile SDK.
Asking about agent conversations, chat UI, or streaming responses? → Agentforce SDK.

When still unclear, ask the user directly.

Routing — which platform?

Platform	Mobile SDK skill	Agentforce SDK skill
iOS (Swift)	`ios-mobile-sdk`	`integrate-agentforce-ios`
Android (Kotlin)	`android-mobile-sdk`	`integrate-agentforce-android`

If the user wants both platforms, route to each child skill separately — they are independent.

Combined workflows (Mobile SDK + Agentforce SDK)

When an app needs both:

Route to the Mobile SDK platform skill first to scaffold and authenticate.
Route to the Agentforce SDK platform skill to layer the agent surface.
Treat each child skill's instructions as authoritative for its SDK; do not merge their steps. Each SDK owns its own auth setup, dependency installation order, and initialization sequence — interleaving them produces conflicting config and broken init order.

This sequencing is the only multi-skill logic this skill owns. Everything else lives inside the child skills.

Loading a child skill

Invoke the child skill by name through the harness. If it is not available locally, prompt the user to install it with npx skills add <repo>. If the user confirms (or has pre-authorized installs), run the command and load the child skill — do not make the user go figure out how to continue the workflow. If the user declines, stop and explain that the child skill owns the SDK's setup steps and the workflow cannot continue without it. Each child skill is published from a public repo:

Skill	Repo	Install command
`ios-mobile-sdk`	`forcedotcom/SalesforceMobileSDK-Templates` → `skills/ios-mobile-sdk/`	`npx --yes skills add forcedotcom/SalesforceMobileSDK-Templates --skill ios-mobile-sdk --yes`
`android-mobile-sdk`	`forcedotcom/SalesforceMobileSDK-Templates` → `skills/android-mobile-sdk/`	`npx --yes skills add forcedotcom/SalesforceMobileSDK-Templates --skill android-mobile-sdk --yes`
`integrate-agentforce-ios`	`salesforce/AgentforceMobileSDK-iOS` → `skills/integrate-agentforce-ios/`	`npx --yes skills add salesforce/AgentforceMobileSDK-iOS --skill integrate-agentforce-ios --yes`
`integrate-agentforce-android`	`salesforce/AgentforceMobileSDK-Android` → `skills/integrate-agentforce-android/`	`npx --yes skills add salesforce/AgentforceMobileSDK-Android --skill integrate-agentforce-android --yes`

After install, load the child skill and let it take over. Do not inline the child skill's content — the child skill owns scenario detection, prerequisites, and step-by-step instructions.

Frequently asked questions

What does the Mobile Apps Create AI skill do?

Why use Mobile Apps Create on TypingMind?

Because you install it once and use it with any model. Mobile Apps Create is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Mobile Apps Create in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/forcedotcom/sf-skills/tree/main/plugins/builder/mobile-development/skills/mobile-apps-create. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Mobile Apps Create?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Mobile Apps Create?

As many as you like. As long as a model supports skills, you can use Mobile Apps Create with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Mobile Apps Create AI skill free?

Yes. It is published on GitHub by forcedotcom under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Brand Discovery

affaan-m

CommunityPopular

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Competitive Platform Analysis

affaan-m

CommunityPopular

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong…

Frontend Slides

Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a…

Plan Canvas

Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Salesforce Mobile

Before routing

Routing — which SDK family?

Tiebreakers when both seem to apply

Routing — which platform?

Combined workflows (Mobile SDK + Agentforce SDK)

Loading a child skill

Frequently asked questions

Related AI Skills

Set up your own AI workspace now