executive-briefing

Name: executive-briefing
Author: juntoku9

106stars1forks

How to install executive-briefing?

juntoku9/claude-for-crypto-research/executive-briefing

$npx -y skills add juntoku9/claude-for-crypto-research --skill executive-briefing

Installs into the current project.

Summary

Transforms research findings into executive-ready briefings. Automatically activated when user mentions 'executive', 'briefing', 'C-suite', 'board', 'leadership', or 'presentation'.

Files · 1

View on GitHub

SKILL.md

1	# Executive Briefing Skill
2
3	## Activation Triggers
4	This skill activates when the conversation mentions:
5	- "executive summary", "executive briefing"
6	- "C-suite", "board presentation", "leadership team"
7	- "stakeholder update", "management report"
8	- "one-pager", "key takeaways"
9
10	## Briefing Format
11
12	When creating executive briefings, always follow this structure:
13
14	### The BLUF Principle (Bottom Line Up Front)
15	Start with the conclusion. Executives are busy - lead with what matters.
16
17	### One-Page Format
18	```
19	═══════════════════════════════════════════════════════════
20	EXECUTIVE BRIEFING: [Topic]
21	Date: [Date] \| Prepared for: [Audience]
22	═══════════════════════════════════════════════════════════
23
24	BOTTOM LINE
25	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
26	[2-3 sentences: What they need to know and what to do about it]
27
28	KEY FINDINGS
29	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
30	• [Finding 1 - with data point if available]
31	• [Finding 2 - with data point if available]
32	• [Finding 3 - with data point if available]
33
34	IMPLICATIONS
35	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
36	What this means for [Company/Team]:
37	• [Implication 1]
38	• [Implication 2]
39
40	RECOMMENDED ACTIONS
41	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
42	1. [Action] - [Owner] - [Timeline]
43	2. [Action] - [Owner] - [Timeline]
44	3. [Action] - [Owner] - [Timeline]
45
46	RISKS & CONSIDERATIONS
47	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
48	• [Risk/Consideration 1]
49	• [Risk/Consideration 2]
50
51	═══════════════════════════════════════════════════════════
52	Sources: [Brief citation list]
53	Contact: [Who to reach out to for questions]
54	═══════════════════════════════════════════════════════════
55	```
56
57	## Style Guidelines
58
59	### Do:
60	- Use numbers and metrics where possible
61	- Keep sentences short and direct
62	- Use bullet points liberally
63	- Highlight decisions that need to be made
64	- Include clear next steps with owners
65
66	### Don't:
67	- Use jargon or technical terms without explanation
68	- Include lengthy background (link to appendix instead)
69	- Bury the recommendation
70	- Use passive voice
71	- Include information that doesn't drive a decision
72
73	## Data Presentation
74
75	When including data:
76	- Round numbers for readability (say "$2.3M" not "$2,347,892")
77	- Compare to benchmarks or previous periods
78	- Highlight deltas and trends
79	- Use comparisons that resonate ("10x faster" not "900% improvement")
80
81	## Confidence Indicators
82
83	Always indicate confidence level:
84	- HIGH CONFIDENCE: Multiple reliable sources, verified data
85	- MEDIUM CONFIDENCE: Good sources but some gaps
86	- LOW CONFIDENCE: Limited data, emerging information
87
88	## Appendix Guidelines
89
90	For detailed information, create a separate appendix file with:
91	- Full methodology
92	- Complete data tables
93	- Source documentation
94	- Technical details
95	- Extended analysis

People who liked this also viewed

6 picks

Type

executive-briefing

106stars1forks

View on GitHub

How to install executive-briefing?

juntoku9/claude-for-crypto-research/executive-briefing

$npx -y skills add juntoku9/claude-for-crypto-research --skill executive-briefing

Installs into the current project.

Summary

Transforms research findings into executive-ready briefings. Automatically activated when user mentions 'executive', 'briefing', 'C-suite', 'board', 'leadership', or 'presentation'.

Files · 1

View on GitHub

SKILL.md

1	# Executive Briefing Skill
2
3	## Activation Triggers
4	This skill activates when the conversation mentions:
5	- "executive summary", "executive briefing"
6	- "C-suite", "board presentation", "leadership team"
7	- "stakeholder update", "management report"
8	- "one-pager", "key takeaways"
9
10	## Briefing Format
11
12	When creating executive briefings, always follow this structure:
13
14	### The BLUF Principle (Bottom Line Up Front)
15	Start with the conclusion. Executives are busy - lead with what matters.
16
17	### One-Page Format
18	```
19	═══════════════════════════════════════════════════════════
20	EXECUTIVE BRIEFING: [Topic]
21	Date: [Date] \| Prepared for: [Audience]
22	═══════════════════════════════════════════════════════════
23
24	BOTTOM LINE
25	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
26	[2-3 sentences: What they need to know and what to do about it]
27
28	KEY FINDINGS
29	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
30	• [Finding 1 - with data point if available]
31	• [Finding 2 - with data point if available]
32	• [Finding 3 - with data point if available]
33
34	IMPLICATIONS
35	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
36	What this means for [Company/Team]:
37	• [Implication 1]
38	• [Implication 2]
39
40	RECOMMENDED ACTIONS
41	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
42	1. [Action] - [Owner] - [Timeline]
43	2. [Action] - [Owner] - [Timeline]
44	3. [Action] - [Owner] - [Timeline]
45
46	RISKS & CONSIDERATIONS
47	━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
48	• [Risk/Consideration 1]
49	• [Risk/Consideration 2]
50
51	═══════════════════════════════════════════════════════════
52	Sources: [Brief citation list]
53	Contact: [Who to reach out to for questions]
54	═══════════════════════════════════════════════════════════
55	```
56
57	## Style Guidelines
58
59	### Do:
60	- Use numbers and metrics where possible
61	- Keep sentences short and direct
62	- Use bullet points liberally
63	- Highlight decisions that need to be made
64	- Include clear next steps with owners
65
66	### Don't:
67	- Use jargon or technical terms without explanation
68	- Include lengthy background (link to appendix instead)
69	- Bury the recommendation
70	- Use passive voice
71	- Include information that doesn't drive a decision
72
73	## Data Presentation
74
75	When including data:
76	- Round numbers for readability (say "$2.3M" not "$2,347,892")
77	- Compare to benchmarks or previous periods
78	- Highlight deltas and trends
79	- Use comparisons that resonate ("10x faster" not "900% improvement")
80
81	## Confidence Indicators
82
83	Always indicate confidence level:
84	- HIGH CONFIDENCE: Multiple reliable sources, verified data
85	- MEDIUM CONFIDENCE: Good sources but some gaps
86	- LOW CONFIDENCE: Limited data, emerging information
87
88	## Appendix Guidelines
89
90	For detailed information, create a separate appendix file with:
91	- Full methodology
92	- Complete data tables
93	- Source documentation
94	- Technical details
95	- Extended analysis

People who liked this also viewed

6 picks

Type