CtrlK
BlogDocsLog inGet started
Tessl Logo

ocr

Extract text from images using Tesseract OCR

59

Quality

48%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./examples/skill/skills/ocr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

32%

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 concise and identifies the core capability (OCR text extraction) and the specific tool (Tesseract), but it lacks completeness by omitting explicit trigger guidance. It would benefit from additional trigger terms users naturally use and a clear 'Use when...' clause to help Claude select it appropriately.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to extract text from images, screenshots, scanned documents, or mentions OCR'

Include natural trigger term variations users would say: 'image to text', 'read text from picture', 'scan image', '.png', '.jpg', 'screenshot'

Expand specific capabilities: mention supported image formats, handling of handwritten vs printed text, or batch processing if applicable

DimensionReasoningScore

Specificity

Names the domain (images, OCR) and one action (extract text), but doesn't list multiple concrete actions like handling different image formats, batch processing, or output options.

2 / 3

Completeness

Describes what it does (extract text from images) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.

1 / 3

Trigger Term Quality

Includes relevant keywords 'images', 'Tesseract', and 'OCR' but misses common variations users might say like 'scan', 'read text from picture', 'image to text', '.png', '.jpg', or 'screenshot'.

2 / 3

Distinctiveness Conflict Risk

Mentioning 'Tesseract OCR' specifically helps distinguish it from other text extraction tools, but without explicit triggers it could still overlap with general image processing or document extraction skills.

2 / 3

Total

7

/

12

Passed

Implementation

64%

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

This skill provides clear, actionable commands for OCR text extraction with good coverage of options and languages. However, it's somewhat verbose with reference tables Claude doesn't need, and lacks guidance on validating OCR output quality or handling common failure cases like poor image quality.

Suggestions

Remove or significantly trim the language codes table and supported formats list - Claude knows these

Add a brief validation step: how to check if OCR output is reasonable (e.g., check confidence scores in JSON output, visual inspection guidance)

Move installation instructions and language reference to a separate REFERENCE.md file, keeping SKILL.md focused on usage

DimensionReasoningScore

Conciseness

The content is mostly efficient but includes some unnecessary sections like the full language table and supported formats list that Claude already knows. The capabilities section is somewhat redundant given the usage examples.

2 / 3

Actionability

Provides fully executable bash commands with clear examples covering basic usage, language options, preprocessing, and URL handling. Commands are copy-paste ready with concrete file paths and flags.

3 / 3

Workflow Clarity

This is a simple single-command tool, but lacks validation guidance. No mention of how to verify OCR success, handle errors, or what to do if output quality is poor. For a tool where accuracy varies, feedback on checking results would help.

2 / 3

Progressive Disclosure

Content is reasonably organized with clear sections, but everything is inline in one file. The language table and installation instructions could be referenced separately. No links to additional resources or advanced usage documentation.

2 / 3

Total

9

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
trpc-group/trpc-agent-go
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.