Introduction¶
In daily document submissions, formatting issues are often more frustrating than content issues: body text within the same document may use two different font sizes, heading hierarchies are cobbled together manually via bolding and enlargement, and margins or line spacings are the result of endless revisions by colleagues. Official documents and Word documents have stricter standards; paragraph-by-paragraph alignment is pure manual labor, and after making changes, one must read through the entire document to ensure the layout hasn’t shifted.
The Skill introduced below hands over this type of layout work—“unifying fonts and paragraphs, standardizing heading hierarchies”—to the model to complete in one go, eliminating the need for manual adjustments paragraph by paragraph.
What is this?¶
“Document Formatting & Beautification” is a general-purpose Skill designed for document layout. Its coordinates are @kunlungrowth/doc-format-polish, version 1.0.0. It is published by “Kunlun Growth,” with a source tag of enterprise and categorized under office-efficiency.
In a nutshell: It organizes document fonts, paragraphs, and heading hierarchies according to unified rules, standardizing the layout of official documents and Word files to produce a professional and clean final product.
It belongs to the general-purpose SKILL.md format. It functions in the stage of “receiving document—re-arranging according to standards—outputting final product” and does not rewrite content.
Core Functions¶
According to the official description, there are three verifiable capabilities:
- Unify Fonts and Paragraphs: Converge scattered and inconsistent body text fonts, sizes, line spacings, and paragraph spacings into a single set of rules.
- Standardize Heading Hierarchies: Ensure consistency in numbering, font size, and spacing for headings at all levels, making hierarchical relationships immediately clear.
- Standardize Official Document and Word Layout: Perform unified processing tailored to the layout requirements of official documents and Word documents.
It should be noted that the official description does not list detailed parameter items (such as specific font size values, line spacing values, or margins), nor does it provide behavioral descriptions regarding whether to preserve original comments, revisions, or table of contents fields. These details need to be confirmed by running a sample test before use.
Installation and Activation¶
Official documentation does not provide a standalone installation command, nor does it specify if an API Key is required (the tag indicates requires_api_key=false). For Skills based on SKILL.md, the general practice is to place the Skill directory into the client’s skills directory or add it via a Skill Marketplace (SkillHub).
Taking Cursor / Claude Code / Codex CLI as examples, if local Skill directories are supported, you can import them as follows:
mkdir -p ~/.cursor/skills
cp -r doc-format-polish ~/.cursor/skills/
mkdir -p ~/.claude/skills
cp -r doc-format-polish ~/.claude/skills/
mkdir -p ~/.codex/skills
cp -r doc-format-polish ~/.codex/skills/
The commands above merely place the Skill directory into the corresponding client’s skills directory; actual support depends on the current version of each client. If using SkillHub, simply add it from the skill page and you can invoke it by entering the coordinates @kunlungrowth/doc-format-polish.
Typical Usage¶
Provide the path to the document requiring formatting to the Skill, specify the target style, and let it re-arrange the document according to standards and save it as a new file. Example workflow:
- Prepare Document: Place the
.docxor Markdown file to be formatted in the working directory. - Specify Target Style: Clarify whether the formatting should follow official document standards or general Word standards to avoid the Skill guessing.
- Execute Formatting: Have the Skill unify fonts, paragraphs, and heading hierarchies.
- Review and Output: Check heading hierarchies and paragraph spacing, then save as a new file without overwriting the original.
On the command line side, you can load the skill using the client’s standard invocation method:
# Example: Invoking in a client that supports the skills parameter
# skill: @kunlungrowth/doc-format-polish
# input: <Document Path>
# style: Official Document Standards
The purpose of this step is to clarify the input file and target style, clearly communicating the formatting rules in one go.
Use Cases and Caveats¶
Suitable Scenarios:
- Internal materials, report documents, or first drafts of official documents that need to quickly converge to a unified layout.
- Documents resulting from multi-person collaboration where fonts and paragraphs are inconsistent and need unification.
- Documents exported from other editors where heading hierarchies and paragraph spacing need standardization.
Limitations to Note:
- Content: It only handles layout; it is not responsible for content polishing or fact-checking. Content issues still require manual review.
- Complex Elements: The behavior regarding the layout of tables, images, formulas, headers, and footers is not described in the official introduction. Please verify with small samples first.
- Strict Standards: Official document layouts have mandatory requirements for issuing authority marks, document numbers, and date of formulation. If your organization has internal templates, confirm whether the Skill’s rules match the template before deciding to apply it directly.
- Safety: It is recommended to execute on a copy and replace the original only after confirming the effect.
Conclusion¶
Repetitive labor such as ensuring layout consistency is better handled by a Skill than manual paragraph-by-paragraph adjustments, saving time and reducing errors. Its value lies in converging fonts, paragraphs, and heading hierarchies into a single set of rules, making it particularly practical for official documents and Word documents.
Official URL: https://api.skillhub.cn/kunlungrowth/doc-format-polish
SkillHub Page: https://www.skillhub.cn/skills/kunlungrowth/doc-format-polish