PaperclipOrg
Claude Agent Skill · by Jaganpro

Sf Flow

Install Sf Flow skill for Claude Code from jaganpro/sf-skills.

Works with Paperclip

How Sf Flow fits into a Paperclip company.

Sf Flow drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md210 lines
Expand
---name: sf-flowdescription: >  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: MITmetadata:  version: "2.1.0"  author: "Jag Valaiyapathy"  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](../sf-apex/SKILL.md)- creating objects / fields first → [sf-metadata](../sf-metadata/SKILL.md)- deploying metadata → [sf-deploy](../sf-deploy/SKILL.md)- seeding post-deploy test data → [sf-data](../sf-data/SKILL.md) --- ## 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 toolBefore 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 templatePrefer 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 guardrailsFocus 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 testingUse:- [sf-deploy](../sf-deploy/SKILL.md) for deploy / dry-run- [sf-data](../sf-data/SKILL.md) 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 ### 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: ```textFlow: <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 testssf flow run test --target-org <alias> --json # Run tests for a specific flowsf flow run test --class-names MyFlow --target-org <alias> --json # Get results for an asynchronous runsf 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](../sf-metadata/SKILL.md) | schema readiness || deploy / activate flow | [sf-deploy](../sf-deploy/SKILL.md) | safe deployment sequence || create realistic bulk test data | [sf-data](../sf-data/SKILL.md) | post-deploy verification || create Apex actions / invocables | [sf-apex](../sf-apex/SKILL.md) | imperative logic || embed LWC in a screen flow | [sf-lwc](../sf-lwc/SKILL.md) | custom UI components || expose Flow to Agentforce | [sf-ai-agentscript](../sf-ai-agentscript/SKILL.md) | agent action orchestration | --- ## Reference Map ### Start here- [references/flow-best-practices.md](references/flow-best-practices.md)- [references/flow-quick-reference.md](references/flow-quick-reference.md)- [references/orchestration.md](references/orchestration.md)- [references/testing-guide.md](references/testing-guide.md) ### Design / orchestration- [references/subflow-library.md](references/subflow-library.md)- [references/governance-checklist.md](references/governance-checklist.md)- [references/transform-vs-loop-guide.md](references/transform-vs-loop-guide.md)- [references/orchestration-guide.md](references/orchestration-guide.md)- [references/orchestration-parent-child.md](references/orchestration-parent-child.md)- [references/orchestration-sequential.md](references/orchestration-sequential.md)- [references/orchestration-conditional.md](references/orchestration-conditional.md) ### AI Decision- [references/ai-decision-guide.md](references/ai-decision-guide.md) ### Screen / integration / troubleshooting- [references/form-building-guide.md](references/form-building-guide.md)- [references/integration-patterns.md](references/integration-patterns.md)- [references/lwc-integration-guide.md](references/lwc-integration-guide.md)- [references/agentforce-flow-integration.md](references/agentforce-flow-integration.md)- [references/xml-gotchas.md](references/xml-gotchas.md)- [references/testing-checklist.md](references/testing-checklist.md)- [references/wait-patterns.md](references/wait-patterns.md)- [assets/](assets/) --- ## 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 |