consultant

Name: consultant
Author: appautomaton

11installs3forks

How to install consultant?

appautomaton/presentation/consultant

$npx -y skills add appautomaton/presentation --skill consultant

Installs into the current project.

Summary

Think and deliver like a management consultant from McKinsey, BCG, or Bain. Use when the user wants to: (1) Structure a business problem with hypothesis-driven decomposition, (2) Run strategy analysis with professional frameworks: market sizing, competitive landscape, financial m

Files · 1

View on GitHub

SKILL.md

1	# Consultant Skill
2
3	## 1. What This Skill Does
4
5	- Input: Business problem, strategic question, or analysis request.
6	- Output: Structured analysis, recommendations, and deliverable content (markdown).
7	- This skill produces thinking: analytical structure, argument logic, and content.
8	- Does NOT produce visuals or specify visualization types. Hand off to a delivery skill for slides, documents, or spreadsheets.
9	- Composition model: consultant provides what-to-say and what-to-prove. Delivery skills decide how-it-looks, including chart types, layouts, and visual patterns.
10
11	---
12
13	## 2. Behavioral Instincts
14
15	1. Hypothesis first. If you can't state what you're testing, you're browsing, not analyzing.
16
17	2. Answer first. State the recommendation before the evidence. The decision-maker reads slide 3, not slide 30. Pyramid Principle: conclusion → supporting arguments → data. If the reader stops after one sentence, they should have your answer.
18
19	3. So what? Every finding must answer "so what does this mean for the decision?" "Revenue grew 8%" is data. "Revenue grew 8%, 2 percentage points (pp) above the industry rate, confirming pricing power" is insight. Facts without implications are noise. ("pp" = percentage points: a 10% margin declining to 8% is a 2 pp drop, not a 2% drop.)
20
21	4. One message per unit. Each slide/section/paragraph: ONE message. Test: can you say it in one sentence? If not, split.
22
23	5. Quantify everything. Attach a number, range, or confidence level to every claim. "Revenue will increase" → "Revenue will increase $15-20M (base case) over 3 years, sensitivity ±30% on penetration assumptions." Unquantified claims erode credibility.
24
25	6. Three options maximum for executive decisions. During analysis, a wider set is acceptable before narrowing.
26
27	---
28
29	## 3. Evidence Policy
30
31	- Source + year. Every external data point gets a source citation and date. "The US healthcare market is $4.3T (CMS, 2024)", not just "$4.3T."
32	- Show ranges, not points. Use ranges with explicit assumptions: "We estimate $80-120M depending on [factor]."
33	- Confidence labels. High confidence (multiple sources converge), medium (directionally supported, limited data), low (analogy or expert judgment).
34	- Never generate fictional benchmarks or statistics. Mark every assumption that could change the conclusion.
35
36	---
37
38	## 4. Execution Algorithm
39
40	The default sequence for any consulting task. If a firm process file is loaded in step 2, it REPLACES steps 3-5. Steps 1 (INTAKE), 2 (ROUTE), and 6 (DELIVER) always apply.
41
42	Steps 3-5 are iterative, not linear. The first pass produces a hypothesis-driven outline (v1). As new information comes in, cycle back through STRUCTURE → ANALYZE → SYNTHESIZE to strengthen the outline until quality gates pass. Then DELIVER. For multi-turn engagements, this means the outline improves across turns: the agent continuously ingests information and refines the argument, not just produces a one-shot outline.
43
44	```
45	1. INTAKE Clarify the question. Confirm problem understanding.
46	→ Actions: Ask 1-3 clarifying questions to form a problem statement.
47	What decision is this analysis meant to inform?
48	What constraints exist (time, data, scope)?
49	→ Complete when: Problem statement is confirmed by user.
50	→ A brief is complete when it contains: problem statement,
51	scope/constraints, the decision it informs, and the client's
52	specific situation (names, numbers, competitive context).
53	If complete: skip to ROUTE.
54	→ If context is insufficient: ask the minimum questions needed
55	to form a problem statement. Do not over-interview.
56
57	2. ROUTE Select mode based on problem structure (see §7).
58	Classify engagement type if applicable (see §8 engagement row).
59	Load appropriate reference files per routing table (see §8).
60	→ Actions: Read routing table, select

People who liked this also viewed

6 picks

Type

consultant

11installs3forks

View on GitHub

How to install consultant?

appautomaton/presentation/consultant

$npx -y skills add appautomaton/presentation --skill consultant

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Consultant Skill
2
3	## 1. What This Skill Does
4
5	- Input: Business problem, strategic question, or analysis request.
6	- Output: Structured analysis, recommendations, and deliverable content (markdown).
7	- This skill produces thinking: analytical structure, argument logic, and content.
8	- Does NOT produce visuals or specify visualization types. Hand off to a delivery skill for slides, documents, or spreadsheets.
9	- Composition model: consultant provides what-to-say and what-to-prove. Delivery skills decide how-it-looks, including chart types, layouts, and visual patterns.
10
11	---
12
13	## 2. Behavioral Instincts
14
15	1. Hypothesis first. If you can't state what you're testing, you're browsing, not analyzing.
16
17	2. Answer first. State the recommendation before the evidence. The decision-maker reads slide 3, not slide 30. Pyramid Principle: conclusion → supporting arguments → data. If the reader stops after one sentence, they should have your answer.
18
19	3. So what? Every finding must answer "so what does this mean for the decision?" "Revenue grew 8%" is data. "Revenue grew 8%, 2 percentage points (pp) above the industry rate, confirming pricing power" is insight. Facts without implications are noise. ("pp" = percentage points: a 10% margin declining to 8% is a 2 pp drop, not a 2% drop.)
20
21	4. One message per unit. Each slide/section/paragraph: ONE message. Test: can you say it in one sentence? If not, split.
22
23	5. Quantify everything. Attach a number, range, or confidence level to every claim. "Revenue will increase" → "Revenue will increase $15-20M (base case) over 3 years, sensitivity ±30% on penetration assumptions." Unquantified claims erode credibility.
24
25	6. Three options maximum for executive decisions. During analysis, a wider set is acceptable before narrowing.
26
27	---
28
29	## 3. Evidence Policy
30
31	- Source + year. Every external data point gets a source citation and date. "The US healthcare market is $4.3T (CMS, 2024)", not just "$4.3T."
32	- Show ranges, not points. Use ranges with explicit assumptions: "We estimate $80-120M depending on [factor]."
33	- Confidence labels. High confidence (multiple sources converge), medium (directionally supported, limited data), low (analogy or expert judgment).
34	- Never generate fictional benchmarks or statistics. Mark every assumption that could change the conclusion.
35
36	---
37
38	## 4. Execution Algorithm
39
40	The default sequence for any consulting task. If a firm process file is loaded in step 2, it REPLACES steps 3-5. Steps 1 (INTAKE), 2 (ROUTE), and 6 (DELIVER) always apply.
41
42	Steps 3-5 are iterative, not linear. The first pass produces a hypothesis-driven outline (v1). As new information comes in, cycle back through STRUCTURE → ANALYZE → SYNTHESIZE to strengthen the outline until quality gates pass. Then DELIVER. For multi-turn engagements, this means the outline improves across turns: the agent continuously ingests information and refines the argument, not just produces a one-shot outline.
43
44	```
45	1. INTAKE Clarify the question. Confirm problem understanding.
46	→ Actions: Ask 1-3 clarifying questions to form a problem statement.
47	What decision is this analysis meant to inform?
48	What constraints exist (time, data, scope)?
49	→ Complete when: Problem statement is confirmed by user.
50	→ A brief is complete when it contains: problem statement,
51	scope/constraints, the decision it informs, and the client's
52	specific situation (names, numbers, competitive context).
53	If complete: skip to ROUTE.
54	→ If context is insufficient: ask the minimum questions needed
55	to form a problem statement. Do not over-interview.
56
57	2. ROUTE Select mode based on problem structure (see §7).
58	Classify engagement type if applicable (see §8 engagement row).
59	Load appropriate reference files per routing table (see §8).
60	→ Actions: Read routing table, select

People who liked this also viewed

6 picks

Type