New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Mobile Platform Native Capabilities Integrate

by forcedotcom in forcedotcom/sf-skills

Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and…

Apache-2.0Auto-check passedSales & Support

Install Mobile Platform Native Capabilities Integrate

skills CLI
$ npx skills add forcedotcom/sf-skills --skill mobile-platform-native-capabilities-integrate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install forcedotcom/sf-skills mobile-platform-native-capabilities-integrate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mobile-platform-native-capabilities-integrate .claude/skills/mobile-platform-native-capabilities-integrate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mobile-platform-native-capabilities-integrate
GitHub stars
1.1k
Token cost
~2.2k tokens
SKILL.md length
951 words
Files
14 (incl. references)
Skills in repo
251
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and…

  • Works in 5 steps: Identify the capability → Load the shared and capability-specific… → Wire the service into the LWC → …
  • The user asks for an LWC that scans a barcode
  • SKILL.md covers When to Use This Skill, Prerequisites, Capability Index and Workflow, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Mobile Platform Native Capabilities Integrate is an agent skill from forcedotcom/sf-skills. Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and payments. Use this skill when the user asks for an LWC that scans a barcode, captures a photo of a document, reads location or geofences, prompts for biometrics, reads/writes the device calendar or contacts, taps NFC, takes a payment, prompts for an app review, or scans an AR space. Also triggers on…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 14 other files, including reference files (for example `references/app-review.md`, `references/ar-space-capture.md` and `references/barcode-scanner.md`).

It sits in Sales & Support, covering Customer feedback analysis, CRM management and Design systems. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

  • The user asks for an LWC that scans a barcode
  • Captures a photo of a document
  • Prompts for biometrics
  • Reads/writes the device calendar

Example prompts

  • “lightning/mobileCapabilities”
  • “mobile capability”
  • “Nimbus”
  • “/mobile-platform-native-capabilities-integrate”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Identify the capability
  2. Load the shared and capability-specific references
  3. Wire the service into the LWC
  4. Surface failure modes to the user
  5. Stay inside the supported surface

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mobile Platform Native Capabilities Integrate loads about 2.2k tokens when it runs, and up to ~19k if it reads all its reference files. Until then it costs about 202 tokens; SKILL.md has 951 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~202
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~19k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 951 words, ~2,199 tokens.

