SkillsDoc Template Design: Agent Skill
Doc Template Design: Agent Skill
Build client-facing Word documents that look professionally made: a neutral layout, the client's brand measured from their site, or their own template.
Get full access to this skill and the tools to run it
For agents
Your AI gets this skill, your clients' context and the research tools, in Claude or any MCP client.
Connector URL: https://mcp.unilytics.ai/mcp
What you get
A finished Word document in one of three looks: a clean neutral layout, the client's brand (colours and fonts measured from their website, confirmed with you on a preview), or the client's own template. Every document gets the same parts (title, numbered sections, tables, figures, running header and footer), with fonts embedded and checked for how it looks once opened.
Deliverable: Word doc
When to use it
Client-facing Word deliverables that must look on brand, or use the client's own template.
The steps
The skill takes your agent through these steps, in order. Each step's full instructions come with the skill when you run it through Unilytics.
- Who is the document for
- New client theme (probe, propose, preview, confirm, save)
- The client's own template
- Build the document
The full skill also covers: Before you start · Definition of done · Gotchas · Files · Rules for this skill.
Tools it needs, with or without Unilytics
Straight from the skill: the data each step needs and the tools that can supply it. Unilytics is one option, never a requirement.
| Capability | Ways to get it |
|---|---|
| Build the .docx | Python 3 with fonttools and Pillow (pip install fonttools pillow); python-docx only for adopt route 1 |
| Fonts | Google Fonts static files from the npm registry (@expo-google-fonts/<family>), or the google/fonts repository on GitHub |
| Render audit | LibreOffice (headless soffice), poppler (pdftoppm), Python pdfplumber, numpy, Pillow |
| Probe a client's site | A browser tool that runs JavaScript on a page and reads its text: a browser-automation extension or MCP server, Playwright or Puppeteer, or the DevTools console by hand |
| Visual reference of the site | Any screenshot tool, or the Unilytics MCP page_screenshot (an image of the page, not its colour values) |
| Brand guidelines pages | Fetch the page text with any scraper, or the Unilytics MCP content_scrape |
| Schema validation (optional) | An OOXML validator, for example the one in the docx skill |
Without the Unilytics MCP
Every step runs without Unilytics. Without it, what you lose is one connection for several of the capabilities above: each one then comes from the other ways listed for it (a tool or account you already have, a vendor API, or a manual export). The Unilytics MCP is one optional way to get several of these tools in a single connection: https://unilytics.ai
New accounts start with 50 credits. Connecting, and reading your skills, projects and client context, costs nothing; research tools and some writes use credits.