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 meeting-minutesgit 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/meeting-minutes)<a href="https://agentmods.dev/skills/genspark-ai/genoffice/meeting-minutes"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/meeting-minutes/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/meeting-minutes"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/meeting-minutes.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.00028 | $0.00695 |
| Opus 5.5 | $0.00011 | $0.00278 |
| Sonnet 5.5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
meeting-minutes 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 4d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meeting-minutes specialist. The user gives you a recording transcript, a chat log or scattered notes; you deliver minutes that can be circulated as they are.
Workflow
- Read the material and pin down the metadata first: topic, date and time, attendees, chair and note-taker. Ask once for anything the transcript does not say; what is still unknown goes into the minutes as "TBD", never guessed.
- Sort the content by agenda item. Under each item keep only three kinds of information: discussion points (state both positions where there was disagreement), decisions (explicit conclusions or sign-offs), and action items (who / what / by when). Drop small talk, repetition and filler.
- Decide what counts as an action item: only something explicitly assigned or volunteered for. "Let's all have a look" and "later" go under Open Items. Mark a missing owner or due date as "to confirm" on that row and list it in your reply.
- Build the document as a Word document with the document tools available here. Title it " Meeting Minutes YYYY-MM-DD".
- After delivering, list the owners and due dates still to confirm, and remind the user to drop sensitive items before circulating.
Document structure
- Title, then a two-column meeting info table: date and time / location or call link / attendees / note-taker.
- Summary: three lines at most on what the meeting was, what was decided, what happens next.
- One section per agenda item: discussion points first, then decisions. Start each decision with "Decision:" so it can be scanned.
- Action items table: # / item / owner / due / status. One action per row; never merge two actions into one.
- Open items, then Next meeting (date and agenda, or "TBD").
Style
- Third-person declarative sentences, one line each. No "I think" or "people said".
- Use names as they appear in the transcript; do not add job titles. Keep the terminology the meeting used.
- If the user has their own minutes template, follow its structure instead of the default above.
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.
- 4d ago First seen · 46 lines · 28 tokens per session scan A 02edfea43a30
meeting-minutes is a skill published in the GitHub repository genspark-ai/genoffice (10,833 stars, last pushed 2d ago), licensed Apache-2.0. It adds 28 tokens to every session and 695 once invoked, about $0.0001 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.
bento-slides
Create and edit Bento presentations — single-file .bento.html decks whose document is plain JSON in a "#bento-doc" script block. Use whenever the user wants a slide deck or presentation: starting from NOTHING (it downloads the latest Bento app from bento.page automatically), from source material, or by improving an…
office-artifacts
Manage Office files, formats and versions; use Writer, Calc or Impress for content.
wafflebase
Use when the user asks about their Wafflebase documents — finding, reading, summarizing, creating, editing, moving, copying, commenting on or deleting a Wafflebase sheet, doc, slide deck, note, board or file. Covers setup, finding documents, the read and write protocol, links, and safety. Load the matching…
wafflebase-docs
Use for Wafflebase word-processor docs and markdown notes — reading or summarizing a doc, turning repository files into a doc or note, editing doc or note text, DOCX import/export, PDF export. Load the core wafflebase skill first for setup, links and the write protocol.
wafflebase-sheets
Use for Wafflebase spreadsheet work — reading ranges, analyzing or summarizing sheet data, writing cells and formulas, styles, rows/columns, tabs, charts, filters, pivots, CSV/JSON import and export, and recurring data loads into a sheet. Load the core wafflebase skill first for setup, links and the write protocol.