CtrlK
BlogDocsLog inGet started
Tessl Logo

doc-reader

Read any common document/data file — PDF, Word (.docx), Excel (.xlsx/.xls), PowerPoint (.pptx), images (OCR), CSV/TSV, plain text, JSON/YAML/TOML, HTML/XML, and most source-code files. Use the `read_document` tool.

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable skill body with concrete tool calls and a useful return-envelope spec. It could be slightly leaner in the OCR configuration section and add stronger validation feedback loops for edge cases.

Suggestions

Trim the OCR engine configuration detail (env-var overrides, provider mapping) into a brief reference and move the long-form explanation to a bundled reference file.

Add an explicit validate/retry loop for OCR failures (e.g. retry with a different engine before reporting empty text).

DimensionReasoningScore

Conciseness

Efficient, table-driven, and assumes Claude's intelligence without explaining what formats are; the OCR configuration section is somewhat detailed but still on-task, fitting the efficient-minor-trim anchor rather than the fully-lean anchor.

4 / 5

Actionability

Provides copy-paste-ready read_document() calls covering common formats plus the return envelope and per-format extra keys, matching the fully-executable anchor.

5 / 5

Workflow Clarity

Workflows are clearly sequenced with an explicit checkpoint ('If OCR returns empty, tell the user; don't fabricate'); not a destructive/batch operation so the cap does not apply, but checkpoints are light rather than full validate-fix-retry loops, fitting the clear-sequence-most-checkpoints anchor.

4 / 5

Progressive Disclosure

No bundle files exist, so all content is appropriately organized in a single SKILL.md with clear sections and tables; well-structured with minor gaps rather than a reference-split layout, fitting the good-structure anchor.

4 / 5

Total

17

/

20

Passed

Description

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

A strong, specific, trigger-rich description that clearly states capabilities and enumerates formats with extensions. Its main weakness is the absence of an explicit 'when to use' clause, which caps completeness.

Suggestions

Add an explicit 'Use when ...' clause naming common user phrasings (e.g. 'Use when the user asks to read, extract, or convert a document or data file').

Tighten the 'any common document/data file' framing to reduce overlap risk with format-specific skills (PDF, Excel).

DimensionReasoningScore

Specificity

Lists multiple concrete actions (read, OCR) plus comprehensive per-format coverage (PDF, Word, Excel, PowerPoint, images, CSV/TSV, config, markup, source code), matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is explicit ('Read any common document/data file ... Use the read_document tool') but there is no 'Use when...' or equivalent trigger guidance for when Claude should invoke it, so completeness caps at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Covers natural terms plus file extensions for every category (e.g. '.docx', '.xlsx/.xls', '.pptx', '.csv/.tsv'), matching the comprehensive-synonyms-and-extensions anchor.

5 / 5

Distinctiveness Conflict Risk

Has a clear niche (a single unified document reader) with mostly distinct triggers, but the broad 'any common document/data file' phrasing carries minor overlap risk with format-specific skills, fitting the mostly-distinct anchor.

4 / 5

Total

17

/

20

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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