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

88%

Does it follow best practices?

Impact

66%

1.46x

Average score across 5 eval scenarios

Securityby

Medium

Suggest reviewing before use

Quality

Content

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

A highly actionable, well-structured body with executable commands and an explicit validation render loop. Minor gains come from trimming filler and either using or removing the bundled assets.

Suggestions

Remove or merge the 'Environment: No required environment variables.' filler to tighten token efficiency.

Reference the bundled `assets/doc.png` and `assets/doc-small.svg` (e.g., as visual-layout examples) or remove them to keep the bundle consistent with the body.

Tighten 'Temp and output conventions' by collapsing the repo-specific `output/doc/` note if it is not universally applicable.

Dimension	Reasoning	Score
Conciseness	Mostly lean and well-organized with no over-explanation of concepts Claude already knows, though the 'No required environment variables.' section and a few procedural notes could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands (`soffice ... --convert-to pdf`, `pdftoppm -png`, `python3 scripts/render_docx.py`, `uv pip install`) covering the common cases.	5 / 5
Workflow Clarity	A clear numbered workflow with an explicit render-loop feedback checkpoint ('re-render and inspect every page at 100% zoom', 'Fix any spacing, alignment, or pagination issues and repeat the render loop').	5 / 5
Progressive Disclosure	Good section structure with a clearly signaled one-level-deep reference to the bundled `scripts/render_docx.py` (which exists), but the bundled `assets/` files are not referenced or put to use.	4 / 5
	Total	18 / 20 Passed

Description

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

A strong, concrete description with an explicit trigger clause and a well-scoped niche. The main room for improvement is broader trigger-term coverage (e.g., 'Word' synonyms).

Dimension	Reasoning	Score
Specificity	Names concrete actions ('reading, creating, or editing `.docx` documents', 'visual checks' via `scripts/render_docx.py`) but does not enumerate fuller coverage like tables, forms, or merging, leaving minor gaps.	4 / 5
Completeness	Explicitly answers both what (read/create/edit .docx, formatting/layout fidelity, visual checks) and when ('Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters').	5 / 5
Trigger Term Quality	Includes the `.docx` extension and natural phrases ('reading, creating, or editing'), but lacks common synonyms such as 'Word files' or 'Word documents' that users might say.	4 / 5
Distinctiveness Conflict Risk	Targets a clear `.docx`-specific niche focused on formatting/layout fidelity and visual rendering, giving it distinct triggers with minimal conflict risk.	5 / 5
	Total	18 / 20 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: d5ae560

Reviewed: 1 day 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.