Agent skill

Sf Flow

Creates and validates Salesforce Flows with 110-point scoring.

Install Sf Flow

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-flow -a claude-code

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

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-flow --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/Jaganpro/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sf-flow .claude/skills/sf-flow && 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/

Paste into Claude Code

Install the "sf-flow" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-flow into .claude/skills/sf-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-flow", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-flow

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-flow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-flow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sf-flow .agents/skills/sf-flow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sf-flow" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-flow into .agents/skills/sf-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-flow", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-flow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-flow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sf-flow .cursor/skills/sf-flow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sf-flow" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-flow into .cursor/skills/sf-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-flow", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Jaganpro/sf-skills.git --path skills/sf-flow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-flow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-flow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sf-flow .gemini/skills/sf-flow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sf-flow" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-flow into .gemini/skills/sf-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-flow", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-flow

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-flow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sf-flow .github/skills/sf-flow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sf-flow" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-flow into .github/skills/sf-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-flow", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-flow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-flow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sf-flow .opencode/skills/sf-flow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sf-flow" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-flow into .opencode/skills/sf-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-flow", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sf-flow
GitHub stars: 424
Token cost: ~1.8k tokens
SKILL.md length: 563 words
Files: 61 (incl. scripts, references, assets)
Skills in repo: 36
Repo updated: Apr 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Creates and validates Salesforce Flows with 110-point scoring.

Works in 5 steps: Choose the right automation tool → Choose the right Flow type → Start from a template → …
Edits record-triggered
SKILL.md covers When This Skill Owns the Task, Required Context to Gather First, Recommended Workflow and High-Signal Rules, plus 5 more sections
Calls sf

What it does

Sf Flow is an agent skill from Jaganpro/sf-skills. Creates and validates Salesforce Flows with 110-point scoring. TRIGGER when: user builds or edits record-triggered, screen, autolaunched, or scheduled flows, or touches .flow-meta.xml files. DO NOT TRIGGER when: Apex automation (use sf-apex), process builder migration questions only, or non-Flow declarative config (use sf-metadata).

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 62 other files, including scripts, reference files and assets (for example `CREDITS.md`, `README.md` and `assets/architecture-review-template.md`).

It sits in Sales & Support, covering CRM management. It works with Salesforce. The repository describes itself as: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active… The licence is MIT.

When your agent uses it

Edits record-triggered
Scheduled flows
Touches .flow-meta.xml files
: Apex automation (use sf-apex)

Example prompts

“Use the sf-flow skill to create and validates Salesforce Flows with 110-point scoring”
“/sf-flow”

Workflow steps

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

Choose the right automation tool
Choose the right Flow type
Start from a template
Validate against Flow guardrails
Hand off deployment and testing

What it can do on your machine

Read from SKILL.md and the folder at commit 53c9956. 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
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
- sf
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

Sf Flow loads about 1.8k tokens when it runs, and up to ~94k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 563 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~86
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~94k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from Jaganpro/sf-skills at commit 53c9956, republished under its MIT licence (© Jaganpro). 563 words, ~1,808 tokens.

