HomeSkillsSkills for StrategyAndrew PershJuly 11, 202611 min read

50 Tier-1 Strategy Skills for Claude: Full Engagement

A strategy operating system for Claude. 50 standalone skills across six engagement domains, diagnose the problem, map the market, choose a path, execute, govern value, and communicate the recommendation.

30,000+ consultants, bankers, private equity professionals

Free skills and prompts for Claude and strategy work

Templates for Claude, ChatGPT and Perplexity — from diagnostics to board-ready decks.

What these strategy skills for Claude are

50 standalone strategy skills for Claude, grouped into six practical engagement domains. Each skill is a small, uploadable workflow that teaches Claude how to perform one high-value strategy task with a repeatable, tier-1 method.

Together, they operate like a strategy operating system for a full engagement: diagnose the problem, map the market, choose a strategic path, translate it into execution, govern value, and communicate the recommendation. Built for operators, consultants, analysts, founders, and strategy teams who want Claude to work closer to a tier-1 strategy consultant, structured before analytical, hypothesis-led before exhaustive, and executive-ready before verbose.

Prefer one deep workflow over a library? Start with the problem-solving skill, which walks a single ambiguous question through structured stages. Want a shorter starter set instead? See these 10 strategy skills before you load the full fifty.

Mechanically, each skill is one folder with a SKILL.md file, grouped by domain inside the zip. Install just the ones you need, or load the full set.

Download all 50 skills

One zip, one folder per skill. Free, no signup.

Download the zip

The 50 Strategy Skills You Get

The collection is grouped into six engagement domains. They run in the order a real engagement does, diagnose first, communicate last, but every skill is also useful on its own.

1

Domain 1 · 8 skills

Problem Framing & Diagnosis

Use these when the team needs the real problem, not the obvious symptom. Fact base first, root-cause discipline, explicit assumptions, and a single sharp question to answer.

1.1

Situation Assessment

Use when: You need the factual baseline before choosing a direction

Output: Fact base, momentum read, and prioritized issues list

1.2

Problem Definition

Use when: The problem is stated as a symptom or is too broad to solve

Output: One-page problem statement and the key question to answer

1.3

Issue Tree Builder

Use when: A big question must be broken into testable sub-questions

Output: MECE issue tree with branches ranked by impact

1.4

Root Cause Analysis

Use when: A problem keeps recurring and symptoms are being treated

Output: Root-cause map and the drivers worth fixing

1.5

Growth Barrier Diagnosis

Use when: Growth has stalled and leadership is debating symptoms

Output: Ranked constraint diagnosis and the evidence to confirm it

1.6

Assumption Audit

Use when: A strategy rests on beliefs that may be weak or untested

Output: Assumption register with a test plan per assumption

1.7

Hypothesis Design

Use when: You want an answer-first plan instead of boiling the ocean

Output: Prioritized hypothesis set and the analyses that test each

1.8

Diagnostic Workplan

Use when: You need to turn the question into a sequenced analysis plan

Output: Workplan with analyses, data needs, owners, and sequence

2

Domain 2 · 9 skills

Market & Competitive Intelligence

Use these when the answer depends on where value sits, how customers differ, how rivals may move, and where the attractive white space is.

2.1

Market Sizing

Use when: You need a defensible size for a market or opportunity

Output: Sized market with method, assumptions, and a sensitivity range

2.2

Market Mapping

Use when: You need to see the full landscape and where you sit in it

Output: Market map, players by role, and the flows of value

2.3

Competitor Analysis

Use when: You need a clear read on rivals and industry structure

Output: Competitor profiles and a five-forces structural read

2.4

Competitive Dynamics

Use when: You need to predict how rivals will respond to your move

Output: Likely competitor moves and your pre-planned responses

2.5

Customer Segmentation

Use when: You need sharper customer groups to steer strategy

Output: MECE segments, sizes, needs, and priority segments

2.6

Voice of Customer

Use when: You need the real jobs and triggers behind buying behavior

Output: Job map, pains and gains, and demand drivers ranked

2.7

Profit Pool Analysis

Use when: You need to know where value is created and captured

Output: Profit-pool map and the strategic implication of each pool

2.8

White Space Mapping

Use when: You need to find where to expand or where rivals are absent

Output: White-space opportunities scored on fit and attractiveness

2.9

Trend and Disruption Scan

Use when: You need to test the strategy against how the world is shifting

Output: Trend map, disruption vectors, and the so-what for strategy

3

