How do I install the Field Service Setup Orchestrator Get skill?

Run npx skillmds@latest add gabrielmoreira/field-service-setup-orchestrator-get in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Field Service Setup Orchestrator Get safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Field Service Setup Orchestrator Get?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Field Service Setup Orchestrator Get free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Field Service Setup Orchestrator Get?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Field Service Setup Orchestrator Get by gabrielmoreira

Name: Field Service Setup Orchestrator Get
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

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.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

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.

Workflow	Sub-skill	Note
Foundation Setup (default)	`sfs-setup-experience/sfs-foundation-setup-designer` → deploys via `sfs-sobject-create`	Always first; covers Work Types, Skills, Service Territories, Operating Hours
Scheduling Policy	`sfs-setup-experience/sfs-scheduling-policy-designer` → deploys via `sfs-sobject-create`	Ask if Foundation is done; if not, offer it first
Data Capture Forms	`sfs-mobile-core-experience/fs-data-capture-form-designer` → `fs-data-capture-form-deployer`	Ask if Foundation is done; if not, offer it first
Pre-Work Brief	`sfs-frontline-ai/fs-prework-brief-deployer`	Ask if Foundation is done; if not, offer it first
Mobile Branding	`sfs-mobile-core-experience/fs-mobile-branding`	Ask 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.

---name: field-service-setup-orchestrator-getdescription: 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 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. | Workflow | Sub-skill | Note | |---|---|---| | **Foundation Setup** *(default)* | `sfs-setup-experience/sfs-foundation-setup-designer` → deploys via `sfs-sobject-create` | Always first; covers Work Types, Skills, Service Territories, Operating Hours | | Scheduling Policy | `sfs-setup-experience/sfs-scheduling-policy-designer` → deploys via `sfs-sobject-create` | Ask if Foundation is done; if not, offer it first | | Data Capture Forms | `sfs-mobile-core-experience/fs-data-capture-form-designer` → `fs-data-capture-form-deployer` | Ask if Foundation is done; if not, offer it first | | Pre-Work Brief | `sfs-frontline-ai/fs-prework-brief-deployer` | Ask if Foundation is done; if not, offer it first | | Mobile Branding | `sfs-mobile-core-experience/fs-mobile-branding` | Ask 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.

Frequently asked questions