doc

Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.

1.46x

Quality

68%

Does it follow best practices?

Impact

66%

1.46x

Average score across 5 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./bundled/skills/doc/SKILL.md

Quality

Content

62%

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

The skill body is well-organized with strong workflow sequencing and real feedback loops, and its rendering commands are executable. Its main gaps are the missing python-docx code example for the core editing task, some redundant/filler sections, and unused bundled assets.

Suggestions

Add a short, executable python-docx snippet (headings, styles, tables) under the editing step so the core task is copy-paste ready.

Drop the "Environment: No required environment variables." line and trim the "When to use" section to avoid restating the description.

Either reference the bundled assets (doc.png, doc-small.svg) where relevant or remove them so the bundle structure is fully signaled.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and actionable with no concept re-explanation, but the "When to use" section restates the description's triggers, the "Environment: No required environment variables" line is filler, and dual uv/pip plus dual OS install blocks add tokens that could be condensed.	2 / 3
Actionability	Rendering and install commands are concrete and copy-paste ready (soffice, pdftoppm, render_docx.py), but the core editing step only says "Use python-docx for edits and structured creation (headings, styles, tables, lists)" with no executable code example, leaving a key detail missing.	2 / 3
Workflow Clarity	The workflow is a clear five-step sequence with explicit feedback loops ("After each meaningful change, re-render and inspect", final-checks render loop with fix-and-repeat), satisfying the validation-checkpoint requirement for document manipulation.	3 / 3
Progressive Disclosure	The body is well-sectioned and signals its one-level-deep bundled script with a concrete invocation, but it is entirely monolithic and the bundled assets (doc.png, doc-small.svg) exist yet are never referenced or navigated from the body.	2 / 3
	Total	9 / 12 Passed

Description

75%

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 cleanly covers both capability and an explicit trigger and occupies a distinct niche, but its action verbs are somewhat generic and it misses the common "Word" user term. Tightening the capability statement and adding natural synonyms would lift the weaker dimensions.

Suggestions

Lead with a concrete third-person capability sentence (e.g. "Reads, creates, and edits .docx documents with formatting and layout fidelity") before the "Use when" clause.

Add the natural user term "Word" / "Word document" alongside ".docx" to broaden trigger coverage.

Replace generic verbs with specific operations (e.g. "apply styles, build tables, fix pagination") to raise specificity.

Dimension	Reasoning	Score
Specificity	It names the .docx domain and lists actions ("reading, creating, or editing"), but these are generic document verbs rather than the rich concrete operations (e.g. extract tables, fill forms) of a top anchor, and the description leads with a "Use when" trigger instead of a clean third-person capability statement.	2 / 3
Completeness	It explicitly answers both what (reading/creating/editing .docx with formatting/layout fidelity) and when via an explicit "Use when the task involves..." trigger clause, matching the top anchor.	3 / 3
Trigger Term Quality	It includes relevant natural terms (".docx documents", "formatting", "layout"), but omits the most common user phrasing ("Word", "Word document") and leans on tool names ("python-docx", "render_docx.py") rather than user vocabulary.	2 / 3
Distinctiveness Conflict Risk	The .docx niche scoped to formatting/layout fidelity with a dedicated render helper is a clear, distinct trigger set unlikely to fire for PDF, pptx, or generic document skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/doc/SKILL.md
Commit: f627ab5

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.