Domain 3 · 9 skills

Strategic Choice & Economics

Use these when leaders need real choices, trade-offs, economics, and allocation decisions. Push Claude toward option-aware, evidence-backed recommendations instead of single-answer advocacy.

3.1

Where to Play, How to Win

Use when: You need a coherent strategic direction, not a list of ideas

Output: A linked choice cascade with the logic that makes it win

3.2

Strategic Options

Use when: You need alternatives before committing to a single path

Output: Three to five real options with the theory of each

3.3

Options Evaluation

Use when: You need to compare options on the same evidence bar

Output: Scored options, trade-offs, and a defensible recommendation

3.4

Business Case Builder

Use when: A decision needs economics, sensitivities, and risks

Output: Business case with base, upside, downside, and decision logic

3.5

Pricing Strategy

Use when: Pricing power, discounting, or monetization is unclear

Output: Pricing diagnosis, model, and an action plan

3.6

Portfolio Review

Use when: You must allocate scarce resources across many bets

Output: Portfolio diagnosis, invest/hold/exit calls, and allocation

3.7

Build, Buy, or Partner

Use when: You need to close a capability or market gap

Output: A build/buy/partner recommendation with the reasoning

3.8

Capital Allocation

Use when: Too many investments compete for limited capital

Output: Ranked investment slate and the allocation rationale

3.9

Go-to-Market Strategy

Use when: You have an offer and need the route to the customer

Output: GTM plan: target, channels, offer, motion, and milestones

4

Domain 4 · 8 skills

Operating Model & Execution

Use these when the strategy must become work: capabilities, decision rights, initiative choices, roadmaps, owners, and the first 90 days.

4.1

Operating Model Design

Use when: Strategy needs translation into how work actually gets done

Output: Operating-model design with capabilities and governance

4.2

Decision Rights

Use when: Decisions stall because ownership is unclear

Output: Decision map with clear owners and escalation paths

4.3

Initiative Prioritization

Use when: Too many initiatives compete for attention and money

Output: Ranked roadmap of initiatives and what to stop doing

4.4

Transformation Roadmap

Use when: A strategy must become sequenced, ownable delivery

Output: Phased roadmap with waves, milestones, owners, and risks

4.5

Org Design

Use when: The current structure blocks the strategy

Output: Org design options with spans, layers, and trade-offs

4.6

Capability Building

Use when: The strategy needs skills the organization lacks today

Output: Capability gap map and a plan to close each gap

4.7

First 90 Days Plan

Use when: A launch or new mandate needs momentum from day one

Output: A 30/60/90 plan with owners, early wins, and checkpoints

4.8

Change and Adoption

Use when: The change will fail on adoption, not on logic

Output: Change plan: awareness, buy-in, enablement, and reinforcement

5

Domain 5 · 8 skills

Risk, Performance & Value Governance

Use these when the recommendation needs pressure-testing, risk control, measurement, and value capture. The bar is a board-ready governance view, not a generic risk list.

5.1

War Gaming

Use when: A strategy needs pressure-testing before it launches

Output: Scenario stress test and the response moves that survive it

5.2

Risk and Mitigation

Use when: Strategic risk needs an owner and a response plan

Output: Risk register, heat map, and mitigation owners

5.3

Pre-Mortem

Use when: You want failure modes surfaced before you commit

Output: Ranked failure modes and the safeguards for each

5.4

Scenario Planning

Use when: The future is uncertain and you need robust choices

Output: Scenarios, signposts to watch, and no-regret moves

5.5

KPI Architecture

Use when: Metrics are noisy, lagging, or performative

Output: A KPI tree that ties every metric to a decision

5.6

Value Driver Tree

Use when: You need to show how the strategy creates value

Output: A driver tree from top-line value to operational levers

5.7

Value Realization

Use when: Benefits must be tracked and captured after launch

Output: Value ledger, gates, and a benefit-capture governance model

5.8

Governance Design

Use when: Delivery needs oversight without slowing it down

Output: Governance model: gates, forums, cadence, and decisions

6

Domain 6 · 8 skills

Alignment & Executive Communication

Use these when the work must survive the room: pre-wire stakeholders, sharpen the executive story, and turn the recommendation into a written decision.

6.1

Stakeholder Alignment

Use when: The recommendation needs pre-wiring before the meeting

Output: Stakeholder map and a one-by-one engagement plan

6.2

Pyramid Storyline

Use when: You need the argument to land in the first 60 seconds

Output: Governing thought, supporting lines, and the story spine

