Why your CRM agent pulls the wrong deals
The MCP can read your deals. It doesn't know what “stalled” means at your company. A skill fixes that in an afternoon.
“I asked for stalled deals and it gave me everything closing this month.”
Why the stock MCP can’t do it
The stock MCP gives Claude a search tool with filters for stage, owner and close date. “Stalled” isn’t one of them. So Claude picks the closest filter it can see, close date this month, and returns everything in it.
Nothing is broken. The MCP answers the question it received. The definition of stalled lives in your head, your pipeline review, or an old Slack thread.
The fix: a skill that knows what stalled means
A skill is a short instruction file Claude loads when the task matches. This one tells Claude what stalled means at your company and points to a reference file with the stage rules.
# Loaded by the pipeline-review skill. Edit here when stages change.
stalled:
no_activity_days: 14
stages: [discovery, proposal, negotiation]
exclude:
- close_date_within_days: 7 # closing soon is not stalled, even if quietKeep the rules in the reference file, not the skill. When stages change, you edit one file.
Get the next MCP-gap post in your inbox. Every two weeks, no fluff.
Almost done. Check your inbox.
Click the link in the email to confirm. No confirmation, no emails.
Nothing else on this rung yet. Next up the ladder.
Comments
Loading comments…No comments yet. The form is right below.
Your connection or our server hiccuped. Your draft below is safe.
Your comment will appear after review.