forcedotcom/sf-skills / skills/sales-agentforce-pipeline-management-configure
sales-agentforce-pipeline-management-configure
VerifiedUse to configure, set up, or repair the Sales Management agent and Agentforce Pipeline Management in a Salesforce org. Automates metadata creation for flows, prompt templates, permission sets, and data source configuration. TRIGGER when: user wants to enable Pipeline Management, configure Sales pipeline features, set up the Sales Management agent for opportunity field updates (including autonomous updates), connect enabled data sources like Einstein Conversation Insights or Einstein Activity Capture, customize opportunity stage descriptions, configure post-meeting suggestions, verify or audit configuration status, fix partially configured orgs, or troubleshoot Pipeline Management metadata issues. DO NOT TRIGGER when: user wants to build a custom agent (use agentforce-generate), configure general Agentforce tracing (use platform-tracing-agentforce-configure), work with non-Sales agents, or enable Einstein Conversation Insights or Einstein Activity Capture from scratch (provisioning is out of scope).
references/flags.md
View on GitHub# setup-all.sh Flags Reference
- `--check-license` — **preflight only**: run auth + the capability gate, then exit (0 = capable, 1 = unlicensed with a printed blocker). Takes no `--fields`, asks nothing, changes nothing. Run this FIRST, before any clarifying question (Step 0 above).
- `--through-phase prompts` — run enablement → provisioning → prompt-template deploy/activate, then **stop before the flow is built**. Hands off to the agent tune-loop. (Call 1 above.)
- `--from-phase flow` — skip the already-done enablement/provisioning/templates and **resume at the flow build** (build + activate flow, agent, PSG recalc, final verify). Pass the same `--fields`. (Call 2 above.) Mutually exclusive with `--through-phase`.
- `--fields "NextStep,StageName,Risk__c"` — comma-separated Opportunity field API names to manage. **At least 1 is required**; setup aborts if zero are selected (no default to `NextStep`). Max 5 (OOTB fields count). Required in `--non-interactive` mode; interactive mode prompts for it. The flow is built with **only** these fields.
- `--field-goal "FieldName:<text>"` — custom goal for a specific field (repeatable; format `Field:text`). Only meaningful for non-`StageName` fields.
- `--field-instruction "FieldName:<text>"` — custom instruction for a specific field (repeatable; same format). For `NextStep`, supplying either flag deploys an OVERRIDE of the OOTB managed prompt; omit both to keep the OOTB prompt.
- `--skip-prompt-verification` — bypass the Phase 4e prompt-verification step entirely (which seeds a test opportunity + note and shows generated suggestions before activating the flow). In `--non-interactive` runs the step still **runs and prints** the generated suggestions (informational) — only the interactive yes/no *gate* is dropped, so the flow proceeds without blocking. **When you drive setup non-interactively (e.g. as an agent), relay the printed suggestions back to the user** so they get the review the interactive gate would have given.
- `--autonomous` — enable autonomous field updates (`enableDealAgentAutoApproveAllTasks=true`); the agent auto-applies suggestions with no human review. Omit to keep suggestions-only. In an interactive run the script asks; in `--non-interactive` mode it stays off unless the flag is passed.
- `--create-stage-descriptions` — create sales-methodology stage descriptions (needed only for `StageName` suggestions, and only prompted/relevant when `StageName` is in `--fields`). Omit to skip. Never auto-created silently in non-interactive mode.
- `--non-interactive` / `--yes` — run without prompts (also implied when stdin is not a TTY). Requires `--fields`. Combined with the opt-in flags this gives fully unattended setup; without them the run stays on the safe defaults.
- `--users "a@x.com,b@x.com"` — explicit comma-separated usernames to also grant the `SalesManagementUserPsg`, in addition to the running user. This is the **only** way to add users in a non-interactive run. **NEVER** query all users / all standard users and bulk-assign the PSG — grant only the running user plus the explicit `--users` (or interactively-typed) list. Email format is validated — each value must match a valid email pattern.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |