Agent skill · forcedotcom
field-service-data-capture-form-designer-configure
Design a Field Service Mobile Data Capture Flow from either a natural-language description OR a PDF/image of an existing paper form. Extracts field labels, types, required-state, and section structure into an intermediate JSON spec, confirms the plan with the user, then hands off to fs-data-capture-form-deployer for compile + deploy. Handles both input modes in one skill — prose ('build a Field Service form for asset inspection', 'make a DataCaptureFlow that asks the technician to…', 'create an inventory transfer form') and visual sources ('convert this PDF to a Data Capture Flow', 'make a Field Service form from this image', 'turn this paper form into a DataCaptureFlow'). Detects the input mode automatically from a .pdf/.png/.jpg/.jpeg path, else extracts from the prose. Do NOT use this skill to patch an already-deployed flow — that's fs-data-capture-form-editor.
What it needs
About 6k tokens when loaded.
What this skill does
Design a Data Capture Form (from prose or from an image / PDF) This skill produces an intermediate JSON spec from the user's input — a natural-language description or a PDF/image of an existing form — gets the user's approval on the plan, and then invokes fs-data-capture-form-deployer to compile and deploy. When this skill fires The user asks for a Data Capture Flow / Field Service Mobile form. The input arrives in one of two modes: Prose mode — the user describes the form in plain text with no attached file. Examples: "Create a data capture form for asset inspection that asks for asset id, condition rating, photos, and remarks." "Build a Field Service form for inventory transfer with parts repeater, source location, and destination dropdown." "Generate a DataCaptureFlow that captures three things: site name, contact info, and a notes field." Image / PDF mode — the user supplies a path to a .pdf, .png, .jpg, or .jpeg file. Examples: "Convert /tmp/inspection.pdf to a Data Capture Flow" "Build a Field Service form from this image: ~/Downloads/site-visit.png" "Turn this paper form into a DataCaptureFlow" (with attached image) Detect the mode from the input: if the user supplied a .pdf / .png / .jpg / .jpeg path, use image/PDF mode; otherwise use prose mode. Everything after extraction (steps 2-6) is identical for both. Workflow 1. Read the source (mode-dependent) Prose mode — read the description carefully; don't fabricate fields. Extract only the fields the user actually mentioned. Don't invent extra fields based on what "usually goes on" an inspection form. If the user says "asks for asset id, condition rating, photos, and remarks", emit four fields, not eight. If the user's description is too vague to produce a usable form ("build a form that captures stuff about a service appointment"), ask one or two targeted questions before extracting — what fields they want, whether there's a parent record, what should happen on submit. Don't guess. …
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-designer-configure--bb6a08