generating-flow

Generate Salesforce Flow XML via the MCP 3-step pipeline.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/cchrisv/professorFlowVisualPicker --skill generating-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generating-flow
Source: https://github.com/cchrisv/professorFlowVisualPicker/tree/main/.agents/skills/generating-flow
Command: npx skills add https://github.com/cchrisv/professorFlowVisualPicker --skill generating-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate Salesforce Flow metadata end-to-end without manual coding by coordinating the MCP pipeline to build and deploy Screen, Autolaunched, Record-Triggered, and Scheduled Flows.

Core Features & Use Cases

  • End-to-end Flow generation via the mandated 3-step MCP pipeline (fetchGroundedObjectMetadata → flowElementSelection → flowElementGeneration) to produce the Flow XML.
  • Supports multiple Flow types (Screen, Autolaunched, Record-Triggered, Scheduled) and various input sources, enabling automation across environments.
  • Enforces the MCP workflow discipline: never generate metadata outside the three-step pipeline and always loop Step 3 until completion.

Quick Start

Describe the flow you want to create and run the full 3-step MCP pipeline to generate its metadata XML.

Frequently Asked Questions about generating-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate Salesforce Flow XML automatically without manual coding?

Salesforce Flow XML generation is automated by orchestrating the MCP 3-step pipeline—fetchGroundedObjectMetadata, flowElementSelection, and flowElementGeneration—to produce deployable Flow metadata files without manual coding.

What types of Salesforce Flows can I create using the MCP pipeline?

The MCP pipeline supports building Screen, Autolaunched, Record-Triggered, and Scheduled Salesforce Flows, handling requests to create and generate flow metadata across various deployment environments.

How does the MCP pipeline process custom object metadata for Salesforce Flows?

The MCP pipeline processes custom object metadata from an sfdx project via inflightMetadata during the fetchGroundedObjectMetadata step, grounding subsequent element selection and generation steps.

Can I generate Salesforce Flow metadata outside of the three-step MCP pipeline?

No, the workflow discipline mandates never generating Salesforce Flow metadata outside the three-step MCP pipeline, requiring strict sequential execution of fetchGroundedObjectMetadata, flowElementSelection, and flowElementGeneration.

What happens if the Salesforce Flow generation is not complete after one loop?

The pipeline loops the flowElementGeneration step until the flow is complete, ensuring all required elements are processed and the final XML output is fully generated using the requestSource 'A4V'.