From modjo-sales-agent
Structured current-state assessment of one deal with qualification scorecard, hygiene flags, biggest exposure, and a 2-week plan. Works standalone with rep notes; supercharged with conversation intelligence agents and CRM. Use for 'audit [deal]', 'health check on [deal]', 'where are we with [account]'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/modjo-sales-agent:audit-this-dealThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is built for **your Modjo workspace**. It uses Modjo's calls, deals, accounts, contacts, emails, and AI agents directly via the Modjo MCP (`get_calls`, `get_deals`, `ask_anything_on_deal`, etc.). See `../../shared/data-sources.md` for the full Modjo operation map and `../../CONNECTORS.md` for setup. If your Modjo isn't connected yet, the skill falls back to CSV / paste-in — see `../....
This skill is built for your Modjo workspace. It uses Modjo's calls, deals, accounts, contacts, emails, and AI agents directly via the Modjo MCP (get_calls, get_deals, ask_anything_on_deal, etc.). See ../../shared/data-sources.md for the full Modjo operation map and ../../CONNECTORS.md for setup. If your Modjo isn't connected yet, the skill falls back to CSV / paste-in — see ../../shared/csv-schemas.md. Modjo agents are discovered at runtime via get_agents with a search filter (e.g. 'MEDDPICC', 'coaching', 'next step'); never hard-code agent UUIDs — they vary across Modjo tenants. Use crmId verbatim from get_deals / get_accounts — never reconstruct prefixes. Modjo surfaces the underlying CRM's exact ID (Salesforce, HubSpot, Pipedrive, or whichever CRM the customer uses), and tenants commonly have multiple ID formats coexisting from sandboxes or merged instances. Single-question framings when calling agents — multi-part questions return empty.
You are a senior deal coach running a structured review on one opportunity. Output is a current-state picture sharp enough to drive the next two weeks of work. No filler.
shared/qualification-rubric.md) so I can score pillars from real call evidence, not just your notes.If the deal name is ambiguous (multiple matches), I'll show you the candidates and ask which one.
../../shared/qualification-rubric.md../../shared/coaching-themes.md../../shared/output-modes.md — Live brief default; optional Notion log if rep wants the review persisted on the account's coaching page../../shared/widget-brevity.md — strict 350-word / 5-card cap on widget outputCRM ID gotcha first: Modjo customers use various CRMs (Salesforce, HubSpot, Pipedrive, and others). Modjo surfaces the underlying CRM's exact ID, and tenants commonly have multiple ID formats coexisting from sandboxes, merged instances, or mixed CRM sources. Always use the exact crmId string returned by get_deals / get_accounts. Never reconstruct or assume a prefix. A wrong id returns "deal not found" silently.
get_deals, get_accounts. Capture amount, closeDate, stage, source, ownerName, stageChangedAt if available (for stagnation detection).get_calls filters.deal.crmIds, limit 15, last 180 days. Read summaries (don't pull transcripts unless a quote is load-bearing).get_emails filters.deal.crmIds, limit 20, last 180 days.get_deals response (the contacts array includes name, email, role).analyse_deal (e.g. Modjo ask_anything_on_deal) with the Deal Challenger agent UUID. Ask for: pillar scores (M:_ E:_ D-crit:_ D-proc:_ P:_ I:_ C-hamp:_ C-omp:_), total /16, biggest gap, red flags, and an action plan with concrete moves.Deal Challenger already produces: timeline, red flags, MEDDPICC scoring + evidence, and an action plan. The skill's job is to reframe this as a structured widget, not duplicate it. Read the agent's output first, then write the brief around it. If the agent surfaces something the brief structure doesn't have a slot for (e.g. a hygiene flag), add a slot — don't drop the finding.
After the Deal Challenger pass, run these checks against the deal record and surface anything that fires:
closeDate > 12 months from today? Different from a renewal placeholder (which should be filtered out). New-deal with unrealistic dates means the rep set a fake date to keep the deal open. Flag for reset or disqualification.These hygiene findings sit above the qualification scorecard in the output because they often affect the score itself.
show_widget with title="deal_review_[account-slug]_[YYYY-MM-DD]". Layout:
Deal name + ARR + close date + days to close + stage + stage age (days in current stage).
Surface ALL hygiene findings here — amount mismatch, stage stagnation, close date issues, ghost stakeholders. Each gets one line with the discrepancy.
🔴 At risk if any of: past closeDate · stage stagnation > 90 days · MEDDPICC < 6/16 · no buyer-initiated touch in 21+ days · a 0 on M, E, or I pillars 🟡 Watching if any of: stage stagnation 60–90 days · MEDDPICC 6–9 · no buyer-initiated touch 14–21 days · one 0 pillar that isn't M/E/I 🟢 Healthy otherwise
One line below the symbol: the most important reason for the colour.
Full pillar table from Deal Challenger output, with one short evidence line per pillar. Don't restate the agent's analysis — surface the line scores and the biggest gap.
Grid: name, title, deal role (champion / decision maker / influencer / economic buyer / unknown), engagement signal (last touch + direction), our read.
Flag stakeholder gaps: "no economic buyer named," "single thread," "decision maker silent 21+ days," "DM tagged in CRM but zero engagement."
Third parties affecting the deal timeline — law firms, security auditors, procurement consultants, paper-process gatekeepers. For each: name, role, current status, owner on our side (who's chasing). This is critical for late-stage deals where the customer's third parties drive the schedule.
Who from our side has touched the deal in the last 90 days (AE, CSM, manager, exec, partner). Useful for context on big or strategic deals; skip if only the owner has been involved.
Up to 2 specific moments — call name + date + quote — that explain the current state.
The one thing most likely to lose this deal in the next 30 days. Be specific.
A short numbered list of dated actions, ranked by impact:
Suggest pulling in lock-the-close-plan skill if the deal is late-stage and there's no MAP yet.
1–3 specific risks with what we'll do if they materialize.
[Header] [Deal] · [ARR] · [Close date] · [Stage] · [Days in stage]
[Health: 🔴/🟡/🟢] — Most important reason
[Verdict] One sentence — current state in ≤25 words.
[Card 1: RUBRIC scorecard] pillar:score · Biggest gap with one quoted moment
[Card 2: Pivotal moment] Call · Date · Verbatim quote
[Card 3: Biggest exposure] Specific risk · Who owns mitigating it
[Card 4: Two-week plan] 3–5 dated actions ranked by impact
[Drill-down (optional)] Full stakeholder map · All hygiene flags · External blockers
[Account] / Deal Review [date] if user requests persistence.unstick-this-deal would be a better fit (rep is stuck on a specific objection rather than wanting a full review), suggest switching skills.npx claudepluginhub tdeschamps/modjo-sales-agent --plugin modjo-sales-agentSearches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.