florianbonnet14/ThePowerOfAnalytics_ClaudeSkills / executive-summary-writer
executive-summary-writer
VerifiedTransform analysis findings into clear, actionable executive summaries using the MAIN framework (Motive, Answer, Impact, Next steps) and Pyramidal Principle. Use when completing any analysis that needs stakeholder buy-in, preparing for leadership meetings, documenting investigation findings, writing business reviews, creating post-mortems, proposing initiatives based on data, or communicating insights to executives.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.6 KB |
| assets/executive-summary-template.md | markdown | 1.2 KB |
| executive-summary-writer-tutorial.md | markdown | 1.5 KB |
| references/examples.md | markdown | 13.2 KB |
| references/main-framework.md | markdown | 9.8 KB |
| references/templates.md | markdown | 8.3 KB |
assets/executive-summary-template.md
View on GitHub# [Topic] - Executive Summary
## Motive
[2-4 sentences explaining the business context, what triggered this analysis, and who is affected]
## Answer
[3-5 sentences covering:
- What you found (key findings in 1-2 sentences)
- What you recommend (specific action)
- Expected outcome if recommendation is followed]
## Impact
[3-5 sentences quantifying:
- Business metrics affected (revenue, users, costs) with specific numbers
- Magnitude and timeline
- Risk if no action taken
- Confidence level]
## Next Steps
1. [Specific action] - Owner: [Name] - ETA: [Date] - Success: [Metric]
2. [Specific action] - Owner: [Name] - ETA: [Date] - Success: [Metric]
3. [Specific action] - Owner: [Name] - ETA: [Date] - Success: [Metric]
4. [Specific action] - Owner: [Name] - ETA: [Date] - Success: [Metric]
---
## Supporting Analysis (Optional)
### Key Finding #1: [Title]
[Brief explanation with supporting data/chart]
### Key Finding #2: [Title]
[Brief explanation with supporting data/chart]
### Key Finding #3: [Title]
[Brief explanation with supporting data/chart]
---
## Appendix (Optional)
### Methodology
[How the analysis was conducted]
### Additional Data
[Supporting tables, charts, detailed segmentation]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |