CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

docx-placeholder-workflow

Fill bounded DOCX templates while preserving content placement

Quality

77%

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/source/package/SKILL.md

The canonical home for this skill is docx-placeholder-workflow in Bitterbot-AI/bitterbot-desktop

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary contract specification for a single-purpose helper: fully executable CLI guidance, an explicit exit-code feedback loop, precise scope and out-of-scope boundaries, and clean section organization with the implementation correctly delegated to the entrypoint script. Its only weakness is mild repetition in the conditional-governance rule, which could be tightened without losing clarity.

DimensionReasoningScore

Conciseness

The body is dense, contract-level specification with no explanations of concepts Claude already knows; the only trimmable padding is the bare-RELOCATION-never-an-alias rule stated three ways within one bullet ("never acts as an alias or fallback", "never affects keep/drop", plus the parenthetical) and the restated inputs-never-modified guarantee.

4 / 5

Actionability

The full CLI invocation with all required arguments, a copy-paste example with concrete development/case-02 paths, and an exit-code diagnostic table are fully executable and cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

This is a simple single-action skill where the one action is unambiguous: one command, three required args, and a contract output filename. The exit-code table with stderr diagnostics forms an explicit validation/feedback loop, and the operation is expressly non-destructive ("Inputs are never modified", "does not edit either input"), so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed: implementation is properly externalized to the helpers/fill_docx.py entrypoint declared in frontmatter and CLI usage, leaving a clear contract overview. Sections (When to use / Scope / Integrity guarantees / CLI usage / Example / Dependencies) are well-organized with easy navigation and nothing that belongs in a separate file is inlined.

5 / 5

Total

19

/

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 is concise and reasonably specific with a distinct niche, but it answers only 'what' and not 'when', and its keyword coverage misses natural synonyms like "Word", ".docx", and "placeholder". Adding an explicit trigger clause and a second concrete action (e.g., resolving conditional blocks from JSON data) would lift it substantially.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., "Use when filling a Word/DOCX template (e.g., an offer letter) from a JSON data object with {{PLACEHOLDER}} fields."

Include natural synonyms and the file extension users would actually say: "Word", "DOCX", ".docx", "placeholders", "offer letter", "template filling".

Mention a second concrete capability — substituting {{FIELD_NAME}} placeholders from JSON and keeping/dropping conditional regions — to raise specificity beyond a single action.

DimensionReasoningScore

Specificity

"Fill bounded DOCX templates while preserving content placement" names the domain and two concrete actions (fill, preserve placement), but omits the JSON data input and conditional resolution, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor.

3 / 5

Completeness

The description gives a clear 'what' (fill bounded DOCX templates preserving content placement) but contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like "DOCX", "templates", and "fill" are present, but common variations users would say — "Word", ".docx", "placeholder", "offer letter", "mail merge" — are missing, matching the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

"bounded DOCX templates" plus "preserving content placement" carves a mostly distinct template-filling niche with only minor overlap risk against generic docx editing skills; not 5 because the lack of explicit trigger phrases leaves some ambiguity about when it applies.

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/source/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.