CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

The canonical home for this skill is doc in foryourhealth111-pixel/Vibe-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

A lean, actionable body with concrete commands and a well-sequenced render/validate loop. The main weakness is minor redundancy between the 'Quality expectations' and 'Final checks' sections.

Suggestions

Merge the overlapping re-render/inspect guidance in 'Quality expectations' and 'Final checks' into a single section to reduce redundancy.

Remove the empty 'Environment: No required environment variables.' section or fold it into a single line elsewhere.

Add a brief python-docx code snippet for the editing step, since the rendering commands are executable but the editing guidance stays abstract.

DimensionReasoningScore

Conciseness

Mostly efficient and free of concept-explanation padding, but 'Quality expectations' and 'Final checks' overlap on re-render/inspect guidance, and the empty 'Environment: No required environment variables.' line adds little.

2 / 3

Actionability

Provides fully executable, copy-paste-ready install and rendering commands (soffice, pdftoppm, render_docx.py) with concrete temp/output paths.

3 / 3

Workflow Clarity

A clear 5-step sequence with an explicit render->inspect->fix->repeat feedback loop, appropriate for document/layout operations.

3 / 3

Progressive Disclosure

Well-organized into clear sections with a one-level-deep bundled script (verified to exist) referenced and clearly signaled; no nested references.

3 / 3

Total

11

/

12

Passed

Description

85%Weight 40%Scale 1-3

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, specific description with an explicit 'Use when...' trigger and named tooling, clearly scoped to DOCX layout fidelity. Its main gap is missing common 'Word document' trigger variations users would naturally say.

Suggestions

Add common user-facing terms like 'Word documents' or 'Word files' alongside `.docx` to broaden natural trigger coverage.

Consider front-loading the 'Use when...' clause before the tooling preference so the trigger reads more naturally.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('reading, creating, or editing `.docx` documents') plus the formatting/layout-fidelity niche and specific tooling (python-docx, scripts/render_docx.py).

3 / 3

Completeness

Explicitly answers both what (read/create/edit docx with formatting fidelity and named tooling) and when via an explicit 'Use when the task involves...' clause.

3 / 3

Trigger Term Quality

Has natural terms (`.docx`, 'formatting', 'layout', 'visual checks') but misses common user phrasings like 'Word documents'/'Word files'.

2 / 3

Distinctiveness Conflict Risk

Tightly scoped to `.docx` with a layout-fidelity framing and a bundled script, making it unlikely to trigger for PDF, markdown, or generic document skills.

3 / 3

Total

11

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

JetBrains/skills

Path

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