officecli-word-form

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

Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Grong/openhub-client --skill officecli-word-form-grong
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: officecli-word-form
Source: https://github.com/Grong/openhub-client/tree/main/crates/backend/openhub-app/assets/builtin-skills/officecli-word-form
Command: npx skills add https://github.com/Grong/openhub-client --skill officecli-word-form-grong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building genuinely fillable Word forms requires OpenXML constructs (SDT content controls, legacy FormFields, MERGEFIELD placeholders, document protection) that plain document generators do not produce, and OfficeCLI's add-time prop limitations silently discard complex attributes like dropdown items and date formats. ## Core Features & Use Cases - Structured form fields: Creates SDT content controls (text, richtext, dropdown, combobox, date), legacy FormField checkboxes, and MERGEFIELD mail-merge placeholders with alias/tag metadata. - Three build paths: Pure CLI for simple fields, raw-set XML injection for dropdown items and date formats, and Word-template workflows for signature pictures and grouped controls. - Protection and locking: Applies documentProtection modes and per-control locks (sdtLocked, contentLocked) for role-gated multi-party forms. - Use Case: Build an employee onboarding intake form with name and start-date fields, a department dropdown with real options, an agreement checkbox, and forms protection so only the fields are editable in Word. ## Quick Start Ask the AI to create a fillable Word intake form with a full-name text field, a start-date picker, a department dropdown, and an agreement checkbox, then lock the document so only those 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 apply document protection with the forms mode. Dropdown items and custom date formats require raw-set XML injection because add-time props silently discard them.

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

Use a legacy FormField with type=checkbox, since SDT checkbox type is not implemented and exits with an error. Set a name of 20 characters or fewer and a checked state, then enable forms protection so it is clickable in Word.

Why are my dropdown items missing after adding a dropdown content control?

OfficeCLI only supports four canonical SDT props at add time; items are silently discarded with an UNSUPPORTED warning. Inject listItem elements afterward using raw-set with an xpath targeting the control's dropDownList node.

Does document protection prevent the CLI from editing the file?

No. Document protection restricts Word users only; all OfficeCLI add, set, and raw-set operations continue to work under any protection mode without a force flag. Apply protection=forms as the final command.

When should I use a Word template instead of building a form purely via CLI?

Use a Word template for picture signature controls, grouped SDTs, placeholder prompt text, or custom richtext styling that exceed CLI prop capabilities. Build the skeleton once in Word's Developer tab, then fill values via CLI set commands.