AGENT SKILL

sf-flow

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
最近更新
2026-07-18
Stars
★ 0
Forks
1

01 前言 Front Matter

name
sf-flow
license
MIT
metadata
{ "author": "Jag Valaiyapathy", "scoring": "110 points across 6 categories", "version": "2.1.0" }
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).

03 SKILL.md 正文

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:


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:


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

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:

  1. Flow type and goal
  2. Files created or updated
  3. Architecture choices
  4. Bulk/error-handling notes
  5. Deploy/testing next steps

Suggested shape:

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:

# 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

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

04 同仓库更多 Skills

om-scogo
om-scogo/skillsh-scraper

arxiv-search

Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.

★ 0
om-scogo
om-scogo/skillsh-scraper

arxiv-search

Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.

★ 0
om-scogo
om-scogo/skillsh-scraper

working-with-legacy-code

Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.

★ 0
om-scogo
om-scogo/skillsh-scraper

working-with-legacy-code

Safely change and test untested codebases using Feathers' "Working Effectively with Legacy Code". Use when the user mentions "legacy code", "no tests", "untested codebase", "how do I test this", "seams", "characterization tests", "golden master", "sprout method", "afraid to change this code", "monster method", "dependency breaking", or "inherited a messy codebase". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout/wrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.

★ 0
om-scogo
om-scogo/skillsh-scraper

web-typography

Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.

★ 0
om-scogo
om-scogo/skillsh-scraper

web-typography

Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.

★ 0