skill-doc-delivery

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

Quality

60%

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

35%

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

The body is well-structured and offers concrete commands and worked examples, but it is far too verbose, repeats knowledge-work concepts Claude already has, delegates its core conversion action to another plugin without executable detail, and lacks any validation checkpoints. It is also monolithic with no real bundle files despite referencing one.

Suggestions

Cut generic advice Claude already knows (slide/Word/PDF best-practices lists) and merge the overlapping Format Recommendations, Styling Tips, and Best Practices sections into one concise format-selection guide.

Replace the delegated "Use the /document-skills:docx skill" descriptions with an actual executable conversion command or code snippet so the core action is copy-paste ready.

Add a validation checkpoint after each conversion step (e.g. verify the output file exists and opens, or confirm slide/page count) to satisfy the workflow-clarity bar for batch conversions.

Move detailed format-by-workflow reference material into a references/ file and fix or remove the dangling skills/blocks/codex-host-adapter.md reference so navigation is one level deep and real.

Dimension	Reasoning	Score
Conciseness	The ~350-line body is padded with concepts Claude already knows (e.g. "One main idea per slide", "Use built-in heading styles", "5-7 bullet points max per slide"), repeats the plugin-install commands several times, and stacks overlapping sections (Format Recommendations, Professional Styling Tips, Best Practices) that restate the same ideas, matching the verbose/padded level-1 anchor rather than the mostly-efficient level-2 anchor.	1 / 3
Actionability	It gives concrete commands (ls -lht ~/.claude-octopus/results/, /plugin install document-skills@anthropic-agent-skills) and worked example filenames, but the central conversion action is delegated by description ("Use the /document-skills:docx skill") rather than executed with real conversion code, leaving it at level 2's incomplete-concrete-guidance anchor rather than copy-paste-ready level 3.	2 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1-4 and numbered example workflows), but there are no validation or verification checkpoints anywhere, and Pattern 3's batch conversion lacks any success-check feedback loop, so per the rubric's batch-operation guidance workflow_clarity is capped at 2 rather than reaching the level-3 explicit-validation anchor.	2 / 3
Progressive Disclosure	The skill is a single ~350-line monolithic file with no bundle files present (references/, scripts/, assets/ do not exist) and even references a skills/blocks/codex-host-adapter.md path that is absent; bulky content that could be split (format-recommendation lists, styling tips) is all inline, fitting the some-structure-but-could-be-better-organized level-2 anchor rather than a clean one-level-deep reference layout.	2 / 3
	Total	7 / 12 Passed

Description

85%

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 is specific and complete, clearly stating what the skill does and when to use it with concrete output formats and an explicit trigger clause. Its main weakness is trigger-term quality, leaning on format names plus the somewhat abstract phrase "exportable deliverables" rather than the full range of natural user phrasings.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ("Convert markdown") across multiple specific output formats ("DOCX, PPTX, XLSX, PDF"), matching the rubric's multiple-specific-concrete-actions anchor rather than the single-domain level-2 anchor.	3 / 3
Completeness	It explicitly answers both what ("Convert markdown to ... office documents") and when ("use when you need exportable deliverables") with an explicit trigger clause, matching the level-3 what-and-when anchor; it is not the level-2 case where 'when' is only implied.	3 / 3
Trigger Term Quality	It surfaces relevant format keywords (DOCX, PPTX, XLSX, PDF) and a "use when" clause, but the trigger phrasing "exportable deliverables" is somewhat abstract and omits common natural variations users would actually say (e.g. "Word document", "PowerPoint", "spreadsheet"), so it sits at level 2 rather than full natural-term coverage.	2 / 3
Distinctiveness Conflict Risk	It carves a clear niche (markdown-to-office-document conversion) with distinct format-based triggers unlikely to fire for unrelated skills; it uses third-person voice with no first/second-person phrasing, so it clears the level-3 distinct-niche bar.	3 / 3
	Total	11 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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

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.