Converts documents to markdown with multi-tool orchestration for best quality. Supports Quick Mode (fast, single tool) and Heavy Mode (best quality, multi-tool merge). Use when converting PDF/DOCX/PPTX files to markdown, extracting images from documents, validating conversion quality, or needing LLM-optimized document output.
Install with Tessl CLI
npx tessl i github:daymade/claude-code-skills --skill markdown-toolsOverall
score
93%
Does it follow best practices?
Validation for skill structure
Discovery
100%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 strong skill description that excels across all dimensions. It provides specific capabilities (conversion modes, image extraction, quality validation), includes natural trigger terms (PDF/DOCX/PPTX, markdown), has an explicit 'Use when...' clause, and carves out a distinct niche with its multi-tool orchestration and LLM-optimization focus. Uses proper third person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Converts documents to markdown', 'multi-tool orchestration', 'Quick Mode (fast, single tool)', 'Heavy Mode (best quality, multi-tool merge)', 'extracting images', 'validating conversion quality'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Converts documents to markdown with multi-tool orchestration') and when ('Use when converting PDF/DOCX/PPTX files to markdown, extracting images from documents, validating conversion quality, or needing LLM-optimized document output'). Has explicit 'Use when...' clause with specific triggers. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'PDF', 'DOCX', 'PPTX', 'markdown', 'converting', 'extracting images', 'documents'. Covers file extensions and common terminology users would naturally use when needing document conversion. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on document-to-markdown conversion with specific differentiators (Quick Mode vs Heavy Mode, multi-tool orchestration, LLM-optimized output). The combination of markdown output focus and quality modes makes it distinct from generic document processing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
88%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill with excellent conciseness and progressive disclosure. The content efficiently communicates tool selection, usage patterns, and troubleshooting through tables and executable commands. The main weakness is the lack of integrated validation steps in the conversion workflow - validation exists as a separate section but should be woven into the workflow as explicit checkpoints.
Suggestions
Integrate validation into the Basic Conversion workflow: after conversion, add an explicit step to run validate_output.py and specify what to do if metrics fail thresholds
Add a feedback loop to the Heavy Mode Workflow section showing what to do when quality metrics indicate issues (e.g., 'If text retention <95%, try extracting images separately and re-run')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference and avoiding explanations of concepts Claude already knows. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable bash commands and clear installation steps. Commands are copy-paste ready with specific flags and options documented in context. | 3 / 3 |
Workflow Clarity | Heavy Mode workflow is explained with clear steps, but lacks explicit validation checkpoints and feedback loops. The quality validation section exists but isn't integrated into the conversion workflow as a mandatory step before considering output complete. | 2 / 3 |
Progressive Disclosure | Excellent structure with quick start at top, detailed sections following, and clear references to external documentation at the bottom. Tables provide scannable overviews, and advanced topics are appropriately linked to reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
88%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 14 / 16 Passed | |
Table of Contents
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.