AC work-productivity-word-mail-workflow-helper
Build and troubleshoot Microsoft Word mail merge and DOCX template workflows with merge fields, content controls, document properties, repeated sections, data sources, and formatting preservation. Use when Codex needs to automate templated Word documents for legal, HR, operations, sales, or administrative workflows.
Build and troubleshoot Microsoft Word mail merge and DOCX template workflows with merge fields, content controls, document properties, repeated sections, data…
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
The same skill appears in 1 more place: ClawHub
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (work-productivity-word-mail-workflow-helper) differs from the folder (work-productivity-word-mail-workflow-helper-180322)
- 70When it triggers. States when to use, but not when not to
- 85Steps. 19 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 576 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 317: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 19 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.