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.

72

Quality

90%

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

77%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.

This is a highly actionable, rigorously validated skill body — every command is executable, the decision paths are unambiguous, and the Delivery Gate plus known-issues table provide genuine feedback loops. Its weakness is shape, not substance: all 669 lines live in SKILL.md with zero bundle files, and a referenced template file is missing, so progressive disclosure and token efficiency both suffer despite excellent per-line density.

Suggestions

Split the long-tail material into one-level-deep reference files — e.g. references/recipes.md (Quick Start, SOW sub-recipes, block-level lock), references/known-issues.md (the K-table), and scripts/delivery_gate.sh (the 6-gate script) — keeping SKILL.md to the mental model, three-path decision table, and pointers.

Provide the referenced assets/templates/onboarding_with_signature.docx (or remove/condition the Path C `cp templates/...` commands) so the Path C workflow is actually executable from the bundle as written.

De-duplicate content that appears twice — the Path C workflow is repeated near-verbatim in 'Three Paths' and 'Path C — Word template workflow', and the B1 dropdown example recurs inside recipe sow-b — to reduce the token cost of the body.

DimensionReasoningScore

Conciseness

The prose itself is dense and assumes competence — no explanations of concepts Claude already knows, and nearly every sentence carries an operational fact ('`--prop lock=...` on `add` is UNSUPPORTED (silently discarded). Apply lock via a separate `set`.'). But at 669 lines / ~44KB loaded on every invocation, the token budget is strained: three full recipes, a 13-row Known Issues table, and the 6-gate Delivery Gate script are exactly the material that should be trimmed from the overview body. Not 4: the issue is scale, not a few trimmable sentences; not 2: nothing is padded or redundant in intent, and explanations are uniformly high-value.

3 / 5

Actionability

Fully executable copy-paste commands throughout — every recipe is complete shell with expected readbacks ('expect: type=dropdown items=Engineering,Finance,HR'), and the decision table maps each need to a concrete path ('dropdown / combobox with options → B, raw-set append `<w:listItem>`'). Not 4: even failure modes come with exact commands (K17's per-header `raw-set … --xpath "//w:noProof" --action remove`), leaving no gaps between instruction and execution.

5 / 5

Workflow Clarity

Clear sequence with explicit validation and feedback loops: a stated build order ('create+open → metadata → structure → skeletons → Path B injections → per-field lock → protection=forms LAST → close'), a stop-and-fix rule for batch/UNSUPPORTED operations ('Any UNSUPPORTED in your build log… stop, rewrite… Do not ship on top'), and an executable six-gate Delivery Gate with error recovery (Gate 1's K8 waiver branch). Not 4: validation checkpoints are executable scripts with REJECT paths, satisfying the feedback-loop requirement for batch/XML manipulation exactly as the 5 anchor describes.

5 / 5

Progressive Disclosure

Internal structure is good — clear section headers, decision tables, and §-cross-references make the file navigable — but there are no bundle files at all (no references/, scripts/, or assets/), so everything is inline, and the referenced 'templates/onboarding_with_signature.docx' does not exist in the bundle. Not 4: content that clearly belongs in separate files (three full recipes, the Known Issues table, the gate script) is inlined in a 669-line SKILL.md rather than split one level deep; not 2: the file is well-sectioned with a quick start and clear navigation, unlike a header-less wall of reference material.

3 / 5

Total

16

/

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 exemplary: it names the concrete payload types, gives a rich list of natural trigger phrases including use-case synonyms, states the output contract (fields editable, rest locked), and preempts mis-routing with explicit negative triggers and a routing target. Both 'what' and 'when' are answered at the concrete level the 5 anchors require, and it stays dense without padding.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection' — comprehensively covering the skill's capability surface with named OpenXML payloads. Not 4: coverage is complete for the domain, not 'minor gaps'; not below: no vague or generic language anywhere.

5 / 5

Completeness

Explicitly answers both what ('create fillable Word forms… with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD… + document protection', 'Output is a single .docx where specific fields are editable and the rest is locked') and when (an explicit 'Trigger on:' list plus a negative 'Do NOT trigger for…' list). Not 4: the when clause is maximally explicit with concrete trigger phrases, not merely present.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and the file extension: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document', plus use-case phrases like 'onboarding form', 'HR intake', 'medical intake questionnaire', and '(.docx)'. Not 4: essentially no common variation is missing, and users would naturally say nearly every listed phrase.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers and explicit boundary management: 'This skill is INDEPENDENT, not a scene layer on docx' and 'Do NOT trigger for regular reports, letters, memos, academic papers, pitch decks… route those to officecli-docx or its scene layers'. Not 4: conflict risk is actively mitigated by negative triggers and routing guidance, not just low by accident.

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.

Validation — 15 / 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.