Technical Writing with Diagrams to Word
Articles and reports with real structure, diagrams that teach, captions with takeaways, and one-command .docx export.
$10
Works with the AI Agents you already use
Technical Writing with Diagrams to Word
Example session with this skill installed
Write a technical article on how our ingest pipeline works, with a diagram, and give me a Word file.
- Read your context and instructions
- Compiled the technical writing
A structured article (hook, problem, architecture diagram, deep dive, trade-offs, conclusion) with every figure introduced in the text and captioned with a takeaway, exported to article.docx with the diagram centred and captioned.
Connects securely to your tools. The creator never sees your data.
About this skill
Most AI-written documents fail in the same three ways: generic structure, diagrams
dropped in without explanation, and captions that only label. This skill fixes all three.
The full specification is in references/standards.md. Read it before writing anything
longer than a page.
| Archetype | Structure |
|---|---|
| Technical article | Hook/abstract → problem statement → system architecture (block diagram) → component deep dive → data flow or sequence → trade-offs and performance → conclusion |
| Formal report | Metadata block → executive summary (callout) → scope and methodology → numbered findings with referenced figures → risk matrix → action plan |
| Blog post | Hook → TL;DR box → hero conceptual diagram (within the first 2–3 paragraphs) → walkthrough with code → comparison table → actionable call to action |
| Executive brief | Strategic challenge → solution → one high-impact diagram or ROI table → decision roadmap |
If the user doesn't say which, infer it from the audience and say which one you chose.
- Introduce, then show. The sentence before a visual names it: "As Figure 2 below shows, requests pass through a local filter before reaching the model…" No visual is ever left without that introduction.
- Standalone comprehension. A reader who sees only the diagram and its caption should
get 80% of the idea. Use descriptive node labels with their role (
Event bus (pub/sub router)), neverNode A. - Captions carry the takeaway:
Figure N: Title — one or two sentences stating what to notice.A bareFigure 1: Architectureis not a caption. - Rhythm. Give the reader a visual break every 300–500 words: a diagram, a table, a code block or a callout. Never stack two complex diagrams without text explaining how they relate.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.
Mermaid diagrams must be rendered to PNG first (Mermaid CLI or similar) before they can go into Word. The converter covers common Markdown only: no footnotes, nested tables or raw HTML.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 13 days ago
- Software
Python 3.9+python-docx@mermaid-js/mermaid-cli
- Optional
Node.js
Node.js is only for Mermaid CLI rendering.
Permissions
File Scopes
md_to_docx.py makes no network calls. The optional Mermaid step runs `npx -y @mermaid-js/mermaid-cli`, which downloads that npm package; skip it and Mermaid blocks stay as code with a warning.