Get a structured account read straight from your CRM.
A sixty-second summary, a multi-source activity audit, a qualification-vs-stage gap check, and an 8-state deal-risk verdict.
Inside: The multi-source activity check, the sandbagging detector, and the risk verdict.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads all of the above automatically, and audits activity across every source, not one field.
adds firmographic and buying-committee context. Deepline is one generic example.
tightens the last-touch and champion-drop checks.
This was built for a B2B SaaS org running a staged pipeline. Set these to your stack:
Run any methodology you like. The skill checks "is this account qualified for the stage it claims," so point it at your qualification fields, not anyone else's.
| Set this | What it is | Default / Example |
|---|---|---|
| STAGE field | the opportunity stage | your stage field |
| AMOUNT field | current and forecasted value | amountARRcontract value |
| QUALIFICATION fields | your methodology's fields | MEDDICBANTyour custom framework |
| ACTIVITY sources | every place a "last touch" lives | accountopptaskevent dates |
| CONTACT ROLES | how you see who is on a deal | your contact-role object |
| DARK_DAYS | no-activity days that mean at risk | 14 (re-tune to your cycle) |
| STUCK_DAYS | days in one stage that mean stuck | 21 (re-tune) |
Everything the skill does, in full.
Reads a single account or deal out of your CRM and gives a straight, structured read: current state, when it was last actually touched, whether the rep did the qualification work the stage claims, and one risk verdict on the deal. It is the sixty-second account summary that tells you what to do next, and the "is the rep BS-ing this deal" check that a single CRM field misses.
- 1Multi-source activity check
Days dark is today minus the most recent touch across ALL your activity sources: the account record, the opp record, completed tasks, and logged events. Never a single field. This solves the classic CRM bug where the opp-level last-activity date is blank because reps log emails and meetings at the account or contact level, so a live deal gets falsely flagged as dead. The skill takes the max across sources and shows the dates.
- 2Account summary (one screen)
Current state, owner, value, days in current stage, last real activity, and the single risk flag. The read a rep or leader needs before walking into a meeting, on one screen.
- 3Qualification-vs-stage gap
If a deal claims a late stage but the qualification fields for that stage are empty, flag it and name the exact field that is missing. This is the sandbagging detector. It is only as good as the fields you map.
- 4Deal-risk verdict
One verdict per open opp: HEALTHY, MOMENTUM, AT_RISK, SLIP_RISK, STUCK, STALE, CHAMPION_DROP, GHOST. GHOST needs every activity source cold and the dates to prove it. CHAMPION_DROP means the main contact has gone quiet. AT_RISK means single-threaded.
- 5Account context
Pull the firmographic and buying-committee context that lives on the record: decision maker, tech stack, hiring or expansion signals. An optional enrichment tool fills what the CRM does not carry.
- No GHOST verdict without showing the activity dates, across every source, that prove it.
- Qualification gaps surface field by field, named, never "incomplete."
- The activity check reads every source, never one field. A single-field read systematically misses real activity.
- Never report a field the export does not contain. A missing field is a prompt, not a guess.
ACME CORP · Customer · CSM: owner Verdict: REACH_OUT (renewal-defence read) Last activity: TODAY (account level) - 6 email replies + meeting in 1h Days in current stage: 12d (late stage) Qualification: 4/4 complete - problems, leverage, decision dynamics, next steps Fit-score check: score looks low, but real usage present -> false negative The qualification read PROBLEMS: inbox plateau, no signal on adoption depth LEVERAGE: multi-team rollout across Sales, RevOps, CS DECISION DYNAMICS: CFO signs, RevOps lead champions NEXT STEPS: finalize commercial terms by the 15th Tech stack: email, CRM, an outbound tool Decision maker: the CFO Signal: hiring 14 reps at this account - expansion Next move: the meeting today. Late stage means commercial close is the gate.
DARK_DAYS (14) and STUCK_DAYS (21) are defaults, not laws. They suited a mid-market SaaS cycle. If your deals run longer, raise them. The multi-source activity rule is not a threshold, it is the correct way to read a CRM, and it does not change. The thresholds are yours.
Where an operator takes this next.
The read is step one. Here's where an operator takes it once the manual version proves out.
You built the read once; now it runs itself.
Point a scheduled Claude task at Salesforce nightly and flag every deal that just moved from HEALTHY to AT_RISK or STUCK.
Post any qualification-vs-stage gap straight to the manager's Slack the moment a rep advances a stage without the fields to back it.
Wire the fit-score correction back into your scoring model's exception list so the same account doesn't get mis-scored again next cycle.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.