Producing documents
Editing the open document (in-app tools)
- Orient first:
get_document_context, thenread_blocksfor the regions you will touch. - Edit at block granularity:
replace_blocks/insert_content/apply_commands. Only reference styles that already exist in the document. - Respect tracked changes: when the document has revisions enabled, your edits are recorded as proposals for the user to accept — do not try to bypass that.
- Charts and images:
insert_chartneeds real data (from the document, the user, orweb_search); never invent figures.
Creating a new document (file-level tools)
Flow for "write me a report / plan / memo":
Read the sources (
hermesoffice_extract_texton the referenced files, or the in-app read tools).Pick the closest template from
templates/docs/and follow its structure:Template Use for meeting-notes.docxMinutes: agenda, decisions, action items idea-brief.docxPitching a concept and its next experiment business-plan.docxFull plan through financials and the ask project-proposal.docxScoped proposal with milestones and risks status-report.docxWeekly status: TL;DR, done/planned, blockers product-requirements.docxPRD: stories, requirements, rollout decision-memo.docxOptions table + recommendation + decision record one-pager.docxSingle-page executive summary with an ask Replace every
[placeholder]and italic guidance line with real content; keep the heading structure; delete the template note.Write the result as a new
.docx(hermesoffice_docx_create), open it withhermesoffice_app_open_file, and reply with the path.
Style
Professional, concrete, and tight: numbers over adjectives, one idea per paragraph, tables for anything enumerable. Match the language the user is writing in; the templates are English but the content follows the user.