officecli-word-form

Creates fillable Word forms with content controls, checkboxes, mail-merge fields, and document protection.

284|54|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/nomifun/nomifun-desktop --skill officecli-word-form-nomifun
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: officecli-word-form
Source: https://github.com/nomifun/nomifun-desktop/tree/main/crates/backend/nomifun-app/assets/builtin-skills/officecli-word-form
Command: npx skills add https://github.com/nomifun/nomifun-desktop --skill officecli-word-form-nomifun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building genuinely fillable Word forms requires OpenXML constructs—SDT content controls, legacy FormField checkboxes, MERGEFIELD placeholders, and document protection—that plain document generators do not produce, leaving users stuck with underscore-line pseudo-forms that capture no structured data. ## Core Features & Use Cases - Structured Fillable Fields: Adds SDT content controls (text, richtext, dropdown, combobox, date) and legacy FormField checkboxes via the OfficeCLI command line, with alias/tag metadata and lock settings. - Mail-Merge Templates: Inserts MERGEFIELD, REF, SEQ, and IF conditional fields for data-driven contract and letter templates. - Document Protection & Locking: Enforces protection=forms so only designated fields are editable, with per-field lock modes for multi-role forms like patient/physician intake. - Use Case: An HR team needs an onboarding intake form where new hires fill name, start date, and department dropdown while the rest of the document stays locked; this skill generates that .docx with real content controls and enforced protection. ## Quick Start Ask the AI to create a fillable employee onboarding form in Word with text fields for name, a date picker for start date, a department dropdown, an agreement checkbox, and document protection so only the fields are editable.

Frequently Asked Questions about officecli-word-form

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a fillable Word form with content controls from the command line?▼

Use OfficeCLI to add SDT elements with type, alias, and tag props, then set protection=forms on the document. Dropdown items and custom date formats require raw-set OpenXML injection since add-time props for those are unsupported.

How do I add a real checkbox to a Word document programmatically?▼

Use a legacy FormField with type=checkbox via officecli add --type formfield. SDT checkboxes are not implemented in OfficeCLI v1.0.63, so FormField is the only way to get a clickable checkbox.

What is the difference between SDT content controls and MERGEFIELD in Word forms?▼

SDT controls are user-fillable fields listed by view forms, while MERGEFIELDs are template-time placeholders filled by a downstream mail-merge engine and listed only by query field. Both can coexist in one document.

Why does my Word form dropdown have no items after creation?▼

The items prop is unsupported at add time and silently discarded with an UNSUPPORTED warning. Inject w:listItem elements into the dropDownList node using officecli raw-set with an XPath targeting the field's tag.

Can I lock parts of a Word form so only certain roles can edit them?▼

Yes, apply lock=contentLocked via a separate set command on the SDTs one role must not touch. Under protection=forms those fields render read-only in Word, supporting patient/physician or two-party contract workflows.

When should I not use this Word form skill?▼

Do not use it for documents without fillable fields such as reports, letters, memos, theses, or pitch decks. Those should be routed to a general docx generation skill instead.