CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docx-placeholder-workflow

Fill bounded DOCX templates while preserving content placement

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/collective-learning/published/executable-learning-20261114/recipient/package/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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, fully executable single-command skill with excellent failure-mode documentation via the exit-code table and clear scope boundaries. Its main weaknesses are a repetitively over-explained conditional-governance paragraph and an entrypoint script reference (`helpers/fill_docx.py`) that is not included in the bundle.

Suggestions

Collapse the conditional-governance explanation to a single statement, e.g. 'The IF_<X> marker is governed exclusively by <X>_PACKAGE (required when the conditional appears); a bare <X> key is unused and never affects keep/drop.'

Include the referenced `helpers/fill_docx.py` in the skill bundle (or state where the pinned runtime provides it) so the CLI usage and frontmatter entrypoint resolve to a real file.

Add a short example of the input JSON data object (2-3 fields) so the expected data shape is executable without inference.

DimensionReasoningScore

Conciseness

The body is mostly efficient (CLI block, exit-code table, tight scope lists), but the conditional-governance paragraph restates the same rule roughly three times — "never acts as an alias or fallback", "never affects keep/drop", and "so an unused bare RELOCATION key cannot stand in for a missing RELOCATION_PACKAGE" — which could be tightened to one sentence. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

The guidance is fully executable: a copy-paste-ready CLI invocation with all three required arguments, a concrete worked example with real paths, a complete exit-code table mapping every failure mode, and explicit dependencies. This matches the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor.

5 / 5

Workflow Clarity

This is a simple single-action skill (run one CLI command) and the action is unambiguous; the exit-code table provides explicit validation semantics and error-recovery guidance for every failure mode (invalid JSON, mismatched conditionals, missing fields, unresolved markers). The destructive-operation cap does not apply since inputs are never modified and a new output file is written.

5 / 5

Progressive Disclosure

Sections are well-organized and appropriately placed for a self-contained single-purpose skill (when-to-use, scope, guarantees, CLI, example, dependencies) with no nested references. It falls short of 5 because the entrypoint referenced in frontmatter and CLI usage, `helpers/fill_docx.py`, is not present in the bundle (no references/, scripts/, or assets/ directories exist), leaving a dangling reference — a minor organization gap matching 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

53%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 states a concrete, well-bounded capability but omits any 'when to use' guidance and lacks the natural synonyms (Word, .docx, placeholders, offer letter) that would let a user's phrasing reliably trigger it. It is specific and distinct but incomplete as a trigger description.

Suggestions

Append an explicit trigger clause, e.g. 'Use when filling Word/DOCX templates with {{PLACEHOLDER}} fields from a JSON data object, such as offer letters or form letters.'

Add natural synonyms users would actually say — 'Word document', '.docx', 'placeholders', 'offer letter', 'mail merge' — to broaden trigger term coverage.

Mention the concrete mechanism (replacing {{FIELD_NAME}} placeholders and resolving conditional blocks) to lift specificity beyond a single action.

DimensionReasoningScore

Specificity

The description names the domain ("DOCX templates") and one concrete action ("Fill") with a preservation constraint ("preserving content placement"), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It does not list several specific actions (e.g. placeholder substitution, conditional regions, writing a new file), so it is not a 4.

3 / 5

Completeness

It has a clear 'what' (fill bounded DOCX templates while preserving content placement) but no 'when' — there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is above 2 because the 'what' is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords like "Fill", "DOCX", and "templates" are present, but common natural variations users would say are missing: "Word", ".docx", "placeholders", "offer letter", or "mail merge". This matches 'some relevant keywords but missing common variations or synonyms' rather than the good coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

"Fill bounded DOCX templates while preserving content placement" carves out a mostly distinct niche (bounded template filling rather than general document work), with only minor overlap risk against general DOCX editing/creation skills. It falls short of 5 because without placeholder or trigger phrases, a general 'edit this Word doc' request could still plausibly surface competing skills.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

Bitterbot-AI/bitterbot-desktop

Path

benchmarks/collective-learning/published/executable-learning-20261114/recipient/package/SKILL.md

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.