Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Frame A Deal Thesis

ASecurity

State the deal thesis — why this target, why now, how value is created — in one sentence before any model is built. Reach for this at the very start of any acquisition, before valuation.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agents

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill frame-a-deal-thesis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Frame A Deal Thesis?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Frame A Deal Thesis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-frame-a-deal-thesis/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-frame-a-deal-thesis)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: frame-a-deal-thesis
description: "State the deal thesis — why this target, why now, how value is created — in one sentence before any model is built. Reach for this at the very start of any acquisition, before valuation."
---

# Skill: Frame a deal thesis

A deal with no thesis is a spreadsheet looking for a victim (§3 #1).

## Step 1 — Write the one-sentence thesis
State why **this** target, why **now**, and **how** it creates value (cost synergy / revenue synergy / capability / market access / defensive). If you can't say it in one sentence, you don't have a thesis — stop.

## Step 2 — Test buy vs build vs partner
Would building or partnering achieve the same outcome cheaper or faster? If yes, the acquisition thesis is weak. Traverse the buy-vs-build tree ([`../../knowledge/ma-decision-trees.md`](../../knowledge/ma-decision-trees.md)).

## Step 3 — Name the value-creation drivers
List the specific drivers with a rough magnitude and whether each is a cost synergy (higher confidence) or revenue synergy (lower confidence). These become the diligence assumptions to confirm or kill.

## Step 4 — Name the deal-breakers up front
State the two or three findings that would kill the deal regardless of price. These seed the diligence plan.

## Step 5 — State the walk-away
Name the price and the conditions beyond which you walk. A thesis with no walk-away is an intention to overpay.

## Output
A one-sentence thesis, a buy-vs-build/partner check, the value-creation drivers (cost vs revenue), the deal-breakers, and the walk-away — the seed for valuation and diligence. See [`../../templates/deal-thesis-memo.md`](../../templates/deal-thesis-memo.md).

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →