officecli-word-form

Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document', 'onboarding form', 'HR intake', 'survey template', 'contract / SOW template', 'mail-merge template', 'compliance checklist', 'medical intake questionnaire'. Output is a single .docx where specific fields are editable and the rest is locked. This skill is INDEPENDENT, not a scene layer on docx — payload is `<w:sdt>` + `<w:ffData>` + `<w:fldChar>` + `documentProtection`, none of which docx base skill covers. Do NOT trigger for regular reports, letters, memos, academic papers, pitch decks, or any document with no user-fillable fields — route those to officecli-docx or its scene layers.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally actionable, workflow-clear skill with strong executable recipes and a rigorous validation gate. Its main weaknesses are length/redundancy in a single monolithic file and a broken template reference, which together keep conciseness and progressive disclosure at the mid level.

Suggestions

De-duplicate the 'INDEPENDENT / reverse handoff' message (currently repeated in the description, the opening paragraph, and the Mental Model section) to a single canonical statement.

Split the Known Issues table and the raw-set recipe details into a reference file (e.g. references/KNOWN_ISSUES.md) and link to it one level deep, moving the body toward a lean overview.

Either ship the referenced 'templates/onboarding_with_signature.docx' in an assets/ folder or remove/replace the dangling reference so Path C is actually runnable.

Dimension	Reasoning	Score
Conciseness	The body is densely specialized (no basic-concept padding about what a .docx or mail-merge is) but runs ~660 lines with real redundancy: the 'reverse handoff / INDEPENDENT, not a scene layer' message is stated three times and the Known Issues table rehashes guidance already given inline. Not a 3 because it could be meaningfully tightened; not a 1 because it does not explain concepts Claude already knows.	2 / 3
Actionability	Provides fully executable, copy-paste-ready bash with concrete props throughout — Quick Start, Path A/B/C recipes, raw-set recipes, batch mode, and the Delivery Gate script. Not a 2 because the code is real and complete, not pseudocode.	3 / 3
Workflow Clarity	Multi-step processes are explicitly sequenced with validation checkpoints: the six Delivery Gates each print an OK/REJECT line with exit-on-failure feedback loops, plus an explicit build order and 'one command at a time' discipline. Not a 2 because validation is explicit and recoverable, not implicit.	3 / 3
Progressive Disclosure	The body is well-sectioned but monolithic — a single ~660-line file with no bundle files, and it references a non-existent 'templates/onboarding_with_signature.docx'. Content that could be split (Known Issues, raw-set recipes, field-pattern table) is inline. Not a 1 because organization is clear with no nested references; not a 3 because nothing is offloaded to one-level-deep real reference files.	2 / 3
	Total	10 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description with explicit what/when guidance and strong distinctiveness from the sibling docx skill. The only weakness is the second-person imperative lead ('Use this skill to create…') instead of third-person voice.

Suggestions

Rewrite the opening in third person (e.g. 'Creates fillable Word forms (.docx) with Content Controls (SDT), legacy FormField checkboxes, MERGEFIELD mail-merge placeholders, and document protection.') to avoid the second-person-voice specificity penalty.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection'), but opens with the second-person imperative 'Use this skill to create…' rather than third person, which the rubric penalizes by reducing specificity by 1. Not a 3 because of the voice penalty; not a 1 because the capabilities named are concrete, not vague.	2 / 3
Completeness	Explicitly answers both what ('create fillable Word forms (.docx) with real Content Controls…') and when ('Trigger on: …' plus 'Do NOT trigger for regular reports, letters, memos… route those to officecli-docx'). Not a 2 because the 'when' is explicit, not merely implied.	3 / 3
Trigger Term Quality	Dense natural-language trigger list ('fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'onboarding form', 'HR intake', 'medical intake questionnaire') plus negative triggers, covering the terms a user would actually say. Not a 2 because coverage is comprehensive, not partial.	3 / 3
Distinctiveness Conflict Risk	States a clear niche ('INDEPENDENT, not a scene layer on docx'), distinguishes its payload from docx, and routes non-form documents away. Unlikely to fire for the wrong skill. Not a 2 because the boundary against the sibling docx skill is explicit and concrete.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (670 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Team-Commonly/commonly
Path: backend/commonly-bundled-skills/officecli/skills/officecli-word-form/SKILL.md
Commit: 69b6005

Reviewed: about 18 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.