Writer

LibreOffice Writer

Overview

This public intake copy packages plugins/antigravity-awesome-skills-claude/skills/libreoffice/writer from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.

LibreOffice Writer

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Core Capabilities, Python Libraries, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

• Creating new documents in ODT format
• Converting documents between formats (ODT <-> DOCX, PDF, HTML, RTF, TXT)
• Automating document generation workflows
• Performing batch document operations
• Creating templates and standardized document formats
• Use when the request clearly matches the imported source intent: Document creation, format conversion (ODT/DOCX/PDF), mail merge, and automation with LibreOffice Writer.

Operating Table

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

1. Creating a New Document #### Method 1: Command-Line bash soffice --writer template.odt #### Method 2: Python with UNO python import uno def createdocument(): localctx = uno.getComponentContext() resolver = localctx.ServiceManager.createInstanceWithContext( "com.sun.star.bridge.UnoUrlResolver", localctx ) ctx = resolver.resolve( "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext" ) smgr = ctx.ServiceManager doc = smgr.createInstanceWithContext("com.sun.star.text.TextDocument", ctx) text = doc.Text cursor = text.createTextCursor() text.insertString(cursor, "Hello from LibreOffice Writer!", 0) doc.storeToURL("file:///path/to/document.odt", ()) doc.close(True) #### Method 3: Using odfpy python from odf.opendocument import OpenDocumentText from odf.text import P, H doc = OpenDocumentText() h1 = H(outlinelevel='1', text='Document Title') doc.text.appendChild(h1) doc.save("document.odt") ### Converting Documents bash # ODT to DOCX soffice --headless --convert-to docx document.odt # ODT to PDF soffice --headless --convert-to pdf document.odt # DOCX to ODT soffice --headless --convert-to odt document.docx # Batch convert for file in *.odt; do soffice --headless --convert-to pdf "$file" done ### Template-Based Generation python import subprocess import tempfile from pathlib import Path def generatefromtemplate(templatepath, variables, outputpath): with tempfile.TemporaryDirectory() as tmpdir: subprocess.run(['unzip', '-q', templatepath, '-d', tmpdir]) contentfile = Path(tmpdir) / 'content.xml' content = contentfile.readtext() for key, value in variables.items(): content = content.replace(f'${{{key}}}', str(value)) contentfile.writetext(content) subprocess.run(['zip', '-rq', outputpath, '.'], cwd=tmpdir) return outputpath

2. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
3. Read the overview and provenance files before loading any copied upstream support files.
4. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
5. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
6. Validate the result against the upstream expectations and the evidence you can point to in the copied files.
7. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.

Imported Workflow Notes

Imported: Workflows

Creating a New Document

Method 1: Command-Line

soffice --writer template.odt

Method 2: Python with UNO

import uno

def create_document():
    local_ctx = uno.getComponentContext()
    resolver = local_ctx.ServiceManager.createInstanceWithContext(
        "com.sun.star.bridge.UnoUrlResolver", local_ctx
    )
    ctx = resolver.resolve(
        "uno:socket,host=localhost,port=8100;urp;StarOffice.ComponentContext"
    )
    smgr = ctx.ServiceManager
    doc = smgr.createInstanceWithContext("com.sun.star.text.TextDocument", ctx)
    text = doc.Text
    cursor = text.createTextCursor()
    text.insertString(cursor, "Hello from LibreOffice Writer!", 0)
    doc.storeToURL("file:///path/to/document.odt", ())
    doc.close(True)

Method 3: Using odfpy

from odf.opendocument import OpenDocumentText
from odf.text import P, H

doc = OpenDocumentText()
h1 = H(outlinelevel='1', text='Document Title')
doc.text.appendChild(h1)
doc.save("document.odt")

Converting Documents

# ODT to DOCX
soffice --headless --convert-to docx document.odt

# ODT to PDF
soffice --headless --convert-to pdf document.odt

# DOCX to ODT
soffice --headless --convert-to odt document.docx

# Batch convert
for file in *.odt; do
    soffice --headless --convert-to pdf "$file"
done

Template-Based Generation

import subprocess
import tempfile
from pathlib import Path

def generate_from_template(template_path, variables, output_path):
    with tempfile.TemporaryDirectory() as tmpdir:
        subprocess.run(['unzip', '-q', template_path, '-d', tmpdir])
        content_file = Path(tmpdir) / 'content.xml'
        content = content_file.read_text()
        for key, value in variables.items():
            content = content.replace(f'${{{key}}}', str(value))
        content_file.write_text(content)
        subprocess.run(['zip', '-rq', output_path, '.'], cwd=tmpdir)
    return output_path

Imported: Overview

LibreOffice Writer skill for creating, editing, converting, and automating document workflows using the native ODT (OpenDocument Text) format.

Imported: Core Capabilities

1. Document Creation

• Create new ODT documents from scratch
• Generate documents from templates
• Create mail merge documents
• Build forms with fillable fields

2. Format Conversion

• ODT to other formats: DOCX, PDF, HTML, RTF, TXT, EPUB
• Other formats to ODT: DOCX, DOC, RTF, HTML, TXT
• Batch conversion of multiple documents

3. Document Automation

• Template-based document generation
• Mail merge with data sources (CSV, spreadsheet, database)
• Batch document processing
• Automated report generation

4. Content Manipulation

• Text extraction and insertion
• Style management and application
• Table creation and manipulation
• Header/footer management

5. Integration

• Command-line automation via soffice
• Python scripting with UNO
• Integration with workflow automation tools

Examples

Example 1: Ask for the upstream workflow directly

Use @writer to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @writer against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @writer for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @writer using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Imported Usage Notes

Imported: Command-Line Reference

soffice --headless
soffice --headless --convert-to <format> <file>
soffice --writer    # Writer
soffice --calc      # Calc
soffice --impress   # Impress
soffice --draw      # Draw

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

• Use styles for consistency
• Create templates for recurring documents
• Ensure accessibility (heading hierarchy, alt text)
• Fill document metadata
• Store ODT source files in version control
• Test conversions thoroughly
• Embed fonts for PDF distribution

Imported Operating Notes

Imported: Best Practices

1. Use styles for consistency
2. Create templates for recurring documents
3. Ensure accessibility (heading hierarchy, alt text)
4. Fill document metadata
5. Store ODT source files in version control
6. Test conversions thoroughly
7. Embed fonts for PDF distribution
8. Handle conversion failures gracefully
9. Log automation operations
10. Clean temporary files

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills-claude/skills/libreoffice/writer, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Imported Troubleshooting Notes

Imported: Troubleshooting

Cannot open socket

killall soffice.bin
soffice --headless --accept="socket,host=localhost,port=8100;urp;"

Conversion Quality Issues

soffice --headless --convert-to pdf:writer_pdf_Export document.odt

Related Skills

• @00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
• @10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Imported Reference Notes

Imported: Format Conversion Reference

Supported Input Formats

• ODT (native), DOCX, DOC, RTF, HTML, TXT, EPUB

Supported Output Formats

• ODT, DOCX, PDF, PDF/A, HTML, RTF, TXT, EPUB

Imported: Resources

• LibreOffice Writer Guide
• LibreOffice SDK
• UNO API Reference
• odfpy

Imported: Python Libraries

pip install odfpy     # ODF manipulation
pip install ezodf     # Easier ODF handling

Imported: Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.