← Back to Skills Marketplace
35
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install work-productivity-word-mail-workflow-helper
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
- Clarify the template model: classic mail merge fields, content controls, bookmarks, custom document properties, placeholder text, or a custom DOCX assembly pipeline.
- Identify the data source and shape: CSV, Excel, JSON, database rows, one-record-per-document, repeated tables, optional clauses, images, or signatures.
- Preserve the template. Work from a clean master copy and generate outputs into a separate folder.
- 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.
- Protect formatting by replacing field values inside existing runs where possible. Avoid rebuilding paragraphs unless the template is simple.
- Handle edge cases explicitly: missing data, long values, date/number formatting, optional sections, blank rows, page breaks, headers/footers, and tracked changes.
- 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 this if you want help with Word mail merge or DOCX template workflows. Be aware it may be invoked too broadly in some agent setups, so confirm the task is actually about Word/DOCX automation before following generated workflow or code, especially for legal, HR, or other sensitive documents.
Capability Assessment
Purpose & Capability
The stated purpose and runtime instructions consistently focus on building and troubleshooting Microsoft Word mail merge, content controls, merge fields, document properties, and DOCX template assembly workflows.
Instruction Scope
Some README, Chinese skill, and requirement-plan trigger examples are broad or awkward, and agents/openai.yaml allows implicit invocation; this may cause over-selection, but the actual capability remains document-workflow guidance rather than privileged automation.
Install Mechanism
The package contains Markdown and YAML files only, with no executable scripts, package install hooks, binaries, or dependency installation steps.
Credentials
The instructions are proportionate to the purpose: they discuss local document templates, data sources, generated outputs, validation, and formatting preservation without requesting credentials, broad filesystem indexing, or unrelated network access.
Persistence & Privilege
No background workers, persistence mechanisms, privilege escalation, credential/session access, or automatic destructive actions were found; preserving a master template and writing outputs separately is expected for this workflow.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install work-productivity-word-mail-workflow-helper - After installation, invoke the skill by name or use
/work-productivity-word-mail-workflow-helper - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Improved skill description and usage documentation for building and troubleshooting Microsoft Word mail merge and DOCX template workflows.
- Added detailed workflow steps for assembling templated documents using various merge field strategies and data sources.
- Included common fix patterns addressing field resolution, formatting preservation, repeating sections, and data normalization.
- Outlined best practices for output validation and auditability.
- Clarified documentation scope and when to reference additional requirement details.
Metadata
Frequently Asked Questions
What is Work Productivity Word Mail Workflow Helper?
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 35 downloads so far.
How do I install Work Productivity Word Mail Workflow Helper?
Run "/install work-productivity-word-mail-workflow-helper" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Work Productivity Word Mail Workflow Helper free?
Yes, Work Productivity Word Mail Workflow Helper is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Work Productivity Word Mail Workflow Helper support?
Work Productivity Word Mail Workflow Helper is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Work Productivity Word Mail Workflow Helper?
It is built and maintained by Kyro (@kyro-ma); the current version is v1.0.1.
More Skills