Doc
Install when your agent must read, create, or edit .docx files without wrecking Word formatting and layout.
Overview
doc is an agent skill for the Build phase that routes agents to OpenAI’s document skill for high-fidelity .docx read, create, and edit workflows.
Install
npx skills add https://github.com/nexu-io/open-design --skill docWhat is this skill?
- Read, create, and edit .docx with formatting and layout fidelity via OpenAI’s upstream document skill
- Catalog entry in Open Design so agents discover the capability during planning
- Trigger phrases: openai doc, docx fidelity, word doc edit, layout doc
- Points to the full upstream bundle on github.com/openai/skills for scripts and references
- Prototype-mode documents category curated from OpenAI’s skills repository
Adoption & trust: 808 installs on skills.sh; 61.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need Word-compatible documents from an agent but generic text output breaks styles, tables, and layout your client expects.
Who is it for?
Solo builders who must deliver or iterate on .docx files and want a named skill trigger plus a clear path to OpenAI’s full document toolchain.
Skip if: Teams that only work in Markdown or Google Docs with no .docx requirement, or anyone expecting the full upstream scripts to ship inside this catalog stub alone.
When should I use this skill?
User mentions openai doc, docx fidelity, word doc edit, layout doc, or needs .docx read/create/edit with layout fidelity.
What do I get? / Deliverables
Your agent discovers the doc skill during planning and, after you install the upstream OpenAI bundle, can run layout-faithful .docx workflows instead of improvising broken exports.
- Edited or newly created .docx files with preserved formatting
- Agent plan that references the upstream document workflow
Recommended Skills
Journey fit
Document authoring and revision happen while you are building specs, contracts, and deliverables—not only at launch. The docs subphase is where solo builders produce and maintain structured written artifacts like Word documents alongside the product.
How it compares
Use as a discovery and install pointer to OpenAI’s document skill—not as a self-contained in-repo Markdown-to-DOCX generator.
Common Questions / FAQ
Who is doc for?
Solo and indie builders using Claude Code, Cursor, Codex, or similar agents who regularly touch .docx deliverables and want catalog-visible triggers for layout-faithful document work.
When should I use doc?
Use it during Build (docs) when you are drafting or revising Word documents, client packs, or formatted specs; invoke by name or phrases like docx fidelity and word doc edit after installing the upstream OpenAI skills bundle.
Is doc safe to install?
This entry is a safe curated pointer with prototype document mode; review the Security Audits panel on this Prism page and inspect github.com/openai/skills before installing the upstream bundle in your agent environment.
SKILL.md
READMESKILL.md - Doc
# doc > Curated from OpenAI's skills repository. ## What it does Read, create, and edit .docx documents with formatting and layout fidelity via OpenAI's document skill. ## Source - Upstream: https://github.com/openai/skills - Category: `documents` ## How to use This catalogue entry advertises the skill in Open Design so the agent discovers it during planning. To run the full upstream workflow with its original assets, scripts, and references, install the upstream bundle into your active agent's skills directory: ```bash # Inspect the upstream README for exact paths open https://github.com/openai/skills ``` Then ask the agent to invoke this skill by name (`doc`) or with one of the trigger phrases listed in this skill's frontmatter.