6.3

Executive Summary

Use when: A busy executive needs the answer on one page

Output: A one-page executive summary that leads with the answer

6.4

Decision Memo

Use when: A decision must be made in writing, not in a meeting

Output: Decision memo with options, recommendation, and next steps

6.5

Board Deck Structuring

Use when: You need a board-ready deck structure before you build it

Output: A storyboard: action titles, message per slide, and flow

6.6

Insight Synthesis

Use when: You have findings but not yet an insight

Output: Findings turned into ranked insights and their implications

6.7

Objection Handling

Use when: The recommendation will face a tough room

Output: The hard questions and a tight answer for each

6.8

Recommendation and Next Steps

Use when: The work must end in a decision and an action

Output: The recommendation, the ask, owners, and the timeline

Domains 1-2 sharpen the diagnosis and the market view. Domains 3-4 turn that view into a choice and a plan. Domains 5-6 govern delivery and land the recommendation with the people who matter.

Setup Guide

Step 1

Download the skills pack

Download all 50 skills (.zip)

The zip contains all 50 skills, one folder per skill. Each skill is a single SKILL.md file. Unzip it anywhere. Keep the whole set, or pull out just the folders you need.

Step 2

Create a Claude Project

Go to claude.ai, open the left sidebar, click Projects, then Create Project. Name it something like "Strategy Assistant" or "Strategy Co-pilot" so you can reuse it across engagements.

Claude Projects view with the New project button highlighted
Step 3

Add the skills as Project Knowledge

Inside your project, open Project Knowledge, click Add Content, and upload the .md files. Add as many as you want, one skill, an entire domain, or all 50. Claude will reference them automatically in every conversation inside that project.

Finder window with the skill markdown files being dragged into the Claude project Files panel
Step 4

Start using the skills

Open a new conversation inside the project, paste in your data, and name the skill you want Claude to run. Claude reads it from project knowledge and runs the analysis with the framework already loaded.

Tip

Refer to the skill by name in your prompt. Phrases like "Use the market-mapping skill" or "Run the assumption-audit skill" point Claude at the right framework instead of leaving it to guess.

Claude conversation using a strategy skill, with the skill reference highlighted in the prompt

Example prompts

  • "Use the market-sizing skill to size the opportunity for a B2B payments product in Germany."
  • "Use the assumption-audit skill to pressure-test our expansion strategy before the board meeting."
  • "Use the pyramid-storyline skill to turn this recommendation into an executive story."
  • "Use the initiative-prioritization skill to cut this list of 18 projects into the 3 that matter."

How to choose a skill

Skip the directory hunt. Pick the row that matches your need and use that skill.

Your need
Skill to use
Truth about the current situation
Situation Assessment
Sharpen a vague problem
Problem Definition
Break a big question into parts
Issue Tree Builder
Stop a problem recurring
Root Cause Analysis
Unblock stalled growth
Growth Barrier Diagnosis
Test strategy beliefs
Assumption Audit
An answer-first plan
Hypothesis Design
Size a market
Market Sizing
See the whole landscape
Market Mapping
Read rivals and industry structure
Competitor Analysis
Predict competitor moves
Competitive Dynamics
Sharper customer groups
Customer Segmentation
Find where the money is made
Profit Pool Analysis
Find where to expand
White Space Mapping
A coherent strategic direction
Where to Play, How to Win
Options before deciding
Strategic Options
Economics of a move
Business Case Builder
Better monetization
Pricing Strategy
Allocate across bets
Portfolio Review
Route to the customer
Go-to-Market Strategy
Redesign how work happens
Operating Model Design
Cut the initiative list
Initiative Prioritization
Sequenced delivery plan
Transformation Roadmap
Momentum from day one
First 90 Days Plan
Stress-test before launch
War Gaming
Strategic risk control
Risk and Mitigation
Robust choices under uncertainty
Scenario Planning
Better metrics
KPI Architecture
Win approval before the meeting
Stakeholder Alignment
A written executive decision
Decision Memo

The quality bar

Every skill is designed to push Claude toward outputs that meet the same partner-grade quality bar, the standard a senior associate would hold each deliverable to before it leaves the room.

Decision-oriented
Structured before analytical
Hypothesis-led
Evidence-aware
Assumption-conscious
Option-aware, not single-answer
Executive-readable
Specific enough to act on
Pressure-tested before they ship
Traceable from claim to source
Pyramid / SCQA-structured
Built for the partner, not the analyst