New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Salesforce Flow Design

by github in github/awesome-copilot

Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards.

OfficialMITAuto-check passedDevOps & Cloud

Install Salesforce Flow Design

skills CLI
$ npx skills add github/awesome-copilot --skill salesforce-flow-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install github/awesome-copilot salesforce-flow-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/salesforce-flow-design .claude/skills/salesforce-flow-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
salesforce-flow-design
GitHub stars
40k
Used in
1 other repo
Token cost
~1.7k tokens
SKILL.md length
823 words
Files
1
Skills in repo
417
Repo updated
First seen
Licence
MIT

At a glance

Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards.

  • Works in 7 steps: Confirm Flow Is the Right Tool → Select the Correct Flow Type → Bulk Safety Checklist → …
  • Reviewing Record-Triggered
  • SKILL.md covers Step 1 — Confirm Flow Is the…, Step 2 — Select the Correct…, Step 3 — Bulk Safety Checklist and Step 4 — Fault Path Requirements, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Salesforce Flow Design is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards. Use this skill when designing or reviewing Record-Triggered, Screen, Autolaunched, Scheduled, or Platform Event flows to ensure correct type selection, no DML/Get Records in loops, proper fault connectors on all data-changing elements, and appropriate automation density checks before deployment.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Deployment. It works with Salesforce. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

  • Reviewing Record-Triggered
  • Platform Event flows to ensure correct type selection
  • No DML/Get Records in loops
  • Proper fault connectors on all data-changing elements

Example prompts

  • “/salesforce-flow-design”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Confirm Flow Is the Right Tool
  2. Select the Correct Flow Type
  3. Bulk Safety Checklist
  4. Fault Path Requirements
  5. Automation Density Check
  6. Screen Flow UX Guidelines
  7. Deployment Safety

What it can do on your machine

Read from SKILL.md and the folder at commit 7cce7cf. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Salesforce Flow Design loads about 1.7k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 823 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 7cce7cf, republished under its MIT licence (© github). 823 words, ~1,740 tokens.

