docx-dual-parse

Extract text from DOCX files using shell or Python zipfile, with environment-aware fallback

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/docx-shell-parse-enhanced-4bba79/SKILL.md

Quality

Content

77%

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

The content is highly actionable with executable code and a clear, validated workflow, but it is verbose due to repeated equivalent implementations and monolithic rather than progressively disclosed. Consolidating redundant variants and splitting reusable scripts into referenced files would improve both conciseness and progressive disclosure.

Suggestions

Consolidate the redundant implementations: keep the unified parse_docx function plus one canonical shell and one Python example, and drop the near-duplicate step-by-step and temp-dir re-implementations.

Move the reusable functions (parse_docx_shell, parse_docx_python, parse_docx) into a scripts/ file referenced from SKILL.md so the body stays a lean overview.

Trim incidental concept restatement (e.g. "DOCX files are ZIP archives containing XML files") and the temp-dir debugging alternatives, or relocate the latter to a references/ file for advanced use.

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete code, but it is heavily redundant — shell steps, a shell function, python steps, a python function, a unified function, and two temp-dir variants all perform essentially the same extraction and could be consolidated.	2 / 3
Actionability	It provides fully executable commands and copy-paste-ready functions (e.g. parse_docx_shell, the inline zipfile snippet, and the unified parse_docx), giving specific, runnable guidance.	3 / 3
Workflow Clarity	Methods use numbered steps, preceded by explicit environment detection and followed by a Verification section and an error-handling tip to "validate output is non-empty before proceeding," supplying clear checkpoints and a recovery loop.	3 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a single ~275-line monolithic file with no external references; reusable functions and the temp-dir alternatives that could live in separate files are inline.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 concrete and clearly scoped to DOCX text extraction with a distinct dual-method niche, but it lacks an explicit usage trigger and misses common natural keyword variations. Adding a "Use when..." clause and terms like "Word documents" / ".docx" would raise completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when extracting text from Word/DOCX files, especially in containers or sandboxes where python-docx or unzip may be unavailable."

Add common natural keyword variations such as "Word documents" and ".docx" alongside "DOCX files" to improve trigger-term coverage.

Replace jargon like "environment-aware fallback" with user-facing phrasing (e.g. "automatically falls back to Python when shell tools are missing") to keep triggers natural.

Dimension	Reasoning	Score
Specificity	"Extract text from DOCX files using shell or Python zipfile" names the domain and a concrete action plus methods, but lists only one main action rather than multiple distinct concrete actions like the 3-anchor (extract + fill + merge).	2 / 3
Completeness	The what is clearly stated, but there is no explicit "Use when..." trigger clause; per the rubric a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Natural terms like "DOCX files" and "extract text" appear, but common variations ("Word documents", ".docx") are missing and jargon like "environment-aware fallback" and "Python zipfile" dilutes the natural keywords.	2 / 3
Distinctiveness Conflict Risk	"Extract text from DOCX files using shell or Python zipfile" carves a clear DOCX-specific niche that is unlikely to trigger for or conflict with other skills.	3 / 3
	Total	9 / 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: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/docx-shell-parse-enhanced-4bba79/SKILL.md
Commit: c5a9c4b

Reviewed: 2 days 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.