| name | document-writer |
| description | Document generation skill for creating DOCX, PDF, PPTX, and other formatted documents. Guides structured content creation with proper formatting, headings, tables, and professional presentation.
|
Document Writer Skill
When to use this Skill
Use this Skill when you are:
- Creating a formatted document (DOCX, PDF, PPTX, XLSX)
- Generating a report, proposal, or specification document
- Converting markdown or structured data into a professional document format
- Creating presentation slides from content
Document Creation Process
1. Understand the Purpose
- Identify the document type (report, proposal, specification, presentation)
- Determine the target audience (technical, business, executive)
- Note any formatting requirements or templates to follow
2. Structure the Content
- Create a clear outline with logical section hierarchy
- Use headings consistently (H1 for title, H2 for sections, H3 for subsections)
- Organize information in order of importance or logical flow
- Include a summary or executive overview for longer documents
3. Write the Content
- Use clear, concise language appropriate for the audience
- Support claims with data, examples, or references
- Use bullet points and numbered lists for scannable content
- Include tables for structured data comparisons
- Add diagrams or charts where visual representation aids understanding
4. Format and Polish
- Apply consistent styling throughout the document
- Ensure headings, fonts, and spacing follow the template or convention
- Add headers, footers, page numbers as needed
- Include table of contents for documents longer than 5 pages
- Review for grammar, spelling, and consistency
Document Types
Reports
- Executive summary at the top
- Findings organized by theme or chronology
- Recommendations clearly separated from findings
- Appendix for supporting data
Presentations
- One key message per slide
- Minimal text — use visuals and bullet points
- Speaker notes for detailed talking points
- Consistent slide layout and branding
Specifications
- Clear scope statement
- Detailed requirements with acceptance criteria
- Diagrams for architecture or workflows
- Glossary for domain-specific terms
Things to Avoid
- Walls of text without structure or headings
- Inconsistent formatting within the same document
- Mixing technical depth levels without clear audience targeting
- Creating documents without understanding who will read them
