Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables
69%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/skill-doc-delivery/SKILL.mdConvert knowledge work outputs from markdown to professional office documents (DOCX, PPTX, XLSX).
This skill helps you transform knowledge work results into polished, deliverable documents:
Inspect the current session's advertised skills for the requested format.
A standalone pptx, docx, xlsx or pdf skill, or a namespaced equivalent,
is sufficient. The document-skills plugin is one possible source. Files on
disk do not establish that a skill is enabled for this session.
Set OCTO_ROOT to the installed Octopus root identified by this loaded skill or
the host's plugin-root metadata. Verify that it contains
scripts/helpers/document-renderer.py, then run it with
--format FORMAT and one --available-skill NAME for each advertised skill.
Pass --renderer NAME and --template PATH when explicitly requested.
Quote each argument as data, including every advertised skill name.
Use the returned skill and template for conversion.
The helper also reads saved choices from
~/.claude-octopus/document-renderers.json. See docs/DOCUMENT-RENDERERS.md.
If the selected skill is unavailable, discovery is ambiguous or the template is missing, report that specific problem. Do not replace a saved or explicit choice silently. Offer installation guidance only when the needed capability is absent; do not install plugins automatically.
Best for PPTX (PowerPoint):
Best for DOCX (Word):
Best for PPTX (PowerPoint):
Best for DOCX (Word):
Best for DOCX (Word):
Best for PDF:
Knowledge work outputs are stored in:
~/.claude-octopus/results/List recent outputs:
ls -lht ~/.claude-octopus/results/ | head -10Ask yourself:
Invoke the resolved skill with the source markdown, requested format and selected template. For slides with approved materials, include the approved slide skeleton, visual callout plan and appendix list. Otherwise, pass the source markdown without implying that an outline or slide materials were approved. Follow that skill's supported-format, authentication, publication and sharing rules. Report its actual artifact path or native deck URL, and report failures without claiming a completed conversion.
When the default document-skills renderers are selected, their capabilities are:
For DOCX (Word):
Use the /document-skills:docx skill to convert markdown to Word format.
Supports headings, lists, tables, and formatting.For PPTX (PowerPoint):
Use the /document-skills:pptx skill to convert markdown to PowerPoint.
Each ## heading becomes a slide, bullet points auto-format.For PDF:
Use the /document-skills:pdf skill to generate PDF documents.
Ideal for final deliverables and archival.After conversion, consider:
User ran one workflow, wants one document:
User: "Export my latest synthesis to a Word document"
1. Check ~/.claude-octopus/results/ for most recent .md file
2. Identify it's from synthesize workflow
3. Recommend DOCX for academic report format
4. Invoke the resolved DOCX renderer with the selected template
5. Save to appropriate locationUser wants to create a deck from research:
User: "Create a PowerPoint from this research"
1. Locate the research markdown
2. Identify key sections (## headings)
3. Invoke the resolved presentation renderer with the selected template
4. Each ## heading becomes a slide
5. Recommend adding title slide and summaryUser wants multiple formats:
User: "Create both a Word doc and PowerPoint from this strategy"
1. Locate source markdown
2. Resolve and invoke the DOCX renderer
3. Resolve and invoke the PPTX renderer
4. Provide both file pathsInput: ~/.claude-octopus/results/empathize-session-2026-01-18.md
Output Goal: Stakeholder presentation
Steps:
1. Read the empathize markdown
2. Extract persona sections
3. Convert with the resolved presentation renderer
4. Each persona becomes a slide
5. Add title slide and key insights summary
6. Save as "UX-Personas-2026-01-18.pptx"Input: ~/.claude-octopus/results/advise-market-analysis-2026-01-18.md
Output Goal: Comprehensive business case document
Steps:
1. Read the advise markdown
2. Structure as: Executive Summary, Analysis, Recommendations, Appendix
3. Add table of contents
4. Format tables and charts properly
5. Convert with the resolved DOCX renderer
6. Save as "Market-Analysis-Business-Case-2026-01-18.docx"Input: ~/.claude-octopus/results/synthesize-ai-safety-2026-01-18.md
Output Goal: Academic paper format
Steps:
1. Read the synthesize markdown
2. Structure as: Abstract, Introduction, Literature Review, Gaps, Conclusions
3. Apply academic formatting (citations, references)
4. Resolve and invoke the PDF renderer with the selected template
5. Save as "AI-Safety-Literature-Review-2026-01-18.pdf" and report its actual pathIf user requests export but no workflow was run:
Response: "I don't see any recent knowledge work outputs. Would you like to run:
- /octo:empathize (UX research)
- /octo:advise (strategic analysis)
- /octo:synthesize (literature review)
Then I can convert the results to your preferred format."If user doesn't specify format:
Response: "I can convert this to:
- DOCX (Word) - Best for detailed documentation
- PPTX (PowerPoint) - Best for presentations
- PDF - Best for final deliverables
Which format would you prefer based on your use case?"If multiple outputs exist:
Response: "I found several knowledge work outputs:
1. empathize-personas-2026-01-15.md (3 days ago)
2. advise-market-analysis-2026-01-18.md (today)
3. synthesize-research-2026-01-10.md (8 days ago)
Which would you like to convert?"If no suitable skill is advertised:
Response: "No renderer for the requested format is available in this session.
Enable an installed skill for that format, name an available renderer, or install
a suitable plugin such as:
/plugin install document-skills@anthropic-agent-skills
Then I can convert your knowledge work to office formats."This skill is designed to work seamlessly with the three knowledge mode workflows:
Knowledge Work Flow:
1. Run workflow: /octo:empathize (or advise/synthesize)
2. Review markdown output in ~/.claude-octopus/results/
3. Request conversion: "Export to PowerPoint"
4. This skill is used after explicit invocation
5. Professional document delivered# List recent knowledge work outputs
ls -lht ~/.claude-octopus/results/ | head -5
# Resolve from the actual advertised skills, for example a standalone pptx skill
python3 "$OCTO_ROOT/scripts/helpers/document-renderer.py" --format pptx --available-skill pptx
# View specific markdown
cat ~/.claude-octopus/results/[filename].mdFor questions about:
Document delivery skill for claude-octopus v7.3.0+
nyldn/claude-octopus
9a6967a
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.