Download SKILL.mdSave it as .claude/skills/mobile-platform-native-capabilities-integrate/SKILL.md (or your agent's skills folder). This skill also uses 13 other files; get the full folder from GitHub.
name
mobile-platform-native-capabilities-integrate
description
Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and payments. Use this skill when the user asks for an LWC that scans a barcode, captures a photo of a document, reads location or geofences, prompts for biometrics, reads/writes the device calendar or contacts, taps NFC, takes a payment, prompts for an app review, or scans an AR space. Also triggers on "lightning/mobileCapabilities", "mobile capability", "Nimbus", "device capability". Do not use for mobile offline / Komaci priming reviews (use `mobile-platform-offline-validate`) or for picking generic Lightning base components (use `design-systems-slds-apply`).
metadata.version
1.0
metadata.domains
Mobile
metadata.relatedSkills
design-systems-slds-apply, mobile-platform-offline-validate

Using Mobile Native Capabilities

The lightning/mobileCapabilities module exposes a set of factory functions that return service objects for native device features (barcode scanning, biometrics, location, etc.). Each service extends a common BaseCapability with an isAvailable() method, so an LWC can degrade gracefully on surfaces where the capability is not present (desktop, mobile web).

This skill routes an agent through (1) picking the right capability, (2) loading the authoritative type definitions, and (3) wiring the service into an LWC with the correct availability gating, error handling, and deprecation-aware API choice.

When to Use This Skill

  • User asks for an LWC that uses a device capability listed in the index below.
  • User mentions lightning/mobileCapabilities, "mobile capability", or "Nimbus" by name.
  • User wants to know which mobile native APIs are available, or which one fits their feature.

Do NOT use this skill for:

  • Mobile-offline review of an LWC (lwc:if, inline GraphQL, Komaci-priming violations) — use mobile-platform-offline-validate.
  • Choosing or styling generic Lightning Base Components / SLDS blueprints — use design-systems-slds-apply.

Prerequisites

  • Knowledge that the LWC will run inside a supported mobile container (Salesforce Mobile App, Field Service Mobile App). These capabilities are unavailable on desktop and mobile web; gate every call behind isAvailable().
  • Familiarity with the lightning/mobileCapabilities module declaration (see mobile-capabilities).

Capability Index

CapabilityReferenceOne-line use
App ReviewApp ReviewPrompt the user for a native in-app review.
AR Space CaptureAR Space CaptureCapture a 3D scan of a physical space using AR.
Barcode ScannerBarcode ScannerRead QR / UPC / EAN / Code-128 / etc. from the camera.
BiometricsBiometricsAuthenticate via Face ID / fingerprint.
CalendarCalendarRead or create events on the device calendar.
ContactsContactsRead or create entries in the device address book.
Document ScannerDocument ScannerScan paper documents using the camera with edge detection.
GeofencingGeofencingTrigger logic when the device crosses a geographic boundary.
LocationLocationRead GPS coordinates and watch for updates.
NFCNFCRead or write NFC tags.
PaymentsPaymentsTake an Apple Pay / Google Pay payment.

Workflow

Step 1 — Identify the capability

Map the user's feature ask to one row of the capability index. If the ask spans multiple capabilities (e.g. "scan a barcode and store it on a contact"), plan for each capability separately — there is one factory function per capability.

Step 2 — Load the shared and capability-specific references

Read these two shared references once per session — they apply to every capability and are not duplicated in the per-capability files:

  • BaseCapability — the common interface with isAvailable() that every service extends.
  • mobile-capabilities — the lightning/mobileCapabilities module declaration showing every re-exported service.

Then open the capability's reference file from the table above. Each per-capability reference contains the service-specific TypeScript API (factory function, service interface, options types, result types, error types) and assumes the two shared references above are already in context.

Do not infer the API from memory — read it. The services evolve and some methods are explicitly @deprecated in favor of newer alternatives.

Step 3 — Wire the service into the LWC

For each capability:

  1. Import the factory from lightning/mobileCapabilities:
    js
    import { getBarcodeScanner } from 'lightning/mobileCapabilities';
  2. Get an instance: const scanner = getBarcodeScanner();
  3. Gate the call behind isAvailable():
    js
    if (!scanner.isAvailable()) {
  // graceful fallback or user message
  return;
}
  4. Call the non-deprecated entry point. Several services keep older methods marked @deprecated alongside the recommended one — always prefer the recommended method in the reference.
  5. Wrap the promise in try/catch and handle the typed failure codes the service exposes (e.g. BarcodeScannerFailureCode, LocationServiceFailureCode). User-cancelled vs. permission-denied vs. service-unavailable are distinct UX states.
Show full SKILL.md (385 more words)Show less
Step 4 — Surface failure modes to the user

Each service defines its own failure-code enum. Translate codes into user-actionable messages: a USER_DENIED_PERMISSION should ask the user to grant permission; a USER_DISABLED_PERMISSION must direct them to the OS settings; a SERVICE_NOT_ENABLED should be a developer-visible error, not shown to the user.

Step 5 — Stay inside the supported surface

Mobile capabilities are available only when the LWC runs inside a supported Salesforce mobile app. If the same component is rendered on desktop or mobile web, the factory will still return an object but isAvailable() will return false. Never assume availability — gate every call.

Examples

Example — "Scan a barcode and write it into a field"
  1. Map to: Barcode Scanner.
  2. Read Barcode Scanner.
  3. Use scan(options) (not the deprecated beginCapture / resumeCapture / endCapture triple).
  4. In options, set the barcodeTypes to the symbologies needed (default is all supported types) and enableMultiScan: false for a single read.
  5. On resolve, write result[0].value to the bound field. On reject, inspect error.code against BarcodeScannerFailureCode.
Example — "Take an Apple Pay payment for an order total"
  1. Map to: Payments.
  2. Read Payments.
  3. Gate on isAvailable().
  4. Build the payment request object per the reference.
  5. On resolve, surface the transaction id to the calling flow. On reject, handle user-cancelled and payment-failed paths separately.

Verification Checklist

  • Every capability call is preceded by isAvailable().
  • The non-deprecated entry point is used (no beginCapture / resumeCapture / endCapture for barcode, etc.).
  • Each rejection path is mapped to the typed failure code enum.
  • Imports come from lightning/mobileCapabilities, not from a private path.
  • No assumption that the capability runs on desktop or mobile web.

Troubleshooting

  • isAvailable() returns false on a real device — the device is running an unsupported app surface (not Salesforce Mobile or Field Service Mobile), or the service is gated by an org-level setting. The fix is org configuration, not code.
  • TypeScript can't find the import — confirm the LWC has access to lightning/mobileCapabilities. The module is declared globally inside Salesforce mobile containers; outside that, the types must be installed separately.
  • Deprecated barcode methods still work — yes, but new code must use scan() and dismiss(). Refactor any sample code the agent received before returning it.
  • Multiple capabilities in one component — get separate instances per capability (they are independent service objects); do not try to share state between them.

© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 13 other files (references) in skills/mobile-platform-native-capabilities-integrate of forcedotcom/sf-skills.

  • SKILL.md
  • references/app-review.md
  • references/ar-space-capture.md
  • references/barcode-scanner.md
  • references/base-capability.md
  • references/biometrics.md
  • references/calendar.md
  • references/contacts.md
  • references/document-scanner.md
  • references/geofencing.md
  • references/location.md
  • references/mobile-capabilities.md
  • references/nfc.md
  • references/payments.md

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Mobile Platform Native Capabilities Integrate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mobile Platform Native Capabilities Integrate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mobile Platform Native Capabilities Integrate this skillforcedotcom/sf-skills1.1k—~2.2kAutomated safety check: PassApache-2.0
Salesforce Component Standardsgithub/awesome-copilot40k1 repos~2.4kAutomated safety check: PassMIT
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib154—~4.3kAutomated safety check: PassMIT
Sf DatacloudJaganpro/sf-skills424—~2.7kAutomated safety check: PassMIT
Soql Lib Selectorbeyond-the-cloud-dev/soql-lib154—~2kAutomated safety check: PassMIT
Lead Gen Tool Builderexplorium-ai/gtm-skills163—~1.8kAutomated safety check: NotesMIT

Similar skills

  • Salesforce Component Standards

    github/awesome-copilot

    Official

    Quality standards for Salesforce Lightning Web Components (LWC), Aura components, and Visualforce pages.

    40k GitHub starsUsed in 1 repo~2.4k tokens
    Frontend & DesignAuto-check passed

  • Soql Lib Query Builder

    beyond-the-cloud-dev/soql-lib

    Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).

    154 GitHub stars~4.3k tokensUpdated 4 days ago
    Sales & SupportAuto-check passed

  • Sf Datacloud

    Jaganpro/sf-skills

    Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.

    424 GitHub stars~2.7k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed

  • Soql Lib Selector

    beyond-the-cloud-dev/soql-lib

    Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.

    154 GitHub stars~2k tokensUpdated 4 days ago
    Sales & SupportAuto-check passed

  • Lead Gen Tool Builder

    explorium-ai/gtm-skills

    Lead generation tool builder skill for Claude Code and Codex: scaffolds a complete, self-hostable, ZoomInfo-style B2B lead-generation web app — company & contact search UI, firmographic and…

    163 GitHub stars~1.8k tokensUpdated 13 days ago
    Sales & SupportAuto-check: notes

  • Dev Setup

    Portwood-Global-Solutions/Portwood

    Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.

    125 GitHub stars~1.1k tokensUpdated today
    Sales & SupportAuto-check passed

