An actionable, well-structured body with executable tool calls and a clear workflow. The main weakness is mild verbosity from a duplicated format list and some explanatory prose that assumes too little of Claude.

Suggestions

Consolidate the supported-format list into one section to avoid repeating it across "What MarkItDown Does" and "When NOT to Use".

Trim definitional prose (e.g., "preserves document structure including headings, tables, lists...") that describes concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete tool calls, but the supported-format list appears twice ("What MarkItDown Does" and "When NOT to Use") and prose like "It preserves document structure including headings, tables, lists..." explains things Claude already knows, so it could be tightened rather than reaching the lean anchor of 3.	2 / 3
Actionability	Provides a copy-paste-ready executable call `mcp__markitdown__convert_to_markdown(uri="file:///absolute/path/to/document.docx")` with specific URI schemes (http/https/file/data) and concrete absolute-path guidance, matching the fully-executable anchor.	3 / 3
Workflow Clarity	A clearly sequenced 4-step workflow (construct file:// URI → call tool → read output → answer) for a simple, non-destructive single-task skill, with failure modes (password-protected files, missing uv) noted under Important Notes; the missing-validation cap does not apply since this is not a destructive or batch operation.	3 / 3
Progressive Disclosure	Well-organized into clear sections (What it Does, When to Use, When NOT to Use, How to Use, Important Notes) with no nested references and no bundle files; all content is appropriately inline for a single-file skill of this scope.	3 / 3
	Total	11 / 12 Passed

Description

92%

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 description with explicit "Use when" triggers and good natural-keyword coverage. The main weakness is a PDF trigger that conflicts with the skill's own body guidance to prefer EdgeParse for PDFs.

Suggestions

Drop PDF from the description's primary triggers (or qualify it as a fallback) to avoid conflicting with the body's guidance to prefer EdgeParse for PDFs.

Lead with the core strength — binary Office formats (.docx/.pptx/.xlsx) — since that is the clearest distinct niche.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "convert PDF, read PPTX, extract text from DOCX, convert document to markdown" — matching the anchor for naming several specific actions rather than vague language.	3 / 3
Completeness	An explicit "Use when the user wants to..." clause answers both what the skill does (convert documents to Markdown) and when to use it, with explicit trigger guidance.	3 / 3
Trigger Term Quality	Combines natural user phrases ("convert to markdown", "read this document", "extract text from", "parse this file") with a full extension list (.pdf/.docx/.pptx/.xlsx/.xls/.ppt/.doc), giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	The niche (binary Office-format conversion via MarkItDown) is fairly distinct, but the description triggers on PDF ("convert PDF", ".pdf") while the body advises preferring EdgeParse for PDFs — an internal overlap that raises conflict risk, so it does not reach the clear-niche anchor of 3.	2 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Reviewed

6 days ago

Table of Contents

Discovery Implementation Validation