CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-doc-delivery

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

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

56%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 delivers a clear, actionable conversion workflow with concrete commands, good edge-case handling, and a sensible prerequisites check. Its weaknesses are verbosity — generic styling best practices and duplicated pattern sections inflate the token budget — and a monolithic body that should offload reference material to bundle files.

Suggestions

Remove or drastically condense the 'Professional Styling Tips' and 'Best Practices' sections (generic guidance Claude already knows, ~70 lines) and trim 'Common Conversion Patterns' and 'Integration with Knowledge Mode', which duplicate the Conversion Guidelines and Overview content.

Move the per-workflow format recommendation matrices and the three example workflows into a reference file (e.g., references/format-guide.md) and keep a one-line pointer in SKILL.md, reducing the body to the workflow steps, prerequisites check, and edge cases.

Add an explicit post-conversion verification step (e.g., confirm the artifact exists at the reported path and is non-empty before claiming success) to close the workflow-clarity validation gap.

DimensionReasoningScore

Conciseness

The ~360-line body contains several padded sections restating knowledge Claude already has: "Professional Styling Tips" ("One main idea per slide", "Use built-in heading styles", "Add page numbers") and "Best Practices", while "Common Conversion Patterns" and "Integration with Knowledge Mode" largely duplicate the Conversion Guidelines and Overview sections. This matches anchor 2 (noticeably verbose) rather than 3, where only occasional tightening would be needed.

2 / 5

Actionability

Concrete, executable guidance is provided: `ls -lht ~/.claude-octopus/results/ | head -10`, the `document-renderer.py --format FORMAT --available-skill NAME` invocation with argument-quoting rules, and ready-made edge-case response templates. Minor gaps (e.g., "Invoke the resolved DOCX renderer" delegates without showing the call) keep it below anchor 5.

4 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced (locate markdown, choose format, invoke renderer, apply styling) with a prerequisites checkpoint (verify `scripts/helpers/document-renderer.py` exists before running) and explicit failure handling ("report that specific problem... report failures without claiming a completed conversion"). It falls short of 5 because there is no explicit post-conversion output verification step.

4 / 5

Progressive Disclosure

The body has clear section headers and navigation, but with no bundle files present, all ~360 lines are inline: the per-workflow format matrices, styling tips, and example workflows are content that clearly belongs in separate reference files, and the only file pointers (`docs/DOCUMENT-RENDERERS.md`, `scripts/helpers/`) are external to the skill. This matches anchor 3 (some structure, content that should be separate is inline) rather than 2, since structure is good rather than minimal.

3 / 5

Total

13

/

20

Passed

Description

70%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 is compact and covers both what and when with concrete format names, scoring well on completeness and trigger quality. Its main gaps are a single action verb limiting specificity and missing natural product-name synonyms (Word, PowerPoint, Excel) that users commonly say.

DimensionReasoningScore

Specificity

"Convert markdown to DOCX, PPTX, XLSX, PDF office documents" names the domain and one concrete action with four specific formats, matching the anchor for 1-2 concrete actions. It is not 4 because only a single action verb (convert) is offered rather than several distinct capabilities.

3 / 5

Completeness

Explicitly answers both what ("Convert markdown to DOCX, PPTX, XLSX, PDF office documents") and when ("use when you need exportable deliverables"). The when-clause is generic rather than concrete trigger phrases, so it does not reach anchor 5.

4 / 5

Trigger Term Quality

Includes "export", "convert", "deliverables" plus the extensions DOCX/PPTX/XLSX/PDF, giving good keyword coverage. It falls short of 5 because natural product-name synonyms users say ("Word", "PowerPoint", "Excel") are missing.

4 / 5

Distinctiveness Conflict Risk

The markdown-to-office conversion niche is mostly distinct with clear format triggers, but has minor overlap with the document-skills renderers it delegates to. It is above anchor 3 because the scope (knowledge-work deliverables) is more specific than generic document handling.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-doc-delivery/SKILL.md

Reviewed

Table of Contents

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.