Crm opportunity summarizer
Skill sisodiabhumca/agent-skills/skills/crm-opportunity-summarizer
Production-Ready Agent Skills : product analytics, growth experiments, CRM, research synthesis, postmortems, data contracts, SaaS spend, compliance, architecture maps, and LLM eval and many more.
npx -y skills add sisodiabhumca/agent-skills --skill crm-opportunity-summarizerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a sales rep or RevOps lead needs a concise opportunity summary from Salesforce or HubSpot — pulling stage, amount, contacts, recent activity, and risks, then producing a deal brief and recommended next-best-action.
SKILL.md
1.7 KB, 381 tokens by cl100k_base, as published. Nobody here has run it
CRM Opportunity Summarizer
When to invoke
- "Summarize the Acme Corp deal."
- "Give me a brief on my top 5 open opps."
- "What's at risk in our Q2 pipeline?"
Inputs needed
- CRM — Salesforce or HubSpot.
- Filter — opportunity ID(s), owner, stage, or close-date range.
- Context depth — quick (just record fields) or deep (include emails, calls, notes).
Workflow
- Resolve — find the opportunity records via API or CSV.
- Aggregate — pull stage, amount, contacts, owner, last activity, age in stage.
- Score risk — flag stalled, no-MEDDIC, no-economic-buyer, slipped close date.
- Draft brief — TL;DR, key facts, risks, recommended next-best-action.
- Hand off — Markdown brief per opp, or a single roll-up table.
Output format per opportunity
## <Account> — <Opportunity Name>
**Stage:** ... | **Amount:** $... | **Close:** YYYY-MM-DD | **Owner:** ...
**TL;DR:** <one line>
**Key contacts:** ...
**Recent activity:** <last 3 touches>
**Risks:**
- ...
**Next best action:** <specific, owned, dated>
Guardrails
- Never invent contacts, amounts, or dates not in the source data.
- If MEDDIC/BANT fields are missing, state "missing" — do not infer.
- Mark records with no activity in 14+ days as "stalled".
Reference code
summarize.py reads from Salesforce REST, HubSpot CRM API, or a CSV export and emits Markdown briefs.