Download SKILL.mdSave it as .claude/skills/sf-flow/SKILL.md (or your agent's skills folder). This skill also uses 60 other files; get the full folder from GitHub.

name: sf-flow
description: Creates and validates Salesforce Flows with 110-point scoring. TRIGGER when: user builds or edits record-triggered, screen, autolaunched, or scheduled flows, or touches .flow-meta.xml files. DO NOT TRIGGER when: Apex automation (use sf-apex), process builder migration questions only, or non-Flow declarative config (use sf-metadata).
license: MIT
metadata.version: 2.1.0
metadata.author: Jag Valaiyapathy
metadata.scoring: 110 points across 6 categories

sf-flow: Salesforce Flow Creation and Validation

Use this skill when the user needs Flow design or Flow XML work: record-triggered, screen, autolaunched, scheduled, or platform-event Flows, including validation, architecture choices, and safe deployment sequencing.

When This Skill Owns the Task

Use sf-flow when the work involves:

.flow-meta.xml files
Flow Builder architecture and XML generation
record-triggered, screen, scheduled, autolaunched, or platform-event flows
Flow-specific bulk safety, fault paths, and subflow orchestration

Delegate elsewhere when the user is:

writing Apex-first automation → sf-apex
creating objects / fields first → sf-metadata
deploying metadata → sf-deploy
seeding post-deploy test data → sf-data

Required Context to Gather First

Ask for or infer:

flow type
trigger object / entry conditions
core business goal
whether this is new, refactor, or repair
target org alias if deployment or validation is needed
whether related objects / fields already exist

Recommended Workflow

1. Choose the right automation tool

Before building, confirm Flow is the right answer rather than:

formula field
validation rule
roll-up summary
Apex

2. Choose the right Flow type

Need	Default flow type
same-record update before save	before-save record-triggered
related-record work / emails / callouts	after-save record-triggered
guided UI	screen flow
reusable background logic	autolaunched / subflow
scheduled processing	scheduled flow
event-driven declarative response	platform-event flow
AI-evaluated routing (sentiment, intent, tone)	autolaunched with AI Decision element

3. Start from a template

Prefer the provided assets:

assets/record-triggered-before-save.xml
assets/record-triggered-after-save.xml
assets/screen-flow-template.xml
assets/autolaunched-flow-template.xml
assets/scheduled-flow-template.xml
assets/platform-event-flow-template.xml
assets/ai-decision-template.xml
assets/subflows/

4. Validate against Flow guardrails

Focus on:

no DML in loops
no Get Records inside loops
proper fault paths
correct trigger conditions
safe subflow composition
AI Decision elements not placed inside loops (credit cost per iteration)
AI Decision prompts include merge field references for data context

5. Hand off deployment and testing

Use:

sf-deploy for deploy / dry-run
sf-data for high-volume test data

High-Signal Rules

Flow architecture

before-save for same-record field updates
after-save for related records, emails, and callouts
do not loop over $Record
use subflows when logic becomes wide or repetitive

Bulk safety

no DML in loops
no Get Records in loops
test with 251+ records when bulk behavior matters
prefer Transform when the job is shaping data, not per-record branching

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

Error handling

every data-changing path should have fault handling
avoid self-referencing fault connectors
deploy Flows as Draft first when activation risk is non-trivial

Output Format

When finishing, report in this order:

Flow type and goal
Files created or updated
Architecture choices
Bulk/error-handling notes
Deploy/testing next steps

Suggested shape:

text

Flow: <name>
Type: <flow type>
Files: <paths>
Design: <trigger choice, subflows, key decisions>
Risks: <bulk safety, fault paths, dependencies>
Next step: <dry-run deploy, activate, or test>

Flow Testing (CLI)

Run Flow tests from the command line without VS Code:

bash

# Run all flow tests
sf flow run test --target-org <alias> --json

# Run tests for a specific flow
sf flow run test --class-names MyFlow --target-org <alias> --json

# Get results for an asynchronous run
sf flow get test --test-run-id <id> --target-org <alias> --json

Flow tests execute in the org and can take 1-5 minutes. sf flow run test returns a test run ID for asynchronous runs; use sf flow get test to retrieve results later. Always run with --json and use background execution for longer runs.

Cross-Skill Integration

Need	Delegate to	Reason
create objects / fields first	sf-metadata	schema readiness
deploy / activate flow	sf-deploy	safe deployment sequence
create realistic bulk test data	sf-data	post-deploy verification
create Apex actions / invocables	sf-apex	imperative logic
embed LWC in a screen flow	sf-lwc	custom UI components
expose Flow to Agentforce	sf-ai-agentscript	agent action orchestration

Reference Map

Start here

Design / orchestration

AI Decision

references/ai-decision-guide.md

Screen / integration / troubleshooting

Score Guide

Score	Meaning
88+	production-ready Flow
75–87	good Flow with some review items
60–74	functional but needs stronger guardrails
< 60	unsafe / incomplete for deployment

Files

SKILL.md and 60 other files (scripts, references, assets) in skills/sf-flow of Jaganpro/sf-skills.

SKILL.md
CREDITS.md
LICENSE
README.md
assets/ai-decision-template.xml
assets/apex-action-template.xml
assets/architecture-review-template.md
assets/autolaunched-flow-template.xml
assets/bypass-check-decision.xml
assets/elements/get-records-pattern.xml
assets/elements/loop-pattern.xml
assets/elements/record-delete-pattern.xml
assets/elements/transform-pattern.xml
assets/flow-documentation-template.md
assets/platform-event-flow-template.xml
assets/record-triggered-after-save.xml
assets/record-triggered-before-delete.xml
assets/record-triggered-before-save.xml
assets/scheduled-flow-template.xml
… and 42 more

Open the folder on GitHubat commit 53c9956

Compare with similar skills

Sf Flow 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.

Sf Flow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sf Flow this skillJaganpro/sf-skills	424	—	~1.8k	Automated safety check: Pass	MIT	5 mo ago
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib	154	—	~4.3k	Automated safety check: Pass	MIT	6 days ago
Soql Lib Selectorbeyond-the-cloud-dev/soql-lib	154	—	~2k	Automated safety check: Pass	MIT	6 days ago
Dev SetupPortwood-Global-Solutions/Portwood	126	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Automation Sandbox Post Copy Configureforcedotcom/sf-skills	1.1k	—	~5.3k	Automated safety check: Notes	Apache-2.0	2 days ago
Automation Sandbox Post Copy Configureforcedotcom/sf-skills	1.1k	—	~5.4k	Automated safety check: Notes	Apache-2.0	2 days ago

Similar skills

Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
154 GitHub stars~4.3k tokensUpdated 6 days ago
Sales & SupportAuto-check passed
Soql Lib Selector
beyond-the-cloud-dev/soql-lib
Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.
154 GitHub stars~2k tokensUpdated 6 days ago
Sales & SupportAuto-check passed
Dev Setup
Portwood-Global-Solutions/Portwood
Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.
126 GitHub stars~1.1k tokensUpdated today
Sales & SupportAuto-check passed
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
1.1k GitHub stars~5.3k tokensUpdated 2 days ago
Sales & SupportAuto-check: notes
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
1.1k GitHub stars~5.4k tokensUpdated 2 days ago
Sales & SupportAuto-check: notes
Google Maps Export
gmapsscraper/google-maps-agent-skills
Export Google Maps business data to CSV, JSON, or CRM format (HubSpot, Pipedrive, Salesforce).
132 GitHub stars~1.2k tokensUpdated 4 mo ago
Sales & SupportAuto-check passed

Questions about Sf Flow

What does Sf Flow do?

Creates and validates Salesforce Flows with 110-point scoring. Sf Flow is an agent skill from Jaganpro/sf-skills. Creates and validates Salesforce Flows with 110-point scoring.

When should I use Sf Flow?

Sf Flow fits situations like: edits record-triggered; scheduled flows; touches .flow-meta.xml files; : Apex automation (use sf-apex).

How do I install Sf Flow in Claude Code?

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

How do I install Sf Flow in Codex?

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

Can I use Sf Flow 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 Jaganpro/sf-skills --skill sf-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sf-flow, .gemini/skills/sf-flow, .github/skills/sf-flow and .opencode/skills/sf-flow in your project.

What does Sf Flow need to run?

Going by SKILL.md and its folder, Sf Flow needs the command-line tools its instructions call (sf).

Does Sf Flow 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 Sf Flow 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Sf Flow use?

Sf Flow is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sf Flow use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 92k tokens, read only when the agent opens those files.

What are the alternatives to Sf Flow?

Skills that share tags, products or a category with Sf Flow: Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars), Dev Setup (Portwood-Global-Solutions/Portwood, 126 stars) and Automation Sandbox Post Copy 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 Sf Flow?

Jaganpro (a GitHub user) maintains it in Jaganpro/sf-skills, which has 424 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on April 27, 2026.

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

Install Sf Flow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

sf-flow: Salesforce Flow Creation and Validation

When This Skill Owns the Task

Required Context to Gather First

Recommended Workflow

1. Choose the right automation tool

2. Choose the right Flow type

3. Start from a template

4. Validate against Flow guardrails

5. Hand off deployment and testing

High-Signal Rules

Flow architecture

Bulk safety

Error handling

Output Format

Flow Testing (CLI)

Cross-Skill Integration

Reference Map

Start here

Design / orchestration

AI Decision

Screen / integration / troubleshooting

Score Guide

Files

Compare with similar skills

Similar skills

More from Jaganpro/sf-skills

Related

Questions about Sf Flow