Skip to content
Agentmart
Submit a tool

document-design

Produce a formal .docx with the docx library — named styles, heading hierarchy, page furniture — verified by reading it back

Skill by briant92

IndexedApache-2.0
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/briant92-document-design

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Produce a formal .docx with the docx library — named styles, heading hierarchy, page furniture — verified by reading it back

Use cases: documents, design

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/document-design

What's inside

Skill name
document-design
Description
Produce a formal .docx with the docx library — named styles, heading hierarchy, page furniture — verified by reading it back
License
Apache-2.0
Instructions
23 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Document design

A formal Word file is structure the reader's own tools can use — styles,
not decorated runs. Output lands at the **sandbox root** (a subfolder file
is invisible to review).

1. **Styles, never inline formatting.** Define heading and body styles once
   on the `Document` and reference them; a bolded large run is not a
   heading — it breaks navigation, numbering and the reader's theme.
2. **Hierarchy holds.** Heading 1 → 2 → 3 with no skips; the title is the
   title, not a Heading 1. A document over ~3 pages gets a table of
   contents built from those headings.
3. **Page furniture.** Header with the document's name, footer with the
   page number, real margins. A formal document that starts at the page
   edge reads as a draft.
4. **Tables carry data.** Real column widths (never all-equal by default),
   a header row that repeats, alignment by content — numbers right, words
   left. No tables as layout scaffolding.
5. **Read it back.** After `Packer.toBuffer`, extract with mammoth and
   quote in your result: word count, the heading outline as extracted, and
   bytes. If what mammoth returns disagrees with what you meant to write,
   the file is wrong, not the check.

From briant92/Agentlings, Apache-2.0.

More from briant92/Agentlings

Signals

Stars
0
Forks
0
Open issues
6
Last commit (this folder)
Aug 9, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from briant92

Cite this page

document-design skill. Agent Mart. https://agentmart.dev/skills/briant92-document-design (last updated 2026-10-24)