More from forcedotcom/sf-skills

All 251 skills in this repo

  • Agentforce Architecture Analyze

    forcedotcom/sf-skills

    Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.

    1.1k GitHub stars~4.5k tokensUpdated today
    Auto-check passed

  • Agentforce D360 Analyze

    forcedotcom/sf-skills

    Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated today
    Auto-check: notes

  • Automation Sandbox Post Copy Configure

    forcedotcom/sf-skills

    Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.4k tokensUpdated today
    Auto-check: notes

  • Design Systems Slds Apply

    forcedotcom/sf-skills

    Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.

    1.1k GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Experience Lwc Generate

    forcedotcom/sf-skills

    Lightning Web Components with PICKLES methodology and 165-point scoring.

    1.1k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Mobile Platform Native Capabilities Integrate

What does Mobile Platform Native Capabilities Integrate do?

Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and…. Mobile Platform Native Capabilities Integrate is an agent skill from forcedotcom/sf-skills. Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and payments.

When should I use Mobile Platform Native Capabilities Integrate?

Mobile Platform Native Capabilities Integrate fits situations like: the user asks for an LWC that scans a barcode; captures a photo of a document; prompts for biometrics; reads/writes the device calendar.

How do I install Mobile Platform Native Capabilities Integrate in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill mobile-platform-native-capabilities-integrate -a claude-code`. Or copy the skill folder (skills/mobile-platform-native-capabilities-integrate in forcedotcom/sf-skills) into .claude/skills/mobile-platform-native-capabilities-integrate in your project. Claude Code loads it when a task matches its description.

How do I install Mobile Platform Native Capabilities Integrate in Codex?

Run `npx skills add forcedotcom/sf-skills --skill mobile-platform-native-capabilities-integrate -a codex`. Or copy the skill folder (skills/mobile-platform-native-capabilities-integrate in forcedotcom/sf-skills) into .agents/skills/mobile-platform-native-capabilities-integrate in your project. Codex loads it when a task matches its description.

Can I use Mobile Platform Native Capabilities Integrate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill mobile-platform-native-capabilities-integrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobile-platform-native-capabilities-integrate, .gemini/skills/mobile-platform-native-capabilities-integrate, .github/skills/mobile-platform-native-capabilities-integrate and .opencode/skills/mobile-platform-native-capabilities-integrate in your project.

What does Mobile Platform Native Capabilities Integrate need to run?

SKILL.md names no scripts, command-line tools or credentials: Mobile Platform Native Capabilities Integrate is instructions for the agent only.

Does Mobile Platform Native Capabilities Integrate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mobile Platform Native Capabilities Integrate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Mobile Platform Native Capabilities Integrate use?

Mobile Platform Native Capabilities Integrate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mobile Platform Native Capabilities Integrate use?

About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 16k tokens, read only when the agent opens those files.

What are the alternatives to Mobile Platform Native Capabilities Integrate?

Skills that share tags, products or a category with Mobile Platform Native Capabilities Integrate: Salesforce Component Standards (github/awesome-copilot, 40k stars), Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Sf Datacloud (Jaganpro/sf-skills, 424 stars) and Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mobile Platform Native Capabilities Integrate?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.