Agent skill

Field Service Setup Orchestrator Get

by forcedotcom in forcedotcom/sf-skills

A skill your agent uses to set up Salesforce Field Service — Work Types, Skills, Service Territories, Operating Hours, Scheduling Policy, Work Rules, Service Objectives, Data Capture Forms, FSL…

Apache-2.0Auto-check passedSales & Support

Install Field Service Setup Orchestrator Get

skills CLI
$ npx skills add forcedotcom/sf-skills --skill field-service-setup-orchestrator-get -a claude-code

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

GitHub CLI
$ gh skill install forcedotcom/sf-skills field-service-setup-orchestrator-get --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/field-service-setup-orchestrator-get .claude/skills/field-service-setup-orchestrator-get && 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
field-service-setup-orchestrator-get
GitHub stars
1.1k
Token cost
~812 tokens
SKILL.md length
344 words
Files
1
Skills in repo
251
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses to set up Salesforce Field Service — Work Types, Skills, Service Territories, Operating Hours, Scheduling Policy, Work Rules, Service Objectives, Data Capture Forms, FSL…

  • Works in 2 steps: Identify and Confirm → Route
  • Set up Salesforce Field Service — Work Types
  • SKILL.md covers How It Works, Phase 1 — Identify and Confirm, Phase 2 — Route and Conversational Tone, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Field Service Setup Orchestrator Get is an agent skill from forcedotcom/sf-skills. 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.

Its SKILL.md is about 810 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering CRM management. 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

  • Set up Salesforce Field Service — Work Types
  • Service Territories
  • Operating Hours
  • Scheduling Policy

Example prompts

  • “/field-service-setup-orchestrator-get”

Workflow steps

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

  1. Identify and Confirm
  2. Route

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.

    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

Field Service Setup Orchestrator Get loads about 812 tokens when it runs. Until then it costs about 129 tokens; SKILL.md has 344 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~129
When it runs · the whole SKILL.md, loaded when a task matches
~812

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). 344 words, ~812 tokens.

Download SKILL.mdSave it as .claude/skills/field-service-setup-orchestrator-get/SKILL.md (or your agent's skills folder).
name
field-service-setup-orchestrator-get
description
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.
owning_team
sfs-setup-experience
metadata.version
1.0
metadata.domains
Field Service

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.

© 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

Just SKILL.md in skills/field-service-setup-orchestrator-get of forcedotcom/sf-skills.

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Field Service Setup Orchestrator Get 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.

Field Service Setup Orchestrator Get compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Field Service Setup Orchestrator Get this skillforcedotcom/sf-skills1.1k—~812Automated safety check: PassApache-2.0
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
Dev SetupPortwood-Global-Solutions/Portwood126—~1.1kAutomated safety check: PassApache-2.0
Sf FlowJaganpro/sf-skills424—~1.8kAutomated safety check: PassMIT

Similar skills

  • 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 6 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 6 days ago
    Sales & SupportAuto-check passed
  • Dev Setup

    Portwood-Global-Solutions/Portwood

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

    126 GitHub stars~1.1k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Sf Flow

    Jaganpro/sf-skills

    Creates and validates Salesforce Flows with 110-point scoring.

    424 GitHub stars~1.8k tokensUpdated 5 mo ago
    Sales & SupportAuto-check passed
  • Google Maps Export

    gmapsscraper/google-maps-agent-skills

    Export Google Maps business data to CSV, JSON, or CRM format (HubSpot, Pipedrive, Salesforce).

    132 GitHub stars~1.2k tokensUpdated 4 mo ago
    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 2 days ago
    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 2 days ago
    Auto-check passed
  • Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.3k tokensUpdated 2 days ago
    Auto-check: notes
  • Apply a Salesforce sandbox post-copy automation JSON config against a target org.

    1.1k GitHub stars~5.4k tokensUpdated 2 days ago
    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 2 days ago
    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 2 days ago
    Auto-check passed

Works with

Categories

Questions about Field Service Setup Orchestrator Get

What does Field Service Setup Orchestrator Get do?

A skill your agent uses to set up Salesforce Field Service — Work Types, Skills, Service Territories, Operating Hours, Scheduling Policy, Work Rules, Service Objectives, Data Capture Forms, FSL…. Field Service Setup Orchestrator Get is an agent skill from forcedotcom/sf-skills. 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.

When should I use Field Service Setup Orchestrator Get?

Field Service Setup Orchestrator Get fits situations like: set up Salesforce Field Service — Work Types; service Territories; operating Hours; scheduling Policy.

How do I install Field Service Setup Orchestrator Get in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill field-service-setup-orchestrator-get -a claude-code`. Or copy the skill folder (skills/field-service-setup-orchestrator-get in forcedotcom/sf-skills) into .claude/skills/field-service-setup-orchestrator-get in your project. Claude Code loads it when a task matches its description.

How do I install Field Service Setup Orchestrator Get in Codex?

Run `npx skills add forcedotcom/sf-skills --skill field-service-setup-orchestrator-get -a codex`. Or copy the skill folder (skills/field-service-setup-orchestrator-get in forcedotcom/sf-skills) into .agents/skills/field-service-setup-orchestrator-get in your project. Codex loads it when a task matches its description.

Can I use Field Service Setup Orchestrator Get 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 field-service-setup-orchestrator-get -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/field-service-setup-orchestrator-get, .gemini/skills/field-service-setup-orchestrator-get, .github/skills/field-service-setup-orchestrator-get and .opencode/skills/field-service-setup-orchestrator-get in your project.

What does Field Service Setup Orchestrator Get need to run?

SKILL.md names no scripts, command-line tools or credentials: Field Service Setup Orchestrator Get is instructions for the agent only.

Does Field Service Setup Orchestrator Get 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 Field Service Setup Orchestrator Get 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 Field Service Setup Orchestrator Get use?

Field Service Setup Orchestrator Get 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 Field Service Setup Orchestrator Get use?

About 812 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Field Service Setup Orchestrator Get?

Skills that share tags, products or a category with Field Service Setup Orchestrator Get: Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Sf Datacloud (Jaganpro/sf-skills, 424 stars), Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars) and Dev Setup (Portwood-Global-Solutions/Portwood, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Field Service Setup Orchestrator Get?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,065 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.