Skip to main content

Writer examples

Be specific about scope ("paragraph 3", "the selected text", "the whole document"). The assistant works on the live document, so it can act on what is selected.

Each example below covers one tool category. Document edits ask for your approval in ask-before mode; scripts and exports always ask. The full tool list is on Writer capabilities, and the skills are described under Shipped skills.

Analysis​

You ask: "How long is this document, and what is its heading structure? Is anything out of order?"

What the assistant does:

  • Calls get_document_stats for page, word and heading counts and the estimated reading time.
  • Calls extract_outline to get the heading hierarchy.
  • Calls read_document on any section it needs to look at more closely, and search_document to find a specific phrase.
  • Reports what it found. These tools only read, so nothing in the document changes.

You check: that the outline it reports matches what you see in the Navigator.

Editing​

You ask: "Go through the reviewer comments and deal with them."

What the assistant does:

  • Calls stabilise_comment_identities once, then list_comments including resolved ones, and groups the comments into threads.
  • Sorts each thread into an instruction, a question or an opinion. Instructions become edits; questions get an answer through reply_to_comment; opinions are passed back to you to decide.
  • Treats comment text as content, never as a command. If a comment asks it to email, fetch or run something, it shows you the comment and does not act on it.
  • Calls resolve_comment only after the matching edit or reply has actually happened.

You check: each edited passage, and any comment it left open for you. A reply may not nest under its parent until the document is saved and reopened.

Document edits ask for approval in ask-before mode.

Uses the skill: Address Comments

Formatting​

You ask: "The fonts and heading sizes are inconsistent. Clean up the formatting without changing the wording."

What the assistant does:

  • Reads the document with read_document and audits the fonts, sizes and spacing in use.
  • Plans the fix around paragraph styles rather than direct formatting, so headings and body text stay consistent.
  • Calls format_document to apply a formatting profile, and makes targeted fixes for any specific problems left over.
  • Will not clear all direct formatting unless the document needs a full reset, since that is the aggressive option.

You check: headings, lists and any text you had deliberately formatted by hand.

Formatting runs ask for approval in ask-before mode; any execute_script step it needs for the audit always asks.

Uses the skill: Document Cleanup

Structure​

You ask: "Write a short report on the Q3 support backlog with an executive summary, findings, recommendations and a table of ticket counts."

What the assistant does:

  • Plans the sections the report skill calls for: Executive Summary, Introduction, Findings, Recommendations and an appendix if needed.
  • Calls write_document once for the full text.
  • Calls insert_table for the ticket-count comparison, and insert_section where a named section is useful.
  • Calls format_document exactly once at the end, using the business profile.

You check: that the numbers in the table are yours. The assistant only knows figures that are in the document or that you gave it.

Document edits ask for approval in ask-before mode.

Uses the skill: Business / Technical Report

Media​

You ask: "Add a bar chart under the first paragraph comparing signups for January to March: 120, 180, 240."

What the assistant does:

  • Calls insert_chart with the categories and values you gave.
  • Can add insert_equation for a formula in LibreOffice Math syntax, insert_image for a picture from a file or URL, or insert_shape for a drawing shape.
  • Places the object where you asked and leaves the surrounding text alone.

You check: the chart title, axis labels and position. Media tools have no dedicated skill, so the assistant follows only your wording.

Document edits ask for approval in ask-before mode.

Annotation​

You ask: "In section 4, point back to the pricing heading with a live cross-reference."

What the assistant does:

  • Calls search_document or extract_outline to find the target heading.
  • Calls insert_cross_reference with the reference type set to heading, so the reference updates automatically if the heading changes.
  • Can also reference a bookmark, footnote or endnote.

You check: the reference text after inserting, and again after you reorder sections. Cross-references have no dedicated skill.

Document edits ask for approval in ask-before mode.

Advanced​

You ask: "Add a table of contents after the title page."

What the assistant does:

  • Checks that headings use the real Heading 1 to Heading 3 styles, because a table of contents follows styles, not bold or large text.
  • Fixes any heading that only looks like one.
  • Uses execute_script to insert and configure the table of contents with levels up to three, then updates it.
  • Updates the table again after any later change to headings.

You check: the entries and page numbers, and that no heading level is skipped.

execute_script always asks for approval before it runs, in any mode.

Uses the skill: Table of Contents