plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-doc-delivery/SKILL.md
Convert markdown to DOCX, PPTX, XLSX office documents. Use when: AUTOMATICALLY ACTIVATE when user requests:. Export knowledge work to office formats (e.g., "export to Word", "create PowerPoint", "convert to DOCX"). Generate professional documents from research (e.g., "create presentation from this synthesis")
npx skillsauth add moliboy5000/.claude skill-doc-deliveryInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Convert knowledge work outputs from markdown to professional office documents (DOCX, PPTX, XLSX).
This skill helps you transform knowledge work results into polished, deliverable documents:
Before converting documents, verify the document-skills plugin is installed:
/plugin list | grep document-skills
If not installed:
/plugin install document-skills@anthropic-agent-skills
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 -10
Ask yourself:
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.
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. Use document-skills:docx to convert
5. Save to appropriate location
User 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. Use document-skills:pptx to convert
4. Each ## heading becomes a slide
5. Recommend adding title slide and summary
User wants multiple formats:
User: "Create both a Word doc and PowerPoint from this strategy"
1. Locate source markdown
2. Convert to DOCX using document-skills:docx
3. Convert to PPTX using document-skills:pptx
4. Provide both file paths
Input: ~/.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 to PPTX using document-skills:pptx
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. Convert to DOCX using document-skills:docx
4. Add table of contents
5. Format tables and charts properly
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. Convert to DOCX using document-skills:docx
4. Apply academic formatting (citations, references)
5. Export to PDF for final version
6. Save as "AI-Safety-Literature-Review-2026-01-18.pdf"
If 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 plugin missing:
Response: "The document-skills plugin is required for conversion.
Install it with:
/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 activates automatically
5. Professional document delivered
# List recent knowledge work outputs
ls -lht ~/.claude-octopus/results/ | head -5
# Check document-skills installed
/plugin list | grep document-skills
# Install document-skills
/plugin install document-skills@anthropic-agent-skills
# View specific markdown
cat ~/.claude-octopus/results/[filename].md
For questions about:
Document delivery skill for claude-octopus v7.3.0+
tools
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
development
DEFAULT PIPELINE for all tasks requiring execution. You (Claude) are the strategic orchestrator. Codex agents are your implementation army - hyper-focused coding specialists. Trigger on ANY task involving code, file modifications, codebase research, multi-step work, or implementation. This is NOT optional - Codex agents are the default for all execution work. Only skip if the user explicitly asks you to do something yourself.
development
This skill should be used when the user asks to analyze a UI screen recording and map interaction states into Figma. Trigger for requests such as "put video frames in Figma", "extract states from my recording", "map interactions from video to Figma", "analyze this screen recording", "create a storyboard from my video", "deconstruct this interaction in Figma", "annotate the UI states in my recording", or "pull the key moments from this video into Figma". Also trigger when the user references a video file (.mp4, .mov, .webm, .avi) together with Figma, design review, interaction analysis, prototypes, or UI states. The skill extracts key visual moments from a video, infers interaction triggers, and builds an annotated Figma Design storyboard using native Figma annotations and uploaded screenshot assets.
development
Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.