← Back to Skills Marketplace
kyro-ma

Word Mail Merge Template Workflow

by Kyro · GitHub ↗ · v0.1.0 · MIT-0
cross-platform ✓ Security Clean
49
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install work-productivity-word-mail-workflow-helper-180322
Description
Build and troubleshoot Microsoft Word mail merge and DOCX template workflows with merge fields, content controls, document properties, repeated sections, dat...
README (SKILL.md)

Word Mail Merge Template Workflow

Use this skill for repeatable Word document assembly: letters, contracts, HR forms, invoices, reports, and other templates that combine structured data with DOCX formatting.

Workflow

  1. Clarify the template model: classic mail merge fields, content controls, bookmarks, custom document properties, placeholder text, or a custom DOCX assembly pipeline.
  2. Identify the data source and shape: CSV, Excel, JSON, database rows, one-record-per-document, repeated tables, optional clauses, images, or signatures.
  3. Preserve the template. Work from a clean master copy and generate outputs into a separate folder.
  4. Choose the safest fill strategy:
    • Use Word mail merge when the user needs Word-native merge behavior.
    • Use content controls for structured templates that should remain editable.
    • Use direct OOXML or a templating library for repeated sections, conditionals, and package-level control.
  5. Protect formatting by replacing field values inside existing runs where possible. Avoid rebuilding paragraphs unless the template is simple.
  6. Handle edge cases explicitly: missing data, long values, date/number formatting, optional sections, blank rows, page breaks, headers/footers, and tracked changes.
  7. Validate generated documents by checking field completion, formatting, page count, section breaks, table rows, filenames, and any required PDF export.

Common Fix Patterns

  • Fields left unresolved: distinguish display text from field-code instructions and update fields in Word when needed.
  • Formatting changes after merge: replace within runs or content controls rather than replacing whole paragraphs.
  • Repeated rows or clauses: model repeats as tables or block-level OOXML, not simple string replacement.
  • Data formatting: normalize dates, currency, line breaks, and locale-specific values before merge.
  • Auditability: keep a manifest of source record IDs and output filenames for batch runs.

Outputs

Provide:

  • A clear template/data mapping.
  • A safe generation workflow or implementation.
  • A validation checklist for batch output quality.
  • Notes about which steps require Word desktop field updates or PDF export.

Read references/requirement-plan.md only when the demand-agent evidence is needed.

Usage Guidance
Install only if you want a helper for Word mail merge or DOCX template workflows. Be aware it may be invoked a little too broadly because of its generic keyword and rough trigger examples; review generated document workflows carefully when using real HR, legal, sales, or administrative data.
Capability Assessment
Purpose & Capability
The artifacts consistently describe help for Microsoft Word mail merge, DOCX templates, merge fields, content controls, document properties, formatting preservation, and validation checklists.
Instruction Scope
The core English skill instructions are purpose-aligned, but the README and Chinese skill include a generic keyword and malformed trigger examples; this is a routing-quality issue rather than evidence of hidden or unsafe behavior.
Install Mechanism
The package contains Markdown and YAML files only, with no executable installer, scripts, dependencies, or package code.
Credentials
The skill is proportionate to its stated purpose: it gives workflow guidance and may help with user-provided DOCX/data only when the user asks, with no credential, network, or broad local indexing requirement.
Persistence & Privilege
No persistence, background workers, privilege escalation, credential handling, or automatic file mutation is present in the artifacts.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install work-productivity-word-mail-workflow-helper-180322
  3. After installation, invoke the skill by name or use /work-productivity-word-mail-workflow-helper-180322
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release of work-productivity-word-mail-workflow-helper. - Provides guidance for building and troubleshooting Microsoft Word mail merge and DOCX template workflows. - Outlines steps for assembling documents from templates with various data sources and merge strategies. - Lists best practices for formatting preservation, repeated sections, and edge case handling. - Offers fix patterns for common mail merge/template automation issues. - Includes outputs: template/data mapping, safe generation workflow, validation checklist, and notes on field updates.
Metadata
Slug work-productivity-word-mail-workflow-helper-180322
Version 0.1.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Word Mail Merge Template Workflow?

Build and troubleshoot Microsoft Word mail merge and DOCX template workflows with merge fields, content controls, document properties, repeated sections, dat... It is an AI Agent Skill for Claude Code / OpenClaw, with 49 downloads so far.

How do I install Word Mail Merge Template Workflow?

Run "/install work-productivity-word-mail-workflow-helper-180322" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Word Mail Merge Template Workflow free?

Yes, Word Mail Merge Template Workflow is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Word Mail Merge Template Workflow support?

Word Mail Merge Template Workflow is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Word Mail Merge Template Workflow?

It is built and maintained by Kyro (@kyro-ma); the current version is v0.1.0.

💬 Comments