GenOffice is an open-source office suite for editing Word, Excel, PowerPoint, PDF, and Markdown files with AI-assisted document editing. People use it as an alternative to Microsoft Office on macOS, Windows, and Linux.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add genspark-ai/genoffice --skill executive-deckgit clone --depth 1 https://github.com/genspark-ai/genofficeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/genspark-ai/genoffice/executive-deck)<a href="https://agentmods.dev/skills/genspark-ai/genoffice/executive-deck"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/executive-deck/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/genspark-ai/genoffice/executive-deck"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/executive-deck.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.00897 |
| Opus 5.5 | $0.00025 | $0.00359 |
| Sonnet 5.5 | $0.00013 | $0.00179 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
executive-deck scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
Slide rules
- Every title is a complete sentence stating a conclusion. If a title could sit on any deck ("Overview", "Results"), rewrite it.
- One message per slide. If a slide needs an "and", split it.
- Bullets: at most 5, each at most 12 words, parallel grammar, no sub-bullets. A bullet that needs a second line is a sentence for the notes, not a bullet.
- Numbers on slides carry unit and period. The source goes in a small footer line on that slide, not in a bullet.
- Charts: one series highlighted, the rest muted; title the chart with its takeaway, not its subject. Prefer bar for comparison, line for trend; no pie with more than 4 slices.
- Speaker notes hold the narration and the caveats, in full sentences. Write them for every content slide.
- Keep the deck's language consistent with the request and sources.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 85 lines · 63 tokens per session scan A 49dc0dfe9b1e
executive-deck is a skill published in the GitHub repository genspark-ai/genoffice (11,115 stars, last pushed today), licensed Apache-2.0. It adds 63 tokens to every session and 897 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-23.
Other skills, from other repositories
office-router
Route Office requests into the correct xlsx, docx, or pptx workflow, while preferring Slidev for new presentation drafts unless .pptx is explicitly required.
access-matrix
Access matrix of role-by-module permissions, with per-role scope, confidentiality level and SME tier, as CSV, SQL, JSON Schema or Notion on request. Use for access reviews.
admin-access-register
Admin account register: system, main and backup admin, seats, plan, 2FA, shared logins and access-review dates, as CSV, SQL, JSON Schema or Notion on request. Use for access reviews.
accounting-audit-system-builder
Routes an accounting or audit request to the right module skill, from software selection through monthly closing, asking only what is missing. Use for books of accounts or audit files.
alumni-re-hire-tracker
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.
document-processing
Use when the deliverable is a document's bytes or its literal content — text/tables out of PDFs, AcroForm fill and flatten, page merge/split, PDF/DOCX from templates, OCR of image-only scans. NOT schema-typed fields pulled from text (that is structured-extraction), NOT signature routing (e-signature) or spreadsheet…