# Sf Flow

> Creates and validates Salesforce Flows (Brite edition) with 110-point scoring. TRIGGER when user builds or edits record-triggered, screen, autolaunched, or scheduled flows, touches .flow-meta.xml files, works in brite-salesforce, asks about the Apex-first flow policy (Flows only for screen flows + simple notifications), the Screen-Flow-deploy-as-Draft trap (regardless of source <statusActive</status), sf data update record failing to activate flows, post-deploy Tooling API verification (SELECT Status FROM Flow WHERE Definition.DeveloperName = '...'), scratch-org flow activation gaps, or /revops:post-deploy-runbook Phase 2 cross-reference. DO NOT TRIGGER when Apex automation (use sf-apex), process builder migration questions only, or non-Flow declarative config (use sf-metadata).

## Facts
- Page: https://tashan.sh/capability/skill-brite-nites-sf-flow
- tashan id: skill:Brite-Nites/sf-flow
- Source: https://github.com/Brite-Nites/brite-claude-plugins
- Type: skill
- Category: comms
- tashan score: not scored (catalogued only — too little public evidence)
- Adoption: 9.0
- Upkeep: 95.0
- Freshness: 90.0
- Evidence coverage: 84% of the inputs this score can use
- Health: active
- Instruction depth: not yet graded
- Official: no

## Install

```sh
cp -r sf-flow ~/.claude/skills/
```

## Security audit
Not scanned. We audit npm-published capabilities; this one has no npm package we can resolve, or has not reached the queue. This is not a clean bill of health.

---
Measured 2026-09-12 by tashan (https://tashan.sh) from public evidence. Scorer s5.