
Executive Deck
Build a reporting or executive presentation where every slide title states a conclusion...
Install
npx skills add genspark-ai/genoffice --skill executive-deck -g -a claude-code -y- Repository
- genspark-ai/genoffice11.5k
- Category
- Documents
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Lightabout 869 tokens
- Runs scripts
- No, instructions only
What it does
Build a reporting or executive presentation where every slide title states a conclusion and the deck follows a pyramid, answer-first structure. Use when the user asks for a management update, board deck, status report, business review or a presentation that argues for a decision, including turning a document into slides.
Executive deck
A reporting deck is read, not performed. The reader should get the whole argument from the slide titles alone; the body of each slide is the proof.
Before building
- Decide the single answer the deck gives. Write it as one sentence. That sentence is the title of slide 2 and the backbone of the whole deck.
- Read every attached or referenced file fully. Figures, names and dates come only from there. If the source lacks a number the story needs, say so on the slide rather than estimating.
- Fix the length from the request: default 8-12 slides for a business review, 5-7 for a status update. Fewer slides with a clear line beat more slides with everything.
Structure (pyramid, answer first)
- Title slide, Deck title that names the decision or question, date, presenter or team.
- Answer slide, The one-sentence conclusion as the title; three supporting points as the body, each one line. Nothing else.
- One slide per supporting point, Title = the point as a full sentence with a verb ("Churn rose because onboarding slipped in Q2", not "Churn"). Body = the evidence: one chart or one table or 3-5 bullets, never all three. Order the slides in the same order as the three points on the answer slide.
- Recommendation / next steps, Numbered actions, each with an owner and a date where the source allows. Title states what is being asked ("Approve the Q4 onboarding rebuild").
- Risks or open questions, Only if real. Short.
- Appendix, Detail tables, methodology, backup charts. Nothing in the appendix may be needed to follow the main story.


