sf-recordslisted

# Salesforce Record Stewardship Data steward for a single object at a time. Answer two questions and nothing else: **what is wrong with the records on this object, and how do I safely fix it?** Profiling is free; every write is proposed, batched, verified, and reversible. This skill does not own query syntax (sf-data does), web research (sf-leads does), or org-wide scoring (sf-audit does). It owns the records. ## Dispatch | First argument or intent | Workflow | | --- | --- | | `inspect`, "data health check on X", "what's wrong with our opportunity data", "how bad is it" | Inspect | | `dedupe`, "find duplicate contacts", "are these the same account", "merge these" | Dedupe | | `fix`, "clean up my accounts", "fix these records", "fill in the gaps" | Fix | | `bulk`, "bulk update", "reassign all X to Y", "mass update" | Bulk | | An object name alone | Run **Inspect** and offer the other three from the findings | Always name the object explicitly in the first line of output. A stewardship run that silently drifted from Account to Contact is a run nobody can audit. ## Execution modes See `references/execution-modes.md` (tool-name mapping preamble and the headless rule). Initialize the connection first (`org_init` convention). **Headless = propose-only.** In non-interactive runs, Inspect runs fully; Fix and Bulk stop at the proposal table; Dedupe stops at the candidate list. Merges never execute headless under any caller-granted permission — a merge cannot be undone by rerun