CtrlK
BlogDocsLog inGet started
Tessl Logo

docx-shell-extract

Extract text from DOCX files using shell commands when python-docx is unavailable

67

Quality

80%

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/gdpval/skills/docx-shell-extract/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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 shell skill with executable commands and a verification checkpoint. The main drag is conciseness: redundant pipeline repetitions and explanations of concepts Claude already knows could be trimmed.

Suggestions

Collapse Steps 1-4 and the Complete Example into one canonical pipeline plus optional flags, removing repeated near-duplicate sed chains.

Cut elementary explanations (DOCX-as-ZIP, the -p flag) that assume too little of Claude, or move them to a brief one-liner.

Tighten the 'Alternatives to Explore' section into a compact bulleted reference rather than prose-style hints.

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands, but it explains things Claude already knows ("DOCX files are ZIP archives", what the -p flag does) and repeats near-identical pipelines across Steps 1-4 and the Complete Example, fitting the 'mostly efficient but could be tightened' anchor rather than the lean level-3 anchor.

2 / 3

Actionability

Every step provides complete, copy-paste-ready shell commands with concrete filenames (report.docx, output.txt), matching the 'fully executable code/commands; copy-paste ready' anchor and clearly above the pseudocode/incomplete level.

3 / 3

Workflow Clarity

Steps are clearly sequenced (extract → strip tags → clean → save) and followed by an explicit Verification section with a conditional check and empty-output warning, satisfying the 'clear sequence with explicit validation steps' anchor; this is a read-only pipeline so the lack of a fix-and-retry loop is appropriate.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed for this simple single-purpose skill; the body is organized into well-labeled sections (When to Use, Core Technique, Steps, Verification, Limitations, Alternatives) with no nested references, matching the well-organized-sections allowance for simple skills.

3 / 3

Total

11

/

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.

A concise, third-person description that clearly pairs a concrete capability with an explicit trigger condition. Its main weakness is listing a single action and missing common trigger synonyms like 'Word documents' or '.docx'.

Suggestions

Expand the action list slightly (e.g., 'extract text and content from DOCX files') to reach the multiple-concrete-actions bar.

Add natural trigger synonyms such as 'Word documents' or '.docx' so users phrasing it differently still match.

DimensionReasoningScore

Specificity

Names the domain ("DOCX files") and a concrete action ("Extract text") plus the tool ("shell commands"), but lists only one action rather than multiple specific concrete actions, so it matches the 'names domain and some actions' anchor rather than the 'lists multiple specific concrete actions' anchor.

2 / 3

Completeness

It states what it does ("Extract text from DOCX files using shell commands") and gives an explicit when-trigger ("when python-docx is unavailable"), satisfying the 'clearly answers both what AND when with explicit triggers' anchor; it is not the level below because the when-clause is explicit rather than merely implied.

3 / 3

Trigger Term Quality

Includes relevant terms a user might say ("DOCX files", "python-docx"), but omits common variations such as "Word documents" or ".docx", fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The DOCX-shell-extraction niche combined with the distinctive 'python-docx is unavailable' trigger makes it unlikely to fire for the wrong skill, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
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.