skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
forcedotcom/sf-skills72 installs

field-service-setup-orchestrator-get

Use this skill to set up Salesforce Field Service — Work Types, Skills, Service Territories, Operating Hours, Scheduling Policy, Work Rules, Service Objectives, Data Capture Forms, FSL mobile forms, Pre-Work Brief, Mobile Branding, or any FSL setup, enablement, or configuration request. Entry point that identifies what the user wants to configure and routes to the right sub-workflow: Foundation Setup, Scheduling Policy, Data Capture Forms, Pre-Work Brief, or Mobile Branding.

How do I install this agent skill?

npx skills add https://github.com/forcedotcom/sf-skills --skill field-service-setup-orchestrator-get
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill acts as a natural language router for Salesforce Field Service setup tasks. It identifies user intent and delegates to appropriate sub-skills while following conversational best practices. No security risks were identified.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

How It Works

This skill is the entry point for all Field Service setup. It identifies what the user wants to configure and routes to the correct sub-skill. It does not perform setup work itself.

Phase 1 — Identify and Confirm

If the intent is unclear or generic, first establish what the user wants to set up before going further.

Before routing to any workflow, always ask a brief confirmation question — never skip this step, even when intent is obvious or the user has already provided data. Adapt the question naturally to context:

  • For workflows with a design stage (Foundation Setup, Scheduling Policy, Data Capture Forms): the question should establish whether the user wants a guided design conversation or to proceed directly with data they already have.
  • For workflows without a design stage (Pre-Work Brief, Mobile Branding): confirm the user is ready before proceeding.

One short question. Wait for the answer before delegating.

Phase 2 — Route

Match the user's intent semantically to a workflow and delegate to the sub-skill.

WorkflowSub-skillNote
Foundation Setup (default)sfs-setup-experience/sfs-foundation-setup-designer → deploys via sfs-sobject-createAlways first; covers Work Types, Skills, Service Territories, Operating Hours
Scheduling Policysfs-setup-experience/sfs-scheduling-policy-designer → deploys via sfs-sobject-createAsk if Foundation is done; if not, offer it first
Data Capture Formssfs-mobile-core-experience/fs-data-capture-form-designer → fs-data-capture-form-deployerAsk if Foundation is done; if not, offer it first
Pre-Work Briefsfs-frontline-ai/fs-prework-brief-deployerAsk if Foundation is done; if not, offer it first
Mobile Brandingsfs-mobile-core-experience/fs-mobile-brandingAsk if Foundation is done; if not, offer it first

Conversational Tone

  • Announce each phase in one plain sentence before it begins — what's about to happen and why.
  • Never expose skill names, SOR IDs, or tool references to the user (no "sfs-foundation-setup-designer", "sfs-sobject-create", "dispatch"). Use plain labels: "Foundation Setup", "design interview", "creating your records".

Key Principles

  • This skill routes — it never does setup work itself.
  • One workflow at a time; wait for explicit confirmation before the next.
  • If a requested area has no sub-skill yet, say so and ask if the user wants to proceed manually.
  • Never delegate to sfs-sobject-create directly — Foundation records must always go through sfs-foundation-setup-designer first.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/forcedotcom/sf-skills/field-service-setup-orchestrator-get">View field-service-setup-orchestrator-get on skillZs</a>