What is field-service-data-capture-migrate?

A migration tool for moving Salesforce Field Service Mobile flows to Data Capture flows. It reads the flow’s XML, changes its structure and field types, and deploys the result as a draft.

Use it to convert Field Service Mobile flows, adjust their execution graphs and fields, remove platform events, and deploy draft versions.

It removes the need to redesign these legacy mobile flows by hand. Activation remains a separate manual administrator step.

field-service-data-capture-migrate — Skill by forcedotcom/sf-skills

About the project

forcedotcom/sf-skills is a collection of reusable instructions that help AI coding agents build and work with Salesforce applications and platform features. Developers use it for Agentforce agents, Lightning apps, Flow, Apex, SOQL, Lightning Web Components, and related Salesforce configuration. The catalogue entries are the repository’s skills, plugins, commands, MCP servers, and agents for AI tools that support skills.

forcedotcom/sf-skills · 1,097 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add forcedotcom/sf-skills --skill field-service-data-capture-migrate

Clone the repo

git clone --depth 1 https://github.com/forcedotcom/sf-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-data-capture-migrate/github.svg)](https://agentmods.dev/skills/forcedotcom/sf-skills/field-service-data-capture-migrate)

Your own site

<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/field-service-data-capture-migrate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-data-capture-migrate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/field-service-data-capture-migrate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-data-capture-migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 196 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,562 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00196	$0.06562
Opus 5.5	$0.00078	$0.02625
Sonnet 5.5	$0.00039	$0.01312
Haiku 4.5	$0.00020	$0.00656

Measured 28d ago against content hash b867b7914034, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

field-service-data-capture-migrate scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 28d ago.

The scan reads SKILL.md. This mod also ships 16 executable files (scripts/analyze_flow.py, scripts/convert_to_dc_spec.py, scripts/cud_analysis.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- tool: ["curl"]

skills/field-service-data-capture-migrate/SKILL.md · 392 lines

How it starts

The opening of the file, as written. The whole thing — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migrate Field Service Mobile Flows to Data Capture

This skill migrates legacy Field Service mobile flows (processType='FieldServiceMobile') to DataCaptureFlow using a fully automated XML transformer. The transformer handles all known migration patterns including field type conversion, execution graph restructuring, variable deduplication, and platform-event removal.

Goal: Get Field Service customers off Mobile Screen Flows and onto Data Capture — the strategic direction for Field Service digital forms.

SKILL_ROOT="${SKILL_ROOT:-${PLUGIN_ROOT:-$HOME/.vibe/skills}/field-service-data-capture-migrate}"
SCR="$SKILL_ROOT/scripts"
OUT="${FSM_OUT:-$PWD}"  # *_DC files land in cwd; override via FSM_OUT.

Why migrate

Capability	Mobile Screen Flow	Data Capture Flow
Conditional Visibility	No — workaround via separate screens	Yes — built-in, within a single screen
Cross-Field Validation	No — validates on "Next" only	Yes — real-time, immediate feedback
Offline	Yes — good (Briefcase priming)	Yes — better, offline-first, autosave/pause
Repeatable Sections	Yes — medium UX (Loop + screens)	Yes — better UX (native Repeater)
Mobile UX	Yes — good	Yes — better, fewer clicks, in-screen logic
Dependent Picklists	Yes — mobile only	Partial — conditional filtering only (roadmap)
Backoffice Completion	Yes — supported	No — roadmap
Form Edit after Submit	No — limited	No — roadmap
Future Proofing	No — legacy path	Yes — AI, Voice to Form, ongoing investment

Automated migration workflow

Step 0 — Clarify migration scope FIRST

Before querying the org, determine the user's intent. If the request is ambiguous (e.g. "migrate flows", "migrate my org's flows"), ask explicitly whether they mean one specific flow, several named flows, or ALL Field Service Mobile flows in the org. Only proceed to Step 1 after the scope is clear. Never query all flows unless the user explicitly wants that.

Read the full file on GitHub · 392 lines

Files

What ships with it

25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

28d ago First seen · 392 lines · 196 tokens per session scan A b867b7914034

Subscribe to this mod's changes

field-service-data-capture-migrate is a skill published in the GitHub repository forcedotcom/sf-skills (1,097 stars, last pushed today), licensed Apache-2.0. It adds 196 tokens to every session and 6,562 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-19.

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

field-service-data-capture-migrate