Agent skill · forcedotcom
field-service-data-capture-form-editor-configure
Patch an existing Data Capture Flow that's already deployed in a connected Salesforce org. Retrieves the live Flow Metadata JSON via the Tooling API, applies the user's requested change, and PATCHes it back. Use when the user names an existing flow and asks to add/remove/rename a field, change visibility, fix a bug, add visual polish, or swap a placeholder for a real component ('add a Notes field to Inventory_Transfer', 'fix the visibility rule on Work_Order_Number', 'make the parts repeater optional', 'replace the Signature placeholder with the real dcSignature component'). Do NOT use this skill to build a brand-new flow — that's fs-data-capture-form-designer followed by fs-data-capture-form-deployer.
What it needs
About 7k tokens when loaded.
What this skill does
Edit a Data Capture Form (in an org) This skill patches a flow that already exists in a connected org. The source of truth is the deployed flow's Metadata JSON, retrieved live from the Tooling Flow sObject — there is no spec file, no .flow-meta.xml, no zip, no SFDX project. The skill retrieves the JSON, edits it in memory, and PATCHes it back. Runtime contract: every org interaction in this skill is a 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 local Python, no temp files, no scratch SFDX project. Auth probes, the flow retrieve, and the redeploy are single REST calls; the JSON patch is authored by the agent inline. Do not shell out. When this skill fires The user names an existing flow (InventoryTransfer, AssetInspection, etc.) and asks for a change. The user pastes a Flow Builder URL and asks for a change. The user describes a deploy error or runtime bug in a deployed flow. If the user is starting from scratch (prose, PDF, image), route to a design- skill instead. Workflow 1. Verify org auth Confirm the connected 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. 401/403 → the org needs re-authentication. Surface that to the user and stop. (The Codey runtime resolves and refreshes the connected org — this skill does not manage org aliases.) 2. Retrieve the live flow's Metadata JSON The Tooling Flow sObject exposes the flow definition as a JSON Metadata field — the same shape the deployer assembles and POSTs. Retrieving is a two-call round-trip, no CLI and no file: 1. Resolve the latest version id from the API name. Dispatch GET /services/data/vXX.0/tooling/query with: Edit the latest version (LatestVersionId) so the patch builds on the newest draft, not a stale active version. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/field-service-data-capture-form-editor-configure