← ClaudeAtlas

sf-flowlisted

Creates and validates Salesforce flows with 110-point scoring and Winter '26 best practices using Salesforce MCP server. Use when building record-triggered flows, screen flows, autolaunched flows, scheduled flows, or reviewing existing flow performance. Do NOT use for Apex classes and triggers (use sf-apex), creating the objects and fields a flow references (use sf-metadata), or diagnosing a flow failure at runtime from debug logs (use sf- debug). Usage: /sf-flow [create|update|validate] {FlowName} ...
kugamon/salesforce-core-skills · ★ 0 · AI & Automation · score 68
Install: claude install-skill kugamon/salesforce-core-skills
# Salesforce Flow Development and Review Expert Salesforce Flow Builder with deep knowledge of best practices, bulkification, and Winter '26 (API 65.0) metadata. Create production-ready, performant, secure, and maintainable flows using Salesforce MCP server for deployment. ## Dispatch Parse `$ARGUMENTS` to determine the action: | First argument or intent | Workflow | | ------------------------------ | ------------------------ | | `create`, new flow request | Create Flow | | `update`, modify existing flow | Update Flow | | `validate`, review, score | Validate Flow | | _(no argument or unclear)_ | Ask the user (see below) | When the operation is missing or unclear, **you MUST use `AskUserQuestion`** before proceeding: ``` AskUserQuestion(question="What would you like to do?\n\n1. **Create** — generate a new Flow\n2. **Update** — fetch, modify, validate, and redeploy\n3. **Validate** — score an existing Flow") ``` Do NOT guess the operation or default to one. Wait for the user's answer. --- ## Approval Processes: Choose the Engine First When a request is to build an approval (e.g. "create an approval process", "require approval before X", "deal/discount approval", "gate a stage until approved"), do NOT start building until the **engine** is decided: | Engine | Build with