read-bin-docs

Straightforward text extraction from document files (text-based PDF only for now, no OCR or docx). Use when you just need to read/extract text from binary documents.

2.04x

Quality

76%

Does it follow best practices?

Impact

100%

2.04x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./read-bin-docs/SKILL.md

Quality

Content

77%

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

A solid, actionable skill with executable code examples and clear CLI usage patterns. The main weakness is redundancy between the Quick Start and Basic Usage sections, which wastes tokens without adding value. The 'Future' note and some explanatory text could be trimmed for better conciseness.

Suggestions

Merge the Quick Start and Basic Usage sections to eliminate the near-duplicate code block, keeping only one canonical example.

Remove the 'Future' note about DOCX/XLSX support — it adds no actionable value and wastes tokens.

Trim the 'Common Issues' explanations to be more terse, e.g., just '**No text extracted**: PDF is likely scanned/image-based (no OCR support).'

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but has redundancy — the basic usage section repeats nearly the same code as the quick start. The 'Common Issues' section and requirements are useful but could be tighter. The 'Future' note is unnecessary filler.	2 / 3
Actionability	Provides fully executable Python code and concrete CLI commands with multiple usage patterns (all pages, specific pages, output to file). The code is copy-paste ready with real library imports.	3 / 3
Workflow Clarity	This is a simple, single-purpose skill (text extraction) with no destructive or multi-step operations. The single action is unambiguous, and the progression from basic to specific pages to CLI usage is clear and logical.	3 / 3
Progressive Disclosure	The content is reasonably structured with sections, but the quick start and basic usage sections are nearly identical, creating redundancy. The reference to 'scripts/extract_pdf_text.py' is good but no bundle files were provided to verify. Content is all inline when the script details could be deferred.	2 / 3
	Total	10 / 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.

This is a solid description that clearly communicates its scope and when to use it, with helpful boundary-setting by explicitly noting what it doesn't do (no OCR, no docx). Its main weaknesses are limited specificity in concrete actions (only text extraction) and moderate trigger term coverage that could include more natural user phrasings. The 'Use when' clause and explicit limitations make it effective for skill selection despite these gaps.

Suggestions

Add more natural trigger terms users would say, such as '.pdf', 'parse PDF', 'get text from a PDF', or 'read a PDF file'.

Expand specificity by listing more concrete actions if applicable, e.g., 'Extracts plain text content, reads page-by-page text, retrieves text from text-based PDF files'.

Dimension	Reasoning	Score
Specificity	Names the domain (text extraction from document files) and specifies a key action (read/extract text), but only describes one core action rather than listing multiple specific concrete actions. The parenthetical clarification about text-based PDF and limitations adds useful specificity.	2 / 3
Completeness	Clearly answers both 'what' (text extraction from document files, text-based PDF) and 'when' ('Use when you just need to read/extract text from binary documents'). The explicit 'Use when' clause with trigger guidance is present.	3 / 3
Trigger Term Quality	Includes some relevant keywords like 'text extraction', 'PDF', 'read', 'extract text', and 'binary documents', but misses common user variations like '.pdf', 'get text from', 'parse PDF', or 'read PDF content'. The term 'binary documents' is somewhat technical and not what users would naturally say.	2 / 3
Distinctiveness Conflict Risk	The description carves out a clear niche by specifying 'straightforward text extraction', explicitly excluding OCR and docx, and focusing on text-based PDF. This makes it clearly distinguishable from OCR skills, docx processing skills, or more complex document manipulation tools.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: YPares/agent-skills
Commit: bc4c2ce

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.