CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

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

The body is a strong, executable reference: concrete commands, a clear three-path decision model, and a rigorous validation gate with feedback loops. Its main weakness is conciseness — the length and some recipe/K-table redundancy leave room to tighten, and the single-file structure could benefit from offloading the long Known Issues and recipe sections into references.

Suggestions

Tighten conciseness by de-duplicating the Path B raw-set recipes against the K-table Known Issues — the K2/K4/K6 rows restate what the B1/B2/B3 recipes already demonstrate; keep one canonical treatment and cross-reference.

Consider moving the multi-part SOW recipe and/or the full Known Issues table into a references/ file (e.g. FORMS-RECIPES.md, KNOWN-ISSUES.md) to shrink the SKILL.md body toward an overview and raise progressive_disclosure to 5.

Reduce repetition of the 'v1.0.63' version pin across prose; state the pinned version once near the top and reference 'the pinned version' elsewhere so the body ages more gracefully.

DimensionReasoningScore

Conciseness

Dense and almost entirely non-padding — no 'what is OpenXML' exposition — but the ~660-line body carries some redundancy (Path B recipes overlap the Known Issues K-table, and v1.0.63 is repeated pervasively). Mostly efficient with minor trim opportunities, fitting the 'efficient; minor instances that could be tightened' anchor rather than the fully-lean 5.

4 / 5

Actionability

Fully executable, copy-paste-ready bash commands with concrete props throughout; a runnable Quick Start, decision tables mapping needs to paths, and coverage of the common cases (intake form, SOW/contract, checkbox, dropdown items, date format, mail-merge) match the fully-executable/specific-examples anchor.

5 / 5

Workflow Clarity

Provides an explicit build-order sequence, a three-path decision made before any command, and a 6-gate Delivery Gate with executable checks plus REJECT/exit-on-failure feedback loops for the destructive/batch operations (raw-set, protection), matching the explicit-validation-and-feedback-loops anchor.

5 / 5

Progressive Disclosure

Single-file skill with no bundle directories present and genuinely well-organized section headers plus a decision table, warranting a high score; held at 4 rather than 5 because a 660-line monolith (Known Issues + multi-part recipes) could offload detail into one-level-deep references, and at 4 rather than 3 because structure and navigation are solid.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

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

The description is exceptionally well-formed: it states the capability concretely, supplies a rich set of natural trigger phrases, gives both positive and negative trigger guidance, and explicitly disambiguates from the sibling docx skill. No meaningful gaps relative to the rubric anchors.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create fillable Word forms', 'Content Controls (SDT)', 'legacy FormField checkboxes', 'MERGEFIELD mail-merge placeholders', 'document protection' — with comprehensive coverage of the form-building capability surface.

5 / 5

Completeness

Explicitly answers both 'what' (create fillable Word forms with SDT/FormField/MERGEFIELD/protection) and 'when' (a 'Trigger on:' list plus a 'Do NOT trigger for... route those to officecli-docx' exclusion), satisfying the concrete-trigger-phrases anchor.

5 / 5

Trigger Term Quality

An explicit 'Trigger on:' clause enumerates ~15 natural user phrases including synonyms and domain variants ('fillable form', 'fill in', 'onboarding form', 'HR intake', 'medical intake questionnaire', 'compliance checklist'), matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche ('fillable forms only') and actively reduces conflict via the 'INDEPENDENT, not a scene layer on docx' statement and the negative-trigger routing to officecli-docx, fitting the clear-niche/minimal-conflict anchor.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.