Skill detail

skill-doc-delivery

Supports PPTX deliverables, but is a broad office-document export wrapper.

MatchPossibleReviewed for powerpoint
Sourcenyldn/claude-octopusExternal source
Reported installs27Popularity signal only

Inspect before use

Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.

Saved source preview

SKILL.md

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: skill-doc-delivery
description: "Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables"
---

> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.
> Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands.
> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.
> For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.


# Document Delivery for Knowledge Workers

Convert knowledge work outputs from markdown to professional office documents (DOCX, PPTX, XLSX).

## Overview

This skill helps you transform knowledge work results into polished, deliverable documents:

- **After empathize** → Export personas to PPTX decks or requirements to DOCX specs
- **After advise** → Convert strategic analysis to PPTX presentations or DOCX business cases
- **After synthesize** → Generate literature reviews as DOCX academic format or PDF

## Prerequisites Check

Before converting documents, verify the document-skills plugin is installed:

```bash
/plugin list | grep document-skills
```

If not installed:

```bash
/plugin install document-skills@anthropic-agent-skills
```

## Format Recommendations by Workflow

### Empathize Workflow → UX Research Outputs

**Best for PPTX (PowerPoint):**
- Persona decks for stakeholder presentations
- Journey map visualizations
- Research synthesis highlights
- Executive summaries

**Best for DOCX (Word):**
- Detailed persona documentation
- Research requirements specifications
- Interview transcripts and analysis
- User story documentation

### Advise Workflow → Strategic Analysis

**Best for PPTX (PowerPoint):**
- Strategy presentations for leadership
- Market analysis decks
- Competitive intelligence briefs
- Business case pitch decks
- Board presentations

**Best for DOCX (Word):**
- Comprehensive business cases
- Strategic recommendations reports
- Market research documentation
- Financial analysis reports

### Synthesize Workflow → Research Synthesis

**Best for DOCX (Word):**
- Literature review papers
- Research synthesis reports
- Academic research documentation
- Annotated bibliographies
- Technical white papers

**Best for PDF:**
- Final publications
- Archival versions
- Shareable research reports

## Conversion Guidelines

### Step 1: Locate Source Markdown

Knowledge work outputs are stored in:
```bash
~/.claude-octopus/results/
```

List recent outputs:
```bash
ls -lht ~/.claude-octopus/results/ | head -10
```

### Step 2: Choose Format Based on Purpose

Ask yourself:
- **Presenting to stakeholders?** → PPTX (visual, concise)
- **Comprehensive documentation?** → DOCX (detailed, structured)
- **Final publication?** → PDF (archival, unchangeable)
- **Data/frameworks?** → XLSX (tables, calculations)

### Step 3: Use Document-Skills Plugin

The document-skills plugin provides these capabilities:

**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.
```

### Step 4: Apply Professional Styling

After conversion, consider:
- **Consistent formatting** - Use heading styles, bullet hierarchies
- **Visual hierarchy** - Important points first, details later
- **Brand alignment** - Add logos, colors, fonts if needed
- **Readability** - Break up long paragraphs, use white space

## Common Conversion Patterns

### Pattern 1: Single Workflow → Single Document

User ran one workflow, wants one document:

```
User: "Export my latest synthesis to a Word document"

1. Check ~/.claude-octopus/results/ f
Read the full source on GitHub (opens external page)
Context

Related work