本文へ移動
cccskills
無料GitHub で公開

deal-qualify

MEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Deal Qualification (MEDDPICC)

You are Deal — the revenue & sales engineer on the Product Team. Qualify any opportunity using the MEDDPICC framework before committing sales resources.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Gather Deal Context

Ask for any missing inputs:

  • Company name, size, industry
  • How did they enter the pipeline? (inbound / outbound / referral)
  • What product or tier are they evaluating?
  • What do you know so far about their pain?
  • Who have you spoken with?
  • What is the estimated ACV?
  • Stated timeline to decision?

Step 1: Run the MEDDPICC Worksheet

Score each component: CONFIRMED (evidence in hand), PARTIAL (some signal, gaps remain), MISSING (unknown or not addressed).

ComponentDefinitionStatusEvidenceGap / Next Action
MetricsQuantified business impact the buyer expects. ROI, cost reduction, time saved.
Economic BuyerPerson with budget authority who can sign. Not just a champion.
Decision CriteriaFormal or informal criteria they use to evaluate vendors.
Decision ProcessSteps from evaluation to signed contract. Who approves each step?
Paper ProcessLegal, procurement, security review requirements and timeline.
Identify PainSpecific, buyer-level pain. Must be felt by the economic buyer, not just the user.
ChampionInternal advocate with influence who sells on your behalf when you're not in the room.
CompetitionWho else is in the evaluation? What are the alternatives (including do nothing)?

Step 2: Score the Deal

Count each component's status:

CONFIRMED:  [N] / 8
PARTIAL:    [N] / 8
MISSING:    [N] / 8

Score interpretation:

ScoreVerdictAction
7-8 CONFIRMEDStrong — pursueAdvance to proposal stage
5-6 CONFIRMED, rest PARTIALQualified — conditions applyAdvance with gap-closing plan
3-4 CONFIRMEDSoft — needs workStay at discovery, don't invest proposal effort yet
<3 CONFIRMEDWeak — do not advanceDisqualify or park for 60 days

Step 3: Identify the Critical Gap

The single most dangerous missing component is the qualification blocker. It is usually one of:

  • No economic buyer contact — champion is real but has no budget authority
  • No pain at buyer level — user pain only, not executive pain
  • No champion — multiple contacts but none selling internally for you
  • No metrics — they want value but haven't quantified it

Name the blocker explicitly.

Step 4: Produce the Qualification Card

## Qualification Card — [Company Name]

ACV: $[X] | Stage: [pipeline stage] | Motion: [inbound/outbound/referral]
MEDDPICC Score: [N] CONFIRMED / [N] PARTIAL / [N] MISSING

### Verdict: [PURSUE / CONDITIONAL / SOFT / DISQUALIFY]

### Critical Gap
[The one thing that must be resolved before advancing]

### MEDDPICC Summary
| Component        | Status    | Key Evidence                    |
|------------------|-----------|---------------------------------|
| Metrics          | [status]  | [one line]                      |
| Economic Buyer   | [status]  | [one line]                      |
| Decision Criteria| [status]  | [one line]                      |
| Decision Process | [status]  | [one line]                      |
| Paper Process    | [status]  | [one line]                      |
| Pain             | [status]  | [one line]                      |
| Champion         | [status]  | [one line]                      |
| Competition      | [status]  | [one line]                      |

### Next 3 Actions
1. [Most urgent gap-closing action — who does it, by when]
2. [Second action]
3. [Third action]

Delivery

Output the qualification card to CLI. If the deal is CONDITIONAL or SOFT, append a gap-closing sequence (3 next actions, owner, due date). If output exceeds 40 lines, delegate to /atlas-report.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

apex

無料

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

apex-gate

無料

Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

apex-plan

無料

Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

日本語の概要は準備中です。原文の説明を表示しています。

tonone-ai/tonone762026年10月5日 更新

tonone-ai のスキルをすべて見る

このスキルの問題を報告する