Download SKILL.mdSave it as .claude/skills/salesforce-flow-design/SKILL.md (or your agent's skills folder).
name
salesforce-flow-design
description
Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards. Use this skill when designing or reviewing Record-Triggered, Screen, Autolaunched, Scheduled, or Platform Event flows to ensure correct type selection, no DML/Get Records in loops, proper fault connectors on all data-changing elements, and appropriate automation density checks before deployment.

Salesforce Flow Design and Validation

Apply these checks to every Flow you design, build, or review.

Step 1 — Confirm Flow Is the Right Tool

Before designing a Flow, verify that a lighter-weight declarative option cannot solve the problem:

RequirementBest tool
Calculate a field value with no side effectsFormula field
Prevent a bad record save with a user messageValidation rule
Sum or count child records on a parentRoll-up Summary field
Complex multi-object logic, callouts, or high volumeApex (Queueable / Batch) — not Flow
Everything elseFlow ✓

If you are building a Flow that could be replaced by a formula field or validation rule, ask the user to confirm the requirement is genuinely more complex.

Step 2 — Select the Correct Flow Type

Use caseFlow typeKey constraint
Update a field on the same record before it is savedBefore-save Record-TriggeredCannot send emails, make callouts, or change related records
Create/update related records, emails, calloutsAfter-save Record-TriggeredRuns after commit — avoid recursion traps
Guide a user through a multi-step UI processScreen FlowCannot be triggered by a record event automatically
Reusable background logic called from another FlowAutolaunched (Subflow)Input/output variables define the contract
Logic invoked from Apex @InvocableMethodAutolaunched (Invocable)Must declare input/output variables
Time-based batch processingScheduled FlowRuns in batch context — respect governor limits
Respond to events (Platform Events / CDC)Platform Event–TriggeredRuns asynchronously — eventual consistency

Decision rule: choose before-save when you only need to change the triggering record's own fields. Move to after-save the moment you need to touch related records, send emails, or make callouts.

Step 3 — Bulk Safety Checklist

These patterns are governor limit failures at scale. Check for all of them before the Flow is activated.

DML in Loops — Automatic Fail
Loop element
  └── Create Records / Update Records / Delete Records  ← ❌ DML inside loop

Fix: collect records inside the loop into a collection variable, then run the DML element outside the loop.

Get Records in Loops — Automatic Fail
Loop element
  └── Get Records  ← ❌ SOQL inside loop

Fix: perform the Get Records query before the loop, then loop over the collection variable.

Correct Bulk Pattern
Get Records — collect all records in one query
└── Loop over the collection variable
    └── Decision / Assignment (no DML, no Get Records)
└── After the loop: Create/Update/Delete Records — one DML operation
Transform vs Loop

When the goal is reshaping a collection (e.g. mapping field values from one object to another), use the Transform element instead of a Loop + Assignment pattern. Transform is bulk-safe by design and produces cleaner Flow graphs.

Step 4 — Fault Path Requirements

Every element that can fail at runtime must have a fault connector. Flows without fault paths surface raw system errors to users.

Elements That Require Fault Connectors
  • Create Records
  • Update Records
  • Delete Records
  • Get Records (when accessing a required record that might not exist)
  • Send Email
  • HTTP Callout / External Service action
  • Apex action (invocable)
  • Subflow (if the subflow can throw a fault)
Fault Handler Pattern
Fault connector → Log Error (Create Records on a logging object or fire a Platform Event)
               → Screen element with user-friendly message (Screen Flows)
               → Stop / End element (Record-Triggered Flows)

Never connect a fault path back to the same element that faulted — this creates an infinite loop.

Show full SKILL.md (365 more words)Show less

Step 5 — Automation Density Check

Before deploying, verify there are no overlapping automations on the same object and trigger event:

  • Other active Record-Triggered Flows on the same Object + When to Run combination
  • Legacy Process Builder rules still active on the same object
  • Workflow Rules that fire on the same field changes
  • Apex triggers that also run on the same before insert / after update context

Overlapping automations can cause unexpected ordering, recursion, and governor limit failures. Document the automation inventory for the object before activating.

Step 6 — Screen Flow UX Guidelines

  • Every path through a Screen Flow must reach an End element — no orphan branches.
  • Provide a Back navigation option on multi-step flows unless back-navigation would corrupt data.
  • Use lightning-input and SLDS-compliant components for all user inputs — do not use HTML form elements.
  • Validate required inputs on the screen before the user can advance — use Flow validation rules on the screen.
  • Handle the Pause element if the flow may need to await user action across sessions.

Step 7 — Deployment Safety

Deploy as Draft    →   Test with 1 record   →   Test with 200+ records   →   Activate
  • Always deploy as Draft first and test thoroughly before activation.
  • For Record-Triggered Flows: test with the exact entry conditions (e.g. ISCHANGED(Status) — ensure the test data actually triggers the condition).
  • For Scheduled Flows: test with a small batch in a sandbox before enabling in production.
  • Check the Automation Density score for the object — more than 3 active automations on a single object increases order-of-execution risk.

Quick Reference — Flow Anti-Patterns Summary

Anti-patternRiskFix
DML element inside a LoopGovernor limit exceptionMove DML outside the loop
Get Records inside a LoopSOQL governor limit exceptionQuery before the loop
No fault connector on DML/email/callout elementUnhandled exception surfaced to userAdd fault path to every such element
Updating the triggering record in an after-save flow with no recursion guardInfinite trigger loopsAdd an entry condition or recursion guard variable
Looping directly on $Record collectionIncorrect behaviour at scaleAssign to a collection variable first, then loop
Process Builder still active alongside a new FlowDouble-execution, unexpected orderingDeactivate Process Builder before activating the Flow
Screen Flow with no End element on all branchesRuntime error or stuck userEnsure every branch resolves to an End element

© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/salesforce-flow-design of github/awesome-copilot.

Open the folder on GitHubat commit 7cce7cf

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Salesforce Flow Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Salesforce Flow Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Salesforce Flow Design this skillgithub/awesome-copilot40k1 repos~1.7kAutomated safety check: PassMIT
Sf DeployJaganpro/sf-skills424—~2kAutomated safety check: PassMIT
Sf Vlocity Build DeployJaganpro/sf-skills424—~1.7kAutomated safety check: PassMIT
Service Digital Engagement Channel Configureforcedotcom/sf-skills1.1k—~4.9kAutomated safety check: PassApache-2.0
Service Digital Engagement Deployment Configureforcedotcom/sf-skills1.1k—~3.7kAutomated safety check: PassApache-2.0
Platform Metadata Deployforcedotcom/sf-skills1.1k—~2.4kAutomated safety check: PassApache-2.0

Similar skills

  • Sf Deploy

    Jaganpro/sf-skills

    Salesforce DevOps automation using sf CLI v2. An agent skill from Jaganpro/sf-skills.

    424 GitHub stars~2k tokensUpdated 5 mo ago
    DevOps & CloudAuto-check passed

  • Sf Vlocity Build Deploy

    Jaganpro/sf-skills

    Salesforce Industries DataPack deployment automation using Vlocity Build.

    424 GitHub stars~1.7k tokensUpdated 5 mo ago
    DevOps & CloudAuto-check passed

  • Service Digital Engagement Channel Configure

    forcedotcom/sf-skills

    Configures and deploys enhanced chat Messaging Channels for Messaging for In-App and Web (MIAW).

    1.1k GitHub stars~4.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Platform Metadata Deploy

    forcedotcom/sf-skills

    Salesforce DevOps automation using sf CLI v2. An agent skill from forcedotcom/sf-skills.

    1.1k GitHub stars~2.4k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Omnistudio Datapacks Deploy

    forcedotcom/sf-skills

    Salesforce Industries DataPack deployment automation using Vlocity Build.

    1.1k GitHub stars~2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from github/awesome-copilot

All 417 skills in this repo

  • Acquire Codebase Knowledge

    github/awesome-copilot

    Official

    Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.

    40k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

  • Azure Architecture Autopilot

    github/awesome-copilot

    Official

    Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.

    40k GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Draw.io Diagram Generator

    github/awesome-copilot

    Official

    Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.

    40k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

  • Credit Risk Data Cleaning

    github/awesome-copilot

    Official

    Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.

    40k GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Daily Focus Board

    github/awesome-copilot

    Official

    Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Python Pypi Package Builder

    github/awesome-copilot

    Official

    End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.

    40k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Works with

Categories

Questions about Salesforce Flow Design

What does Salesforce Flow Design do?

Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards. Salesforce Flow Design is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Salesforce Flow architecture decisions, flow type selection, bulk safety validation, and fault handling standards.

When should I use Salesforce Flow Design?

Salesforce Flow Design fits situations like: reviewing Record-Triggered; platform Event flows to ensure correct type selection; no DML/Get Records in loops; proper fault connectors on all data-changing elements.

How do I install Salesforce Flow Design in Claude Code?

Run `npx skills add github/awesome-copilot --skill salesforce-flow-design -a claude-code`. Or copy the skill folder (skills/salesforce-flow-design in github/awesome-copilot) into .claude/skills/salesforce-flow-design in your project. Claude Code loads it when a task matches its description.

How do I install Salesforce Flow Design in Codex?

Run `npx skills add github/awesome-copilot --skill salesforce-flow-design -a codex`. Or copy the skill folder (skills/salesforce-flow-design in github/awesome-copilot) into .agents/skills/salesforce-flow-design in your project. Codex loads it when a task matches its description.

Can I use Salesforce Flow Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill salesforce-flow-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/salesforce-flow-design, .gemini/skills/salesforce-flow-design, .github/skills/salesforce-flow-design and .opencode/skills/salesforce-flow-design in your project.

What does Salesforce Flow Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Salesforce Flow Design is instructions for the agent only.

Does Salesforce Flow Design access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Salesforce Flow Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Salesforce Flow Design use?

Salesforce Flow Design is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Salesforce Flow Design use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Salesforce Flow Design?

Skills that share tags, products or a category with Salesforce Flow Design: Sf Deploy (Jaganpro/sf-skills, 424 stars), Sf Vlocity Build Deploy (Jaganpro/sf-skills, 424 stars), Service Digital Engagement Channel Configure (forcedotcom/sf-skills, 1.1k stars) and Service Digital Engagement Deployment Configure (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Salesforce Flow Design?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,792 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 8, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.