⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

deal-premortem

@dhand-personal⭐ 0 stars

Runs a premortem on one live sales deal. Assumes the deal has already failed, works backward to the most likely causes using the account's real communications and CRM data, and ends with dated tripwires. Use whenever a rep or manager asks to premortem, stress test, or pressure test an open deal, or asks \"how could this deal die,\" \"what could kill this opp,\" \"what am I missing on Acme,\" or \"poke holes in this deal before my forecast call,\" even if they never say the word premortem. Not for closed deals (use a postmortem skill) and not for forecast category, qualification grading, or deal status (use a deal review skill). Pulls account history through unified-communication by default, or works from a pasted transcript, email thread, or notes.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐ 0 on GitHubGitHub ↗

New / niche

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

deal-premortem

A Claude skill that runs a premortem on one live sales deal.

It assumes the deal has already failed, works backward to the most likely causes using the account's real communications and CRM data, and ends with dated tripwires you can check against.

Why a premortem

Asking "is this deal on track?" invites reasons to say yes. Asking "it failed, what happened?" gets people to name the risks they were avoiding. The technique comes from Gary Klein's project premortem. This skill applies it to a single open deal and ties every finding to the record, so the output is specific to the account and not a generic list of deal risks.

What it does

  • Builds a sourced baseline: stage, amount, close date, next step, stakeholders, competitors, and what the buyer has said about timing, budget, and decision process.
  • Sets a failure date and a failure type, then writes the 5 to 7 most likely causes (fewer for a small deal).
  • Tests each cause against two layers: the methodology in use (MEDDPICC, Command of the Message, Sandler, BANT, SPICED, Challenger, or others) and the things no methodology tracks, such as reorgs, spending freezes, security reviews, and procurement lead time.
  • Tags each cause as signal present, unknown, or contradicted, with a dated source.
  • Names the most likely cause, the most dangerous cause, and the biggest hidden assumption.
  • Plays the adversary: the competitor, status quo, or internal skeptic who benefits if the deal fails.
  • Ends with 3 to 5 tripwires, each with an observable signal, a check date, and a stop result.

What it does not do

  • It does not assign a forecast category, a score, or a win probability.
  • It does not grade qualification. That is a deal review.
  • It does not analyze closed deals. Use a postmortem for those. See deal-postmortem.
  • It does not write to your CRM, send messages, or create tasks. It proposes changes and waits for your approval.

Inputs

  • The account name, and which opportunity if more than one is open.
  • Communications for the account. The skill uses the unified-communication skill if you have it. If not, paste a transcript, email thread, or notes.
  • A CRM snapshot, optional. If a HubSpot or Salesforce connector is available, the skill reads the opportunity (read only). Without one, it asks for the close date, amount, and stage.

Install

The skill is one file, SKILL.md, in a folder named deal-premortem.

  • Claude (web, desktop, mobile): zip the deal-premortem folder so SKILL.md sits inside it, then upload it as a custom skill in your Claude settings. Check Anthropic's current documentation for the exact steps, since the settings layout changes.
  • Claude Code: copy the deal-premortem folder into your skills directory, for example ~/.claude/skills/.

Companion skills

This skill works on its own. It is built to pair with:

  • unified-communication, which gathers email, call transcripts, CRM activity, and notes for an account.
  • crm-deal-updater, which can log approved tripwires to your CRM.
  • deal-postmortem, the closed-deal counterpart.

If a companion is not installed, the skill says so and falls back to pasted material or a plain summary.

Example prompts

  • "Run a premortem on the Acme renewal."
  • "How could this deal die? Here is the email thread."
  • "Poke holes in the Northwind opportunity before my forecast call."

License

MIT. See LICENSE.

// HOW IT'S BUILT

KEY FILES

SKILL.mdREADME.md

// REPO STATS

0 stars