AI Agent Hub
Back to skills
Official Document Format Editor (GB/T 9704-2012) icon

Official Document Format Editor (GB/T 9704-2012)

Office Efficiency Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_ec3a57cf/gbt-9704-2012-skills according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Official .docx documents in government agencies, public institutions, and research organizations often have inconsistent margins, fonts, heading levels, punctuation, signatures, and page numbering. Manual review is error-prone, especially for second-level numbering, separate attachment pages, and letter closings. This skill targets office drafting and formatting workflows, diagnosing common layout issues and correcting them according to GB/T 9704-2012 and practical formatting rules, while avoiding changes to elements that must be preserved, such as letterhead, document numbers, and end matter.

How It Works

The core workflow is diagnose → punctuate → format → review. It first identifies format defects, then fixes mixed Chinese/English punctuation, paragraph-ending periods, list-level semicolons/periods, and protected English apostrophes. It then normalizes page setup, fonts, sizes, line spacing, title wrapping, signature centering, attachment pages, and page numbering. Page numbers are typically cleared and rebuilt: cover and table of contents are unnumbered, body text starts at page 1, and odd/even pages align right/left. Tables receive basic border, width, and alignment optimization, but letterhead tables are not redrawn. For closings such as “此致/敬礼” or “顺颂”, it can correct line breaks and punctuation offline, without drafting new thanks.

Boundaries

The skill only handles .docx; .doc files must be converted first. Typos, colloquial phrasing, and formality issues are reported but not silently rewritten. If an organization has special requirements for end matter, letterhead, seals, or page numbers, those elements must be declared as preserved. Confidential documents should not be sent to internet-connected machines or cloud models and should be processed in an isolated offline environment.

Use Cases

  • After drafting a .docx notice, check margins, fonts, second-level entries, signature, and page numbers against the standard.
  • When letter closings such as “此致敬礼” or “顺颂” are inconsistent, fix line breaks and punctuation offline without rewriting body content.
  • Preserve unit-specific letterhead, document number, and end matter while fixing body punctuation, numbering, pagination, and attachment pages.
  • Process confidential documents on an isolated machine by running offline diagnosis, formatting, and pagination without sending text to online AI.

Best For

  • Government office staff who must review notices and letters against GB/T 9704-2012 formatting and signature rules.
  • Public institution clerks who need to preserve unit letterhead and end matter while fixing body punctuation, hierarchy, and page numbers.
  • Researchers who want to standardize journal names, paper counts, punctuation, and attachment pages in official documents.
  • IT staff who deploy offline Python tooling on isolated machines to format confidential documents.