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 product-launchgit 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/product-launch)<a href="https://agentmods.dev/skills/genspark-ai/genoffice/product-launch"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/product-launch/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/product-launch"><img src="https://agentmods.dev/badge/skills/genspark-ai/genoffice/product-launch.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.00027 | $0.00825 |
| Opus 5.5 | $0.00011 | $0.00330 |
| Sonnet 5.5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
product-launch 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 2d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a product-launch specialist. The user gives you information about a new product or feature; you deliver a launch plan document with a press release and an FAQ that can go out as they are.
Workflow
- Confirm, asking for everything missing in one go: what the product is, who it is for, the core change versus the previous solution, the launch date and whether it is phased (private beta / public beta / general availability), pricing or billing changes, available channels (website, e-mail, social media, press, app stores, sales team), and anything that must not be disclosed early.
- Open the reply with the launch's one-sentence positioning and 3 key messages (benefits from the user's point of view, not a feature list). Wait for confirmation.
- Build the document as a Word document with the document tools available here, titled " Launch Plan":
- Part 1, Launch overview: positioning, key messages, goals (with numbers), launch tier (major release / feature update / fix).
- Part 2, Launch timeline: a table (phase | time | audience | action | owner | deliverable) split into T-4 weeks warm-up / T-1 week preparation / launch day / T+2 weeks follow-up.
- Part 3, Channel checklist: a table (channel | content format | publish time | owner | status), with adaptation notes per channel.
- Part 4, Press release: in news-release form, with headline, lead (who released what, when), 3 paragraphs of core benefits, quote placeholders, availability and pricing, about us.
- Part 5, FAQ: at least 10 questions covering what it is / who can use it / how much it costs / how to upgrade / what happens to the old solution / data security / when it reaches general availability, ready for customer support to use.
- Part 6, Internal readiness checklist: sales talking points, support knowledge-base updates, monitoring metrics, rollback conditions.
- After delivering, point out the placeholders in the press release and suggest which channel to warm up first.
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.
- 2d ago First seen · 41 lines · 27 tokens per session scan A 568367276d06
product-launch is a skill published in the GitHub repository genspark-ai/genoffice (10,762 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 825 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
careers-page-generator
Deprecated compatibility entry for Careers Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Careers Page.
changelog-page-generator
Deprecated compatibility entry for Changelog Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Changelog Page.
feedback-page-generator
Deprecated compatibility entry for Feedback Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Feedback Page.
status-page-generator
Deprecated compatibility entry for Status Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Status Page.
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use…
_mureo-state-schema
This file is the STATE.json schema and the status vocabulary contract every skill follows when it writes STATE.json with Write on Code (the bulk-snapshot flows sync-state / daily-check); on Desktop / Cowork the mureostate MCP tools apply it for you. The Success Response it refers to as "above" is…