# Aos Publish Document

> Coordinate end-to-end professional document publishing across editable Word and fixed PDF deliverables. Use when Codex needs to turn source materials into publication-ready reports, white papers, proposals, manuals, brand books, or other business documents through content planning, DOCX authoring, PDF conversion, metadata review, and page-by-page visual QA. Prefer this orchestration skill when th…

- **Type:** Skill
- **Install:** `agentstack add skill-axutse-aos-agent-skill-document-aos-publish-document`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [axutse](https://agentstack.voostack.com/s/axutse)
- **Installs:** 0
- **Category:** [Content & Media](https://agentstack.voostack.com/c/content-and-media)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [axutse](https://github.com/axutse)
- **Source:** https://github.com/axutse/aos-agent-skill-document/tree/main/plugins/aos-agent-skill-document/skills/aos-publish-document
- **Website:** https://github.com/axutse/aos-agent-skill-document

## Install

```sh
agentstack add skill-axutse-aos-agent-skill-document-aos-publish-document
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# AOS Document Publishing

Produce polished documents through a deterministic `plan -> author -> render -> inspect -> revise -> verify` loop.

Match the user's requested language. When the user requests Chinese and English editions, read [references/bilingual-delivery.md](references/bilingual-delivery.md) and verify each language artifact independently.

## Position the work

Act as a document publishing orchestrator, not as a replacement for Word, Acrobat, factual review, legal review, or rights clearance. Combine Codex reasoning with local document tools, preserve editability where required, and treat rendered-page verification as part of the deliverable rather than an optional preview.

Read [references/positioning-and-routing.md](references/positioning-and-routing.md) when selecting among the three AOS skills, explaining scope to the user, or defining the input and output contract.

## Route the work

- Use `$aos-author-word` when editability, semantic styles, tracked document structure, or DOCX delivery matters.
- Use `$aos-process-pdf` for fixed-layout creation, PDF inspection, metadata checks, rendering, page operations, or print-ready verification.
- Use both when the user requests DOCX and PDF: author the DOCX first, verify it, export the PDF, and verify the PDF again.
- Do not invoke all three skills mechanically. Use this skill as the orchestration entry point and load the format-specific workflow only when the task requires it.

## Required workflow

1. Inspect all supplied sources before drafting.
2. Confirm format, page size, language, editability, style, and delivery requirements from context.
3. Build a section and page plan for long documents.
4. Preserve verified names, figures, terminology, and source meaning. Mark simulated values clearly.
5. Apply a coherent editorial system. Read [references/editorial-design.md](references/editorial-design.md) for premium reports and white papers.
6. Render the complete final document.
7. Inspect every page at readable zoom; a contact sheet is only an overview.
8. Fix clipping, overlaps, broken tables, missing glyphs, blurry images, weak hierarchy, and incorrect headers or footers.
9. Re-render after each layout-sensitive change.
10. Run metadata and secret checks before public release.
11. Deliver only requested final artifacts unless QA outputs are requested.

## Editorial defaults

- Use conclusion-first titles and one dominant idea per page.
- Keep type, spacing, grid, table geometry, and accent colors consistent.
- Prefer native text and tables over screenshots when content must remain crisp or editable.
- Label simulated data as `PLANNING ASSUMPTION / 企划模拟值`.
- Never redistribute font files, credentials, private records, or unapproved third-party source documents.
- Use [assets/apple-editorial.json](assets/apple-editorial.json) as the default style pack when the user asks for an Apple-inspired editorial treatment.

## Final gate

Read [references/qa-checklist.md](references/qa-checklist.md) and approve the artifact only after all applicable content, layout, image, table, navigation, metadata, and PDF checks pass.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [axutse](https://github.com/axutse)
- **Source:** [axutse/aos-agent-skill-document](https://github.com/axutse/aos-agent-skill-document)
- **License:** MIT
- **Homepage:** https://github.com/axutse/aos-agent-skill-document

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-axutse-aos-agent-skill-document-aos-publish-document
- Seller: https://agentstack.voostack.com/s/axutse
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.