Skip to content
Get packs

Guide · Agent skill

How to use the Fillable Word Form Builder agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Fillable Word Form Builder is an agent skill named officecli-word-form. It lets an AI agent build a single .docx file in which specific answer fields are editable and the rest of the page is locked. This guide explains what the skill does, how to install it, how to ask for it in plain language, and what it needs to run. After reading, you should be able to create a working form such as an HR intake, onboarding form, survey or contract template.

Fillable Word Form BuilderiOfficeAI/OfficeCLI · Apache-2.0

Quick start

  1. 1Install the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings, Capabilities, Skills in the Claude apps.
  2. 2Install OfficeCLI. Run the install command for your platform, then run officecli --version to confirm it works. If it fails, download the binary from the GitHub releases page.
  3. 3Ask for the form. Describe the form, its purpose and which fields should be editable, for example an HR intake or onboarding form.
  4. 4Let the agent build the fields. The agent adds content controls, checkboxes and mail-merge placeholders one command at a time, reading the output after each step.
  5. 5Lock the document. Once static layout is final, the agent sets forms protection so only the fields remain editable.
  6. 6Check the result. Review the form view and content control queries to confirm the fields and protection are correct.

What the skill makes the agent do

The skill builds Word forms, not ordinary documents. A form is a .docx that combines four kinds of structured elements: content controls (SDT) for text, dropdown, combo box, date, picture and group fields; legacy FormField checkboxes, which are the only real clickable checkbox in this approach; MERGEFIELD placeholders for mail merge; and document protection, which makes non-field text read-only in Word.

The agent drives the OfficeCLI command-line tool to add these elements one step at a time. Every command changes the file immediately. The skill's documentation states that it is independent of the general Word (docx) skill, because none of the form elements are covered there.

  • Content controls: text, richtext, dropdown, combobox, date, picture, group
  • Checkboxes: legacy FormField, since SDT checkboxes are not implemented
  • Mail-merge placeholders: MERGEFIELD, filled in later by a downstream merge engine
  • Protection: forms protection locks static content and leaves form fields editable

Install the skill and the OfficeCLI tool

To add the skill, download the ZIP from this page and unzip it into ~/.claude/skills/ for your user account, or into a project's .claude/skills/ folder for one project. Alternatively, in the Claude apps, open Settings, then Capabilities, then Skills, and upload the skill there.

The skill also needs the OfficeCLI command-line tool. The skill checks whether officecli is installed and installs it if not. On macOS or Linux it uses the install script from d.officecli.ai. On Windows it uses the PowerShell install script from the same domain. Run the verify command afterward. If the install is blocked or fails, download the binary for your platform from the OfficeCLI GitHub releases page and run the verify command again.

  • Skill folder contains SKILL.md
  • Upload route: Settings, Capabilities, Skills in the Claude apps
  • Folder route: ~/.claude/skills/ or project .claude/skills/
  • Tool check: officecli --version
if ! command -v officecli >/dev/null 2>&1; then curl -fsSL https://d.officecli.ai/install.sh | bash fi officecli --version

Trigger the skill with natural requests

You do not need to name the skill. The agent is directed to use it when a request involves fillable or protected Word documents. Useful trigger phrases include fillable form, form fields, content controls, only editable fields, protect document, onboarding form, HR intake, survey template, contract or SOW template, mail-merge template, compliance checklist and medical intake questionnaire.

Be specific about which parts should be editable. The skill's output is a single .docx where the fields you name are editable and the rest is locked.

  • Create a fillable onboarding form in Word where only the name, start date and manager fields are editable.
  • Make a contract SOW template with mail-merge fields for client name and fee, and lock the rest of the document.
  • Build a compliance checklist in Word with checkboxes that staff can tick, and protect the document.
  • Turn this survey into a Word template with dropdown answers and only the answer fields editable.

What the skill will not do

The skill is meant for documents whose purpose is data capture or template merge. If your request is for a regular report, letter, memo, academic paper, pitch deck or any document with no fields to fill, the skill tells the agent to route the work to officecli-docx or one of its scene skills instead.

Ask for a form only when the document has places where a person or a merge will enter data.

Build the form and check it

The skill works in small, ordered steps. Finish all static layout first, because after forms protection is set, edits to non-field content are refused unless you pass --force. Field edits still succeed after protection.

Use the help system for uncertain properties. The skill says help output is pinned to the installed CLI version and wins if it disagrees with the skill text. Check the form by viewing its fields and querying content controls, and confirm that protection is enforced.

  • Read help before guessing a property: officecli help docx sdt
  • Wrap any path with brackets in quotes so the shell does not expand it
  • Quote any property value that contains a dollar sign in single quotes
  • Use the form view and query commands to confirm fillable fields and protection
officecli help docx sdt officecli add "$FILE" /body --type sdt --prop alias=Party_A_Name --prop tag=party_a --after 'find:甲方签字（Service Provider）' officecli get "$FILE" '/body/sdt[1]' officecli view "$FILE" forms

Safety notes: scripts and network

This skill runs shell commands and uses the network. The install step downloads and runs a script from d.officecli.ai, and the workflow runs officecli commands on your .docx file. Only use the skill if you are comfortable with an agent running shell commands on your machine.

If your environment blocks scripted installs, use the manual download route from GitHub releases instead. Users who cannot install a command-line tool or run shell commands cannot use this skill, because the workflow depends on OfficeCLI.

  • Runs scripts: yes
  • Uses network: yes
  • Needs shell access and the OfficeCLI tool
  • Optional: jq is used in some steps to read JSON output

What people use it for

  • HR intake or employee onboarding forms where staff fill in their own details
  • Contract or statement of work templates with mail-merge fields for client and fee details
  • Compliance checklists with tick-box items and protected wording
  • Medical intake questionnaires and survey templates where only answer fields are editable

Frequently asked questions

Is the Fillable Word Form Builder skill free?

The skill's source is released under the Apache-2.0 licence, as stated on this page. Check the licence file in the source repository for the full terms before you use or redistribute it.

What do I need to use this skill?

You need an agent that can run shell commands and the OfficeCLI command-line tool. The skill installs OfficeCLI if it is missing, and the workflow needs network access for that step.

Can I use this skill to make a normal Word report or letter?

No. The skill says to route reports, letters, memos, papers and documents with no fields to officecli-docx or its scene skills instead.

Why does my Word checkbox not work?

The skill uses legacy FormField checkboxes because they are the only real clickable checkbox in this approach. SDT checkboxes are not implemented, so the agent should use FormField elements for checkboxes.

What should I do if the install command fails?

If the install is blocked by security policy, has no network access or lacks permissions, download the binary for your platform from the OfficeCLI GitHub releases page, then run officecli --version again.

Why was my edit refused after I protected the form?

Forms protection blocks edits to non-field content and returns an error asking for --force. Form field edits still work. Finish static layout first, or temporarily clear protection, edit, and re-lock.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you need a Word form where only chosen answer fields are editable, and you are comfortable running a command-line tool through an agent. Pick a different option if you only need ordinary Word documents, or if you cannot install a command-line tool or run shell commands.

Download the skill