1. Set up
Try a plugin
The Sales plugin ships with /pipeline-review and other forecast-hygiene skills as a starting point, already structured to check your pipeline stage by stage and call out at-risk deals. If your admin manages plugins and it's not available yet, skip this step. The prompt below works without it.
/pipeline-reviewAnalyze pipeline health — prioritize deals, flag risks, get a weekly action plan./call-prepPrepare for a sales call with account context, attendee research, and suggested agenda.Connect your tools
Claude is more powerful when it works directly with your systems. You control permissions and access. Learn about tool access(opens in new tab).
Add a connector(opens in new tab) for each tool you want Claude to use.
Set your working folder
Drag the files you'll use (this week's pipeline export, last week's review doc, your stage definitions) into one folder on your machine, then give Claude access to it(opens in new tab) in the Claude desktop app. Claude reads from the folder and writes the scored sheet and review doc back to it. If you run pipeline weekly, create a project(opens in new tab) from that folder so your stage criteria, instructions, and memory stay attached.
2. The prompt
Copy this into Claude
Score each open opp in this week's pipeline on stage hygiene, whether there's a real next step, and how long it's sat in stage. Flag the at-risk deals and say why in one line each, then write the manager-ready review doc for our Monday pipeline meeting.
Why this works
Spell out your scoring criteria. "Hygiene, real next step, age in stage" gives Claude the rubric your manager uses, so the score means something in the meeting instead of being a generic health number.
Set a length limit per item. "Say why in one line each" keeps the at-risk section scannable, so the meeting time goes to the deals that need it rather than reading paragraphs.
Ask for the write-up alongside the data. "Manager-ready review doc" tells Claude to write the narrative around the scores, the part you'd otherwise type up Sunday night.
Put your reference docs in the folder. Your stage exit criteria and last week's review doc sit in the working folder, so hygiene is scored against your definitions and the doc follows the format your manager already expects.
Get a better draft
Add an example to match. Drop an example you like into the folder and Claude matches your structure and voice.
Ask it to flag uncertainty. Add "flag anything you're not confident about" so you know where to look first when you review the draft.
3. Make Claude work for you
Tell Claude your own rules for this task, such as your at-risk thresholds and your review doc format, then save what you've done as a skill of your own. A few minutes of conversation and it runs with your standards from then on.
Make what we've done in this task so far into a skill called /pipeline-score.
Review the skill, and save it if Claude hasn't already.
4. Make it repeatable
Run it before the Monday meeting
The review should be waiting before the meeting, not built during it. Ask Claude to set up a scheduled task, or open Scheduled in the sidebar, and /pipeline-score scores the pipeline and writes the doc every Monday morning.
Set up a scheduled task for every Monday at 8am: run /pipeline-score against the current Salesforce pipeline and write the scored sheet and review doc to a new folder under Pipeline named for the week.
Runs /pipeline-score against the current Salesforce pipeline and writes
the scored sheet and review doc to a weekly folder.
To use a folder on your computer during a scheduled task, keep your computer on and awake with the Claude desktop app open so Claude can access it.
5. Share with your teammates
Your /pipeline-score skill now carries your stage criteria, your at-risk thresholds, and your review doc format. Share it so every rep scores their own pipeline the same way, and the team meeting reads from one consistent doc per rep.