67
GitHub Stars
4
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill jaganpro/sf-skills --skill sf-flow- CREDITS.md6.4 KB
- LICENSE1.1 KB
- README.md3.8 KB
- SKILL.md23.8 KB
Overview
This skill creates and validates Salesforce Flow metadata using Winter '26 (API 65.0) best practices and a 110-point validation score. It generates production-ready Flow XML, enforces strict checks to prevent anti-patterns, and produces actionable validation reports and simulation results. Use it to build, review, and prepare flows for safe deployment.
How this skill works
The skill fills flow templates with provided requirements, enforces alphabetical XML ordering and API constraints, and runs an enhanced validator that scores across six categories (Design, Logic, Architecture, Performance, Error Handling, Security). It simulates record-triggered and scheduled flows against bulk test records and blocks generation or deployment if critical anti-patterns are detected. It also offers auto-fix options or guided manual fixes and integrates with a deploy step.
When to use it
- Creating new record-triggered, screen, autolaunched, scheduled, or platform-event flows
- Reviewing and hardening existing Flow XML before deployment
- Validating bulk safety and governor-limit behavior with 200+ record simulations
- Ensuring Flow metadata is API 65.0-compliant and follows naming/element-order rules
- Pre-deployment checks when flows reference newly created custom objects or fields
Best practices
- Never loop over triggered records; use $Record for single-record access and let the platform batch
- Query related records before loops; collect DML inside loops and perform a single DML after the loop
- Always include fault connectors for DML and queries; route faults to a dedicated error handler
- Set storeOutputAutomatically=false and select explicit fields to avoid data leaks
- Use entry conditions for after-save flows that update the same object to avoid infinite loops
- Keep API version at 65.0, use Auto-Layout (locationX/Y=0), and follow strict XML element ordering
Example use cases
- Generate an Auto_ prefixed after-save flow for lead assignment with automated validations and fault handling
- Validate and score an existing flow file and receive a 110-point report with prioritized fixes
- Simulate a record-triggered flow with 200+ test records to expose bulkification or SOQL-in-loop issues
- Create an autolaunched subflow template for reusable actions like SendEmailAlert or UpdateRelatedRecords
- Prepare scheduled cleanup flows with proper fault paths and security checks before deployment
FAQ
Generation is blocked. You get a clear explanation and options to refactor to the recommended pattern or request an explicit exception with documented justification.
Do I need to run simulations for every flow type?
Simulations are required for record-triggered and scheduled flows to validate bulk safety; other types should be validated and tested per their specific testing checklist.