CtrlK
BlogDocsLog inGet started
Tessl Logo

docx-shell-extract

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

65

Quality

77%

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

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

The content is highly actionable, with copy-paste-ready commands, a clear sequenced workflow, and an explicit verification step. Its only weakness is minor over-explanation of shell flags and sed behavior that Claude could infer, slightly trimming token efficiency.

Suggestions

Tighten the explanatory prose — e.g. drop the per-line 'This removes...' bullet list and the `-p` flag note, letting the code stand on its own.

Optionally fold Step 4 into the Complete Example to avoid a near-duplicate pipeline.

DimensionReasoningScore

Conciseness

The body is lean and dominated by executable code, but contains minor over-explanation such as re-listing what each sed pipeline removes and the `-p` flag note, which Claude could largely infer.

4 / 5

Actionability

Fully executable, copy-paste-ready shell commands are provided across all steps plus a complete worked example and a verification snippet, covering the common extraction cases.

5 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced and the dedicated Verification section provides an explicit validation check (`[ -s "$OUTPUT_FILE"`) with an empty-output warning, giving a clear feedback loop for error recovery.

5 / 5

Progressive Disclosure

This is a single-purpose skill under 50 lines with no external bundle files and no in-body references; per the simple-skill scoring note, its well-organized section headers earn a 5 without separate reference files.

5 / 5

Total

19

/

20

Passed

Description

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

The description is clear and has both a 'what' and a 'when', but its capability list is narrow (a single action) and it omits common natural synonyms like 'Word documents' or '.docx'. It is solid but leaves room for broader trigger coverage and more enumerated actions.

Suggestions

Add concrete synonyms/extensions users would actually say, e.g. 'Word documents (.docx)' instead of only 'DOCX files'.

Enumerate a couple more concrete actions if the skill supports them (e.g. '...strip XML tags to plain text, save to a text file') to lift specificity.

Expand the 'when' clause into a broader trigger phrase such as 'Use when reading Word documents in a shell-only environment without python-docx'.

DimensionReasoningScore

Specificity

Names the DOCX domain and one concrete action ('Extract text') but offers no additional actions, matching the '1-2 concrete actions' anchor rather than the 'several specific actions' anchor above.

3 / 5

Completeness

Clearly states what it does ('Extract text from DOCX files using shell commands') and a 'when' trigger ('when python-docx is unavailable'), but the 'when' is a narrow constraint rather than broad, explicit trigger phrases, so it sits at anchor 4 not 5.

4 / 5

Trigger Term Quality

Includes relevant terms ('DOCX files', 'shell commands', 'python-docx') but misses common natural synonyms users would say such as 'Word documents', 'Word files', or the '.docx' extension.

3 / 5

Distinctiveness Conflict Risk

The DOCX-shell-extraction niche with a python-docx-unavailable constraint is mostly distinct with only minor overlap risk against closely related document skills.

4 / 5

Total

14

/

20

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.