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

Optimize this skill with Tessl

npx tessl skill review --optimize ./read-bin-docs/SKILL.md

Quality

Discovery

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, focused description that clearly communicates its narrow scope and when to use it. The explicit limitations (no OCR, no docx) are a strength for distinctiveness. It could benefit from slightly more specific trigger terms and listing additional concrete actions beyond basic text extraction.

Suggestions

Add more natural trigger term variations such as '.pdf', 'parse PDF', 'get text from PDF', 'read PDF content' to improve keyword coverage.

Consider listing more specific actions if applicable (e.g., 'extract text, read page content, retrieve paragraphs from text-based PDF files') to strengthen specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (text extraction from documents) and specifies a key constraint (text-based PDF only, no OCR or docx), but only describes one action (extract text) rather than listing multiple concrete capabilities.	2 / 3
Completeness	Clearly answers both 'what' (straightforward text extraction from text-based PDFs) and 'when' ('Use when you just need to read/extract text from binary documents'), with explicit scope limitations (no OCR, no docx).	3 / 3
Trigger Term Quality	Includes some natural terms 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'.	2 / 3
Distinctiveness Conflict Risk	The explicit constraints (text-based PDF only, no OCR, no docx) and the narrow scope (just text extraction, not analysis or manipulation) make this clearly distinguishable from broader document processing or PDF manipulation skills.	3 / 3
	Total	10 / 12 Passed

Implementation

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. The main weakness is redundancy between the Quick Start and Basic Usage sections, which wastes tokens without adding value. The skill is well-suited for its simple purpose but could be tightened by eliminating duplicate code blocks and unnecessary commentary.

Suggestions

Remove the 'Basic Usage' section or merge it with Quick Start — the code is nearly identical and wastes tokens.

Remove the 'Future: Support for DOCX...' line as it provides no actionable guidance and will become stale.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but has redundancy — the basic usage section repeats the quick start code almost identically, and some explanations like 'Works with most text-based PDFs' and the future plans note are unnecessary filler. The common issues section adds modest value but could be tighter.	2 / 3
Actionability	Provides fully executable, copy-paste ready Python code and CLI commands with concrete examples for different use cases (all pages, specific pages, output to file). The script usage examples with flags are specific and actionable.	3 / 3
Workflow Clarity	This is a simple, single-purpose skill (text extraction) with no destructive or batch operations requiring validation checkpoints. The single task is unambiguous with clear code examples, and the common issues section provides basic troubleshooting guidance.	3 / 3
Progressive Disclosure	The content is reasonably structured with sections progressing from quick start to advanced usage and troubleshooting. However, the basic usage section largely duplicates the quick start, and the content could benefit from clearer separation — the script reference could point to the actual script file rather than re-documenting its CLI interface inline.	2 / 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: aed1afb

Reviewed: 2 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.