deal-classification

Classify open opportunities into Commit, Best Case, or Pipeline using CRM activity signals.

58|21|Updated May 15, 2026
One-click install
npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill deal-classification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deal-classification
Source: https://github.com/t0ddc3by/claude-for-customer-success/tree/main/rev-ops/skills/deal-classification
Command: npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill deal-classification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It resolves forecast and reporting ambiguity by independently classifying each open opportunity as Commit, Best Case, or Pipeline using CRM activity signals rather than rep self-reporting.

Core Features & Use Cases

  • Independent signal scoring across activity recency, stakeholder coverage, stage progression rate, competitive signals, and rep forecast accuracy.
  • Delta vs. rep forecast call that flags where the model disagrees by more than one tier, without overriding judgment.
  • Forecast-safe analytical output that includes the required data-as-of context and analytical-input language.

Quick Start

Use the deal-classification skill to classify the pipeline deals for a specific account or portfolio.

Frequently Asked Questions about deal-classification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify pipeline deals using CRM activity signals instead of rep self-reporting?

The model flags divergence when its independent classification disagrees with the rep stated forecast category by more than one tier, providing a delta report without overriding the rep's original judgment.

Can I run a portfolio sweep to validate rep forecast categories for forecast reporting?

Yes, you can run portfolio sweeps to validate rep stated forecast categories across open opportunities, generating a classification table with rep versus model delta flags to support forecast reporting and handoff readiness.

What CRM activity inputs are required for pipeline scoring and deal classification?

Pipeline scoring requires CRM activity inputs that include data-as-of timestamps to ensure forecast-safe analytical context, enabling the system to evaluate activity recency, stakeholder engagement, and competitive signals.

Does the deal classification model apply analytical-only guardrails to prevent CRM edits?

Yes, the deal classification model applies analytical-only guardrails meaning it processes CRM activity signals to output a classification table and divergence flags without making any direct CRM edits.

What is the best way to resolve forecast ambiguity for RevOps reporting?

Resolve forecast ambiguity by independently classifying each open opportunity as Commit, Best Case, or Pipeline using analytical CRM activity signals, producing a forecast-safe output with data-as-of context for RevOps reporting.