Agent skill · forcedotcom

field-service-mobile-branding-configure

Derive a Field Service mobile app color scheme from a brand source (URL, hex codes, brand-guide paste, or color description), validate WCAG AA contrast in both light and dark mode, and apply the 14-field scheme to the org-default FieldServiceMobileSettings record. Trigger phrases include 'brand the mobile app', 'apply branding to Field Service mobile', 'update the mobile app colors', 'use this brand guide for the app', 'set the color scheme for the mobile app'. Do NOT use this skill for Dispatcher console / Gantt branding, Experience Cloud BrandingSet records, or scheduling policy colors — out of scope.

What it needs

About 5k tokens when loaded.

What this skill does

Field Service Mobile Branding This skill ingests a brand source and produces a 14-field color scheme that gets applied to the org-default FieldServiceMobileSettings record (DeveloperName='FieldServiceMobileSettings', IsDefault=true). Confirmation with the user happens between derivation and apply — never apply without approval. Source: This skill was authored by Chad Barbour and is mirrored from an upstream Field Service assets repository. Methodology, color tables, and contrast checks are unchanged from upstream — refresh from upstream when content changes there. Runtime contract: every org interaction in this skill is a single REST call dispatched through the Codey runtime (dispatch locally / the hosted Headless 360 MCP in shared surfaces). This skill has no dependency on the execution environment — no sf CLI, no shell scripts, no local Python, no temp files. Colors are derived and validated by the agent inline, then written with one sObject PATCH. Do not shell out. Input contract One of: A website URL — fetch with WebFetch, extract dominant brand colors. A brand-guide paste or document — parse for hex codes and named colors. Direct hex codes — accept as-is. A color description (e.g. "we're a red and white company") — ask for at least one specific hex code or URL before proceeding. See reference/derivation-methodology.md for the four ingestion cases (A–D) in detail. Output A 14-field color scheme written to the org-default FieldServiceMobileSettings record via a single sObject PATCH (PATCH /services/data/vXX.0/sobjects/FieldServiceMobileSettings/{id}). Color changes appear on devices after the metadata cache refreshes (default: 7 days, force-refreshable from app Settings). Workflow 1. Confirm the target org Before fetching the brand source, confirm the org is reachable with a cheap auth probe — dispatch SELECT Id FROM Organization LIMIT 1 (GET /services/data/vXX.0/query): 2xx with totalSize=1 → the session token is live; continue. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills forcedotcom/field-service-mobile-branding-configure

View the source on GitHub

Browse the @skills marketplace