Create Microsoft Word .docx documents from a title and body text. Use when the user asks for a Word file, .docx, formal letter, proposal, quote, report, or document to edit/share in Microsoft Word.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add LFTPadilla/agent-dev-kit --skill word-docx --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Word Docx?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lftpadilla-word-docx)More formats (shields.io, HTML) on the badges page.
---
name: word-docx
tags: ['skill']
description: Create Microsoft Word .docx documents from a title and body text. Use when the user asks for a Word file, .docx, formal letter, proposal, quote, report, or document to edit/share in Microsoft Word.
---
# Word DOCX
Use this skill when the user asks for a Word document.
## Output
- Create a real `.docx` file, not plain text renamed as `.docx`.
- Save it under the current workspace, preferably `workspace/` or the current conversation folder.
- Use a clear filename ending in `.docx`.
- Reply with the file path and a short note about what was created.
## Tool
```bash
python3 scripts/create_docx.py \
--title "Document title" \
--body-file input.md \
--output output.docx
```
## Body Format
The body file is plain text or simple Markdown:
- Lines starting with `# ` become Heading 1.
- Lines starting with `## ` become Heading 2.
- Lines starting with `- ` or `* ` become bullets.
- Blank lines separate paragraphs.
- Other lines become normal paragraphs.
## Guidance
- For letters, include date, recipient, greeting, body, closing, and sender name if known.
- For business documents, use short sections with headings and bullets.
- If user did not give all details, make a clean draft with reasonable placeholders instead of blocking.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.