CtrlK
BlogDocsLog inGet started
Tessl Logo

word-analysis

Word (.docx/.doc) 文档全量解析。覆盖:正文/段落文本提取、表格数据提取、高亮/颜色格式读取、多文件汇总对比、嵌入图片转 caption。

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is lean and highly actionable with well-organized executable methods, but it lacks explicit validation checkpoints in its workflows and keeps all content in one monolithic file rather than splitting detail into references.

Suggestions

Add explicit validation/feedback steps for risky operations — e.g. after libreoffice .doc conversion, verify the output .docx opens before proceeding; after multi-file aggregation, summarize success/failure counts so failures are visible.

Move the larger detail blocks (Method 3 format-aware extraction, Method 5 image captioning) into one-level-deep reference files (e.g. references/FORMATS.md, references/IMAGES.md) and keep SKILL.md as a concise overview with signaled links.

Replace the placeholder CAPTION path '/path/to/skills/sn-da-image-caption/scripts/caption.py' with a real, resolvable path or a guarded fallback so Method 5 is fully executable as written.

DimensionReasoningScore

Conciseness

The body is mostly executable code with brief, purposeful docstrings and comments; it does not explain concepts Claude already knows and assumes competence, so every token earns its place.

3 / 3

Actionability

Five core methods plus common patterns are copy-paste-ready executable Python with concrete functions; the only blemish is the placeholder CAPTION path in Method 5, but the overwhelming majority is fully executable.

3 / 3

Workflow Clarity

Methods are individually clear but presented as independent recipes rather than a sequenced workflow, with no explicit validate→fix→retry checkpoints for the batch/multi-file and .doc-conversion operations; the guidelines cap workflow clarity at 2 for batch operations lacking validation, despite the try/except handling in process_all_docs.

2 / 3

Progressive Disclosure

A single ~270-line monolithic file with no bundle files; sections are well-organized but content that could be split (format-aware extraction, image captioning) is inline, matching the anchor for 'content that could be separate is inline' and not qualifying for the under-50-lines exception.

2 / 3

Total

10

/

12

Passed

Description

82%

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 specific, distinctive, and rich in natural trigger terms, but it omits an explicit 'when to use' clause, which limits completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to parse, extract, or compare Word (.docx/.doc) documents — text, tables, highlights/colors, or embedded images.'

Include a couple of natural trigger variations users might say (e.g. '读取 Word 表格', '标黄的内容', 'docx 高亮') to broaden trigger-term coverage further.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '正文/段落文本提取、表格数据提取、高亮/颜色格式读取、多文件汇总对比、嵌入图片转 caption' — matching the anchor for several specific concrete actions rather than a partial domain+actions list.

3 / 3

Completeness

Strongly answers 'what' via the 覆盖 list, but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which the guidelines state caps completeness at 2; not a 1 because the 'what' is comprehensive.

2 / 3

Trigger Term Quality

Covers natural terms users would say — 'Word (.docx/.doc)', '文档', '表格', '高亮', '颜色', '嵌入图片' — comparable in coverage to the anchor-3 example; voice is third-person declarative so no penalty applies.

3 / 3

Distinctiveness Conflict Risk

A clearly Word-specific niche with distinctive format-aware operations (highlight/color reading, image captioning) that is unlikely to conflict with PDF or Excel skills.

3 / 3

Total

11

/

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
OpenSenseNova/SenseNova-Skills
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.