skill-doc-delivery

Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skill-doc-delivery/SKILL.md

Quality

Content

42%Weight 40%Scale 1-5

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

The skill provides a clear, well-structured conversion workflow with concrete file-location commands and explicit delegation to the document-skills plugin. Its main weaknesses are verbosity from generic formatting advice Claude already knows, missing output validation on batch conversions, and a monolithic body with no reference-file split.

Suggestions

Trim or move the generic "Professional Styling Tips" and "Best Practices" sections (PowerPoint/Word/PDF formatting advice) — Claude already knows this material and it adds significant token weight.

Add an explicit validation/verification step after conversion (e.g., confirm the output file exists and opens) — especially for the batch-conversion pattern, which currently has no checkpoints.

Split detailed format-specific guidance and the example workflows into reference files (e.g., FORMATS.md, EXAMPLES.md) referenced one level deep from SKILL.md, leaving only the overview and quick-start inline.

Dimension	Reasoning	Score
Conciseness	The ~350-line body includes several padded sections of generic advice Claude already knows (PowerPoint "5-7 bullet points max", Word heading-style tips, PDF font-embedding tips, "Best Practices" list), making it noticeably verbose.	2 / 5
Actionability	Concrete commands exist for locating files and installing the plugin, and specific delegated skill names are named, but the core conversion mechanics are delegated to other skills and the example workflows are pseudocode-style numbered steps rather than executable instructions.	3 / 5
Workflow Clarity	Steps are clearly sequenced (Step 1-4 plus a prerequisites check), but output verification is absent and the batch-conversion pattern has no validation; per the batch-operation rule this caps the score at 3.	3 / 5
Progressive Disclosure	The body is well-sectioned with clear headers, but no bundle files exist and content that would fit separate references (styling tips, format recommendations, example workflows) is all inlined in a single ~350-line file.	3 / 5
	Total	11 / 20 Passed

Description

65%Weight 40%Scale 1-5

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 clearly communicates the skill's purpose and includes a usable "use when" trigger, with good file-extension keyword coverage. It is weakened by a single generic action verb, missing common format synonyms, and a second-person phrasing that triggers the voice penalty.

Suggestions

Replace second-person phrasing with third person (e.g., "Convert markdown to DOCX/PPTX/XLSX/PDF. Use when the user requests exportable office deliverables.") to avoid the voice penalty.

Add common synonyms users say — Word, PowerPoint, Excel — alongside the file extensions to broaden trigger coverage.

Expand the action list beyond a single "Convert" verb (e.g., "Convert, assemble, and export markdown to...") to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and target formats (DOCX/PPTX/XLSX/PDF) but offers only one concrete action ("Convert markdown to..."); would be a 3 but reduced by 1 because the description uses second person ("use when you need").	2 / 5
Completeness	Clearly states what ("Convert markdown to ... office documents") and includes an explicit "use when you need exportable deliverables" clause, but the "when" is somewhat generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes file extensions (DOCX, PPTX, XLSX, PDF), "markdown", and "office documents"/"exportable deliverables", but misses common synonyms like Word/PowerPoint/Excel that users naturally say.	4 / 5
Distinctiveness Conflict Risk	The markdown-to-office-conversion niche is mostly distinct, though there is minor overlap risk with the document-skills plugin skills it delegates to.	4 / 5
	Total	14 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nyldn/claude-octopus
Path: .claude/skills/skill-doc-delivery/SKILL.md
Commit: 6a1fd2b

Reviewed: about 6 hours 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.