docx-creator
Generates branded .docx files following enterprise standards with a 4-color Microsoft visual scheme.
Install
mkdir -p .claude/skills/docx-creator && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15945" && unzip -o skill.zip -d .claude/skills/docx-creator && rm skill.zipInstalls to .claude/skills/docx-creator
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create vibrant, colorful Microsoft Word documents (.docx) using the 4-color Microsoft logo palette (Red, Green, Blue, Yellow). Each section gets a different logo color for headings and tables, with decorative 4-color bars between sections. USE FOR: create Word document, generate docx, colorful document, Microsoft-branded document, workshop guide, training material, client-facing Word doc, colorful, 4 cores, visual, vibrante. DO NOT USE FOR: presentations (use pptx-creator), PDFs (use pdf-creator), Excel (use xlsx-creator).Key capabilities
- →Create Microsoft Word documents (.docx)
- →Apply a 4-color Microsoft logo palette to headings and tables
- →Add decorative 4-color bars between sections
- →Generate a cover page with Microsoft+GitHub logo and metadata
- →Include a Table of Contents after the cover page
- →Auto-fill document properties like author, title, subject, and keywords
How it works
This skill creates Word documents by applying a specific 4-color palette and incorporating mandatory elements like a cover page, table of contents, and headers/footers.
Inputs & outputs
When to use docx-creator
- →Creating workshop guides
- →Generating training materials
- →Drafting professional documents
About this skill
Microsoft DOCX Colorful Creator
Create enterprise-grade, professional Word documents using the 4-color Microsoft logo palette — a visually vibrant alternative to the standard single-blue ms-docx-creator.
Core Principles — ALWAYS Follow These
Every document created with this skill MUST include:
| # | Requirement | Details |
|---|---|---|
| 1 | Cover Page | Modern, themed, with Microsoft+GitHub logo, 4-color bars, title, metadata, confidentiality |
| 2 | Table of Contents | Always generated after cover page — no exceptions |
| 3 | Document Properties | Auto-filled: author=[email protected], title, subject, keywords matching the theme |
| 4 | Header | {Title} | Software GBB Americas (NEVER "Latam") |
| 5 | Footer | Microsoft Confidential | Page X of Y |
| 6 | Rich Visual Elements | Tables, icons, highlights, callouts, diagrams, flows, charts as needed |
| 7 | Standard Closing Page | "Thank You" + Contact info + Next Steps (when applicable) |
| 8 | English Only | All content must be written in English |
| 9 | Best Practices | Use enterprise documentation best practices throughout |
When to Use This vs ms-docx-creator
| This skill (ms-docx-colorful) | ms-docx-creator |
|---|---|
| Client-facing workshop guides | Internal technical specs |
| Training materials & participant guides | Architecture documents |
| Assessment reports & playbooks | Formal proposals |
| Visually rich enterprise handouts | Executive summaries |
| Educational/didactic content | Single-color branded docs |
| When user asks for "colorful" | When user asks for "standard" |
Color System
The 4 Microsoft logo colors rotate across sections:
| Color | Hex | RGB | Text Color |
|---|---|---|---|
| Blue | #00A4EF | rgb(0, 164, 239) | White |
| Green | #7FBA00 | rgb(127, 186, 0) | White |
| Yellow | #FFB900 | rgb(255, 185, 0) | Black (readability) |
| Red | #F25022 | rgb(242, 80, 34) | White |
Quick Start
import sys, os
sys.path.insert(0, '<skill-path>/scripts')
from create_colorful_document import MSColorfulDocCreator, Icons
# Logo auto-resolves from assets/ folder, or specify explicitly
doc = MSColorfulDocCreator(
title="Document Title",
subtitle="Description of the document",
version="1.0",
client="Client Name", # Optional
author="[email protected]", # Always this
subject="Topic keywords for properties", # Auto-fills doc properties
keywords="keyword1, keyword2, keyword3", # Auto-fills doc properties
category="Workshop Guide", # Auto-fills doc properties
logo_path="<skill-path>/assets/logo-msft-github-color-black.png", # Auto-resolved if omitted
)
# 1. ALWAYS: Cover + TOC + Header/Footer
doc.create_full_document()
# 2. Content with rotating colors
doc.add_executive_summary("Overview text...", color="blue")
doc.add_color_bar()
doc.add_section_heading("Section Title", level=1, color="green")
doc.add_body("Paragraph text...")
doc.add_bullets(["Item 1", "Item 2"])
doc.add_table(
headers=["Col1", "Col2", "Col3"],
rows=[["A", "B", "C"], ["D", "E", "F"]],
color="green"
)
doc.add_color_bar()
doc.add_section_heading("Another Section", level=1, color="yellow")
doc.add_highlight_box("Key Point", "Important content here", color="yellow", icon=Icons.TARGET)
doc.add_key_takeaway("Critical insight...", color="yellow")
doc.add_best_practice("Recommended approach...", color="green")
doc.add_note("Tip: ", "Helpful information", color="blue")
doc.add_diagram_placeholder("Architecture diagram description", color="blue")
doc.add_code_block("print('hello')", language="python")
doc.add_source("Source Name", "https://url.com")
doc.add_icon_list([(Icons.CHECK, "Done"), (Icons.ROCKET, "In Progress")])
# 3. ALWAYS: Closing page with contact and next steps
doc.add_closing_page(
next_steps=["Step 1", "Step 2", "Step 3"],
contact_name="Paula Silva",
contact_email="[email protected]",
contact_role="Senior Software Engineer | Global Black Belt",
contact_team="Software GBB Americas",
github_usernames=["@paulanunes85", "@paulasilvatech"], # Default if omitted
additional_contacts=[ # Optional
{"name": "Colleague", "email": "[email protected]", "role": "Role",
"github": ["@username"]}
]
)
doc.save("/path/to/output.docx")
Dependencies: pip install python-docx lxml
Workflow
1. IDENTIFY document type and target audience
2. GATHER content — NEVER invent information
3. PLAN color assignment: assign each major section a logo color (rotate evenly)
4. CREATE with scripts/create_colorful_document.py:
a. Initialize with ALL properties (title, subtitle, subject, keywords, category)
b. create_full_document() → Cover + TOC + Header/Footer
c. Add content sections with rich visual elements
d. add_closing_page() → Contact + Next Steps
5. SAVE with naming: {name}_v{version}.docx
Document Properties — ALWAYS Fill These
The document properties (File > Properties in Word) MUST be filled:
| Property | Value | Example |
|---|---|---|
| Author | [email protected] | Always |
| Title | Document title | "Agentic DevOps Workshop Guide" |
| Subject | Topic description | "AI-Native DevOps, GitHub Copilot, Azure" |
| Keywords | Relevant keywords | "DevOps, AI, GitHub, Azure, Workshop" |
| Category | Document type | "Workshop Guide", "Assessment Report", etc. |
| Comments | Team attribution | "Created by Software GBB Americas" |
| Language | en-US | Always English |
Visual Elements — Use Generously
Use these elements throughout documents to create professional, enterprise-grade content:
| Element | Method | When to Use |
|---|---|---|
| Colored Table | add_table(headers, rows, color) | Data comparisons, inventories, agendas, matrices |
| Highlight Box | add_highlight_box(title, text, color, icon) | Key points, important callouts, warnings |
| Key Takeaway | add_key_takeaway(text, color) | Section summaries, critical insights |
| Best Practice | add_best_practice(text, color) | Recommended approaches, guidelines |
| Note/Callout | add_note(title, text, color) | Tips, warnings, info callouts |
| Icon List | add_icon_list([(icon, text)]) | Status lists, feature lists, checklists |
| Diagram Placeholder | add_diagram_placeholder(desc, color) | Architecture, flows, sequences |
| Code Block | add_code_block(code, language) | Configuration, API samples |
| Color Bar | add_color_bar() | Section separators |
| Source Citation | add_source(text, url) | External references |
| Version History | add_version_history(versions) | Document versioning |
| Glossary | add_glossary([(term, def)]) | Technical terms |
| Exec Summary | add_executive_summary(text, color) | Long documents (5+ pages) |
Available Icons (from Icons class)
CHECK ✅ WARNING ⚠️ INFO ℹ️ IMPORTANT ❗ TIP 💡
PIN 📌 ROCKET 🚀 TARGET 🎯 CHART 📊 GEAR ⚙️
LINK 🔗 CALENDAR 📅 PERSON 👤 TEAM 👥 EMAIL 📧
STAR ⭐ CLOCK ⏱️ SHIELD 🛡️ KEY 🔑 ARROW_RIGHT ➡️
PROGRESS 🔄 NEXT ▶️
Color Assignment Strategy
Distribute colors evenly. Default rotation: Blue → Green → Yellow → Red → repeat.
Use doc.next_color() for auto-rotation, or specify explicitly:
doc.add_section_heading("Section", color="blue") # Explicit
doc.add_section_heading("Section") # Auto-rotation
For tables within a section, match the section's color OR use a contrasting one.
Document Structure Standards
For ALL Documents
Cover Page (themed)
Table of Contents
[Version History — if multiple versions]
[Executive Summary — if 5+ pages]
Content Sections (with visual elements)
[Glossary — if technical terms used]
Closing Page (contact + next steps)
Header Format
Line 1: {Title} | Software GBB Americas
Line 2: Version {x.xx} | [email protected]
⚠️ IMPORTANT: Always use "Software GBB Americas" — NEVER "Latam", "LATAM", or "Latam Software GBB".
Content Rules
CRITICAL — Never Invent Information
- Use ONLY information from context, directory, or project knowledge
- ALWAYS cite external sources with
doc.add_source() - If unavailable, state: "Information not available in provided context"
Enterprise Best Practices
- Use tables for ANY structured/comparative data
- Add highlight boxes for key points in every major section
- Include diagrams/flow placeholders where architecture or process is described
- Add icon lists for status tracking and checklists
- Use notes/callouts for tips, warnings, and important information
- Include glossary when 3+ technical acronyms are used
- Add executive summary for documents with 5+ content pages
- Always include next steps on the closing page when actionable items exist
Typography — Segoe UI Family ONLY
All text in the document MUST use Segoe UI and its variations. No other fonts allowed.
| Element | Font | Size | Weight |
|---|---|---|---|
| Cover Title | Segoe UI Light | 32pt | Regular |
| Cover Subtitle | Segoe UI Semilight | 16pt | Regular |
| Heading 1 | Segoe UI | 18pt | Bold |
| Heading 2 | Segoe UI | 15pt | Bold |
| Heading 3 | Segoe UI Semibold | 13pt | Bold |
| Heading 4 | Segoe UI | 12pt | Bold |
| Body Text | Segoe UI | 11pt | Regular |
| Table Header | Segoe UI | 10pt | Bold |
| Table Body | Segoe UI | 10pt | Regular |
| Code Blocks | Consolas | 10pt | Regular |
| Captions | Segoe UI | 9pt | Italic |
| Source Citations | Segoe UI | 9pt | Italic |
| Header | Segoe UI | 9pt/8pt | Regular |
| Footer | Segoe UI | 8pt | Regular |
Resources
| File | Purpose |
|---|---|
scripts/create_colorful_document.py | Main class with all methods |
| `asset |
Content truncated.
When not to use it
- →When creating presentations
- →When creating PDFs
- →When creating Excel documents
Prerequisites
Limitations
- →All content must be written in English
- →Only Segoe UI font family is allowed
- →The author is always [email protected]
How it compares
This skill generates visually vibrant, Microsoft-branded Word documents with specific structural requirements, unlike a standard document creator that might produce single-color or unformatted output.
Compared to similar skills
docx-creator side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| docx-creator (this skill) | 0 | 4mo | Review | Intermediate |
| vscode-screenshots | 0 | 6mo | Review | Beginner |
| positron-abstract-svg | 0 | 1mo | No flags | Intermediate |
| ckm:brand | 0 | 4mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by paulasilvatech
View all by paulasilvatech →You might also like
vscode-screenshots
palewire
Captures VSCode window screenshots using a semi-automated workflow. Use this when asked to capture, document, or screenshot VSCode, terminal output, or other desktop application states.
positron-abstract-svg
posit-dev
>
ckm:brand
akshh229
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.
drawbridge
alexknowshtml
|
ux-design
NhomNhem
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
ohmycaptcha-image
shenhao-stu
Generate product visuals, README banners, documentation illustrations, and architecture diagrams for OhMyCaptcha. Use when the user asks for repository art, hero images, deployment diagrams, or marketing visuals for captcha infrastructure projects.