{"id":"eb2129b2-f272-448b-8cc1-df1444c8857a","entityType":"agent","slug":"clawhub-wing-art-format-official-docx","name":"党政公文格式化","canonicalUrl":"https://www.xpersona.co/agent/clawhub-wing-art-format-official-docx","canonicalPath":"/agent/clawhub-wing-art-format-official-docx","generatedAt":"2026-10-11T14:14:53.531Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T09:44:28.436Z","emptyReason":null},"description":"将文字或 Word 转为规范党政机关公文格式 Skill: 党政公文格式化 Owner: wing-art Summary: 将文字或 Word 转为规范党政机关公文格式 Tags: latest:1.0.2 Version history: v1.0.2 | 2026-07-09T08:31:26.327Z | user - Removed the sample file skill-card.md. - No changes to features or behavior; documentation updated and streamlined in SKILL.md. - All functionality remains as previously described. v1.0.1 | 2026-07-09T06:55:14.720Z | user - Added skill documentation (README.md) and metadata fil","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s179t0n7qy7rwex3mw410r5yj185eah7:format-official-docx","sourceUrl":"https://clawhub.ai/wing-art/format-official-docx","homepage":"https://clawhub.ai/wing-art/skills/format-official-docx","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/wing-art/format-official-docx","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/wing-art/skills/format-official-docx","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"将文字或 Word 转为规范党政机关公文格式 Skill: 党政公文格式化 Owner: wing-art Summary: 将文字或 Word 转为规范党政机关公文格式 Tags: latest:1.0.2 Version history: v1.0.2 | 2026-07-09T08:31:26.327Z | us"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T09:44:28.436Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T09:44:28.436Z","emptyReason":null},"stars":null,"forks":null,"downloads":1096,"packageName":null,"latestVersion":"1.0.2","tractionLabel":"1.1K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T09:44:28.430Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T09:44:28.436Z","lastCrawledAt":"2026-10-11T09:44:28.430Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T09:44:28.430Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.2","createdAt":"2026-07-09T08:31:26.327Z","changelog":"- Removed the sample file skill-card.md. - No changes to features or behavior; documentation updated and streamlined in SKILL.md. - All functionality remains as previously described.","fileCount":11,"zipByteSize":19097},{"version":"1.0.1","createdAt":"2026-07-09T06:55:14.720Z","changelog":"- Added skill documentation (README.md) and metadata file. - Updated documentation to clarify preserved formatting in format-only mode: now explicitly preserves tables and styles them per official font rules. - Expanded feature list in the description: now highlights support for red headers, 发文字号/签发人, secret level markings, 主送机关 colon auto-fill, date auto-fill, attachment notes/markers, proper issuer/date placement, page numbers, font-missing warnings, and a checker script. - Added new command-line options documentation, including support for secret-level marking, --date today, and table preservation. - Improved guidance on official document formatting details and output checks.","fileCount":11,"zipByteSize":19074},{"version":"1.0.0","createdAt":"2026-07-07T22:46:04.978Z","changelog":"- Initial release: generates or reformats Word (.docx) documents to Chinese PRC party/government official document standards. - Supports format-only and generated shell workflows for official document types (请示、函、报告、通知等). - Applies specific fonts, red headers, government margins, and layout rules per national and local formatting standards (GB/T 9704 and local overrides). - Does not modify substantive wording unless asked; uses placeholders for missing metadata. - Provides example commands for generating, formatting, and quality-checking documents via scripts. - Requires python-docx and related scripts; checks for correctness of key formal elements (fonts, headers, numbers, etc.).","fileCount":10,"zipByteSize":14212}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s179t0n7qy7rwex3mw410r5yj185eah7:format-official-docx","setupComplexity":"low","setupSteps":["Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T14:14:53.530Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-wing-art-format-official-docx/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T09:44:28.436Z","emptyReason":null},"readme":"Skill: 党政公文格式化\n\nOwner: wing-art\n\nSummary: 将文字或 Word 转为规范党政机关公文格式\n\nTags: latest:1.0.2\n\nVersion history:\n\nv1.0.2 | 2026-07-09T08:31:26.327Z | user\n\n- Removed the sample file skill-card.md.\n- No changes to features or behavior; documentation updated and streamlined in SKILL.md.\n- All functionality remains as previously described.\n\nv1.0.1 | 2026-07-09T06:55:14.720Z | user\n\n- Added skill documentation (README.md) and metadata file.\n- Updated documentation to clarify preserved formatting in format-only mode: now explicitly preserves tables and styles them per official font rules.\n- Expanded feature list in the description: now highlights support for red headers, 发文字号/签发人, secret level markings, 主送机关 colon auto-fill, date auto-fill, attachment notes/markers, proper issuer/date placement, page numbers, font-missing warnings, and a checker script.\n- Added new command-line options documentation, including support for secret-level marking, --date today, and table preservation.\n- Improved guidance on official document formatting details and output checks.\n\nv1.0.0 | 2026-07-07T22:46:04.978Z | auto\n\n- Initial release: generates or reformats Word (.docx) documents to Chinese PRC party/government official document standards.\n- Supports format-only and generated shell workflows for official document types (请示、函、报告、通知等).\n- Applies specific fonts, red headers, government margins, and layout rules per national and local formatting standards (GB/T 9704 and local overrides).\n- Does not modify substantive wording unless asked; uses placeholders for missing metadata.\n- Provides example commands for generating, formatting, and quality-checking documents via scripts.\n- Requires python-docx and related scripts; checks for correctness of key formal elements (fonts, headers, numbers, etc.).\n\nArchive index:\n\nArchive v1.0.2: 11 files, 19097 bytes\n\nFiles: _meta.json (139b), agents/openai.yaml (246b), README.md (3467b), references/document-types.md (972b), references/format-rules.md (3131b), requirements.txt (19b), scripts/check_fonts.py (1840b), scripts/check_official_docx.py (6478b), scripts/generate_official_docx.py (21646b), skill-card.md (2444b), SKILL.md (4164b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: format-official-docx\ndescription: 将粘贴的中文文本或现有 .docx 文档，转换为符合党政机关公文格式规范的 Word 文档。支持函、请示、报告、通知、批复、意见、纪要、上行文等文种。功能包括红头、发文字号/签发人、密级标注（密级★期限）、主送机关自动补全冒号、--date today 自动填日期、附件说明与附件首页“附件N”标识、发文机关署名居中且成文日期右空四字、版记落偶数页、页码、字体缺失告警，以及保留表格的重排（format-only）模式。附带格式校验脚本。\n---\n\n# 党政公文格式化\n\n生成规范的 .docx 文件；不要只给建议而不实际生成。\n\n## 快速流程\n\n1. 判断意图：\n - `format-only`（仅重排）：保留段落文字与顺序，只调整版式与样式。\n - `generate`（生成）：创建公文外壳并撰写简洁正文。\n2. 选择文种。若不明确，参考 `references/document-types.md`；否则不必加载。\n3. 版式细则参考 `references/format-rules.md`。本地细则优先于通用 GB/T 9704 知识。\n4. 用 `scripts/generate_official_docx.py` 生成。\n5. 正式公文（请示/函/报告）生成后，尽量运行 `scripts/check_official_docx.py` 做格式校验。\n6. 最终文件保存到 `outputs/`。\n\n前置依赖：`python-docx`；若缺失请用 `pip install -r requirements.txt` 安装。\n\n## 核心规则\n\n- 除非用户要求起草或修改，否则保留原文实质内容。\n- 不要臆造缺失的元数据；应询问用户，或使用 `XXXX` 等占位符。\n- 标题/红头使用方正小标宋简体，正文使用仿宋_GB2312，一级标题使用黑体，二级标题使用楷体_GB2312，数字及拉丁文字使用 Times New Roman。\n- 严格的 format-only 模式不得新增结尾、署名、附件或元数据。\n- 现有 .docx 的 format-only 重排会保留段落文字与表格（重新套用正文规范字体）；不保留图片、批注、修订痕迹、文本框、复杂页眉。\n\n## 常用命令\n\n生成请示：\n\n```bash\npython scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type request --red-header \"某单位文件\" --outgoing-no \"某字〔XXXX〕XX号\" --signer \"XXX\" --title \"某单位\\n关于XXXX的请示\" --recipient \"某上级机关：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --add-closing\n```\n\n生成函：\n\n```bash\npython scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type letter --letterhead \"某单位\" --outgoing-no \"某字〔XXXX〕XX号\" --title \"关于XXXX的函\" --recipient \"某单位：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --no-page-number\n```\n\n仅重排：\n\n```bash\npython scripts/generate_official_docx.py --input source.docx --output formatted.docx --doc-type generic --format-only --promote-first-paragraph-title\n```\n\n格式校验：\n\n```bash\npython scripts/check_official_docx.py out.docx --doc-type request\npython scripts/check_fonts.py\n```\n\n## 关键参数\n\n- `--doc-type`：文种，`generic` / `request` / `report` / `letter` / `notice`\n- `--format-only`：仅重排模式\n- `--red-header`：请示/上行文的红色“发文机关名称+文件”红头\n- `--letterhead`：函的红色机关头\n- `--letter-special-margins`：仅在明确要求时使用本地函首页页边距（上 5.1 / 下 2.1）\n- `--outgoing-no`、`--signer`、`--title`、`--recipient`、`--issuer`、`--date`、`--contact`\n- `--attachment`、`--copy-to`、`--print-org`、`--print-date`、`--disclosure-note`\n- `--secret-level`：左上角三号黑体密级行，如 `秘密★1年`\n- `--add-closing`：仅在缺失时补充标准请示/报告结尾\n- `--date today`：自动填入当前日期（也接受 `XXXX年XX月XX日`）\n- `--bold-headings`：一级（黑体）标题加粗；默认关闭，遵循三号黑体不加粗规范\n\n## 最终检查\n\n检查标题/红头字体、页边距、行距、首行缩进、标题发文机关行、发文字号/签发人、右对齐的署名与日期、联系人/披露说明、页码、版记。若本机未安装方正小标宋简体或仿宋_GB2312，Word 会替换字体。\n\nFile v1.0.2:README.md\n\n# format-official-docx（党政公文格式化）\n\n将纯文本或现有 Word 文档，按党政机关公文格式规范，生成/重排为规范的 `.docx`。\n支持 **请示、报告、函、通知、批复、意见、纪要** 等文种，以及密级标注、红头、附件、版记、页码等要素。\n\n> 本技能默认遵循「三号仿宋_GB2312 正文、方正小标宋简体标题、版记落偶数页」等常见规范；\n> 具体以你单位印发的格式细则为准。文中示例均使用 `某单位` 等占位名称，请按实际替换。\n\n## 特性\n\n- 生成（generate）与重排（format-only）两种工作流\n- 文种：请示 / 报告 / 函 / 通知，校验亦支持 批复 / 意见 / 纪要\n- 红头（发文机关+文件）、发文字号、签发人、密级（左上角 三号黑体 `密级★期限`）\n- 主送机关自动补全中文冒号；成文日期支持 `--date today` 自动填\n- 附件说明（首行缩进）+ 附件首页「附件N」标识\n- 发文机关署名居中、成文日期右空四字\n- 版记（抄送 / 印发机关 / 印发日期）强制落偶数页\n- 字体缺失时主动告警（避免 Word 静默替换导致排版漂移）\n- `--bold-headings` 可选：一级黑体标题加粗\n\n## 安装\n\n```bash\npip install -r requirements.txt\n```\n\n依赖：`python-docx>=1.2.0`。\n\n## 快速开始\n\n生成一份请示：\n\n```bash\npython scripts/generate_official_docx.py \\\n --input body.txt --output out.docx --doc-type request \\\n --red-header \"某单位文件\" --outgoing-no \"某字〔2026〕1号\" --signer \"XXX\" \\\n --title \"某单位\\n关于某事项的请示\" --recipient \"某上级机关\" \\\n --issuer \"某单位\" --date today --add-closing \\\n --attachment \"关于某事项的说明\" --copy-to \"某机关\" \\\n --print-org \"某办公室\" --print-date \"2026年7月9日\" \\\n --contact \"(联系人：XXX，联系方式：XXXXXXXX)\" --secret-level \"秘密★1年\"\n```\n\n将已有 `.docx` 重排为规范格式（**保留表格**）：\n\n```bash\npython scripts/generate_official_docx.py \\\n --input source.docx --output formatted.docx --doc-type generic \\\n --format-only --promote-first-paragraph-title\n```\n\n校验格式信号：\n\n```bash\npython scripts/check_official_docx.py out.docx --doc-type request\npython scripts/check_fonts.py\n```\n\n## 常用参数\n\n| 参数 | 说明 |\n|---|---|\n| `--doc-type` | `generic` / `request` / `report` / `letter` / `notice` |\n| `--format-only` | 仅改版式与字体，不新增结尾、署名、附件等要素 |\n| `--red-header` | 请示/上行文红头，如 `某单位文件` |\n| `--letterhead` | 函的红头机关名称 |\n| `--secret-level` | 左上角密级，如 `秘密★1年` |\n| `--attachment` | 可多次，附件名称 |\n| `--copy-to` | 抄送机关 |\n| `--print-org` / `--print-date` | 印发机关 / 印发日期 |\n| `--date today` | 自动填入当前日期 |\n| `--add-closing` | 请示/报告自动补结尾（仅在缺失时） |\n| `--bold-headings` | 一级黑体标题加粗（默认不加粗） |\n\n## 字体说明\n\n生成脚本写入的字体名为规范名称：`方正小标宋简体`、`仿宋_GB2312`、`楷体_GB2312`、\n`黑体`、`宋体`、`Times New Roman`。若本机未安装对应字体，Word 打开时会替换渲染，\n脚本会在生成时向 stderr 告警。装好字体即可获得与打印一致的规范排版。\n\n## 文种速查\n\n详见 `references/document-types.md`；版式细则见 `references/format-rules.md`。\n\n## License\n\nMIT-0\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn78ykfdjrjqt3k7qfhmj66ef585ekjt\",\n \"slug\": \"format-official-docx\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1783585886327\n}\n\nFile v1.0.2:references/document-types.md\n\n# 公文文种选择速查\n\n仅在用户未明确文种时使用。\n\n- 请示：向上级请求批准或指示；一事一请；结尾用 `妥否，请批示。`\n- 报告：向上级汇报工作、情况或结果；不提批准请求；补全结构时以 `特此报告。` 结尾。\n- 函：不相隶属机关之间商洽、询问、请求协助、答复或反馈意见；无意见答复通常用函。\n- 通知：布置工作、转发文件、公布事项、要求执行。\n- 批复：上级答复下级请示。\n- 意见：提出指导意见、实施办法、政策或工作建议。\n- 纪要：会议记录，含议定事项、参会单位、后续跟进。\n\n判断参考：\n\n- 用户明确说请示/函/报告，从其意。\n- “征求意见/无意见/函复” → 通常为函。\n- “请批准/请审定/提请研究” → 通常为请示。\n- “汇报/报送情况/说明进展” → 通常为报告。\n- “请各单位落实/转发” → 通常为通知。\n\nFile v1.0.2:references/format-rules.md\n\n# 党政机关公文格式规则\n\n本规则提炼自本地公文格式规范。若与通用 GB/T 9704 知识冲突，以本规则为准。\n\n## 页面\n\n- 用 A4 纸；标准页边距：上 3.7 厘米、下 3.5 厘米、左 2.8 厘米、右 2.6 厘米。\n- 部分本地函模板首页用上 5.1 厘米、下 2.1 厘米；仅在明确要求时使用。\n- 固定行距 28.9 磅。默认文字颜色为黑色。\n- 双面打印，左侧装订。\n\n## 字体\n\n- 红头 / 主标题：方正小标宋简体。\n- 主标题：二号，居中。\n- 正文：三号仿宋_GB2312；数字及拉丁文字用 Times New Roman。\n- 一级标题（一、）：三号黑体。\n- 二级标题（（一））：三号楷体_GB2312。\n- 三级/四级标题（1． / （1））：三号仿宋_GB2312。\n- 页码：四号宋体，格式为 — 1 —。\n- 版记：四号仿宋_GB2312。\n\n## 函\n\n正式函应包含：\n\n- 红色机关头，如 `某单位`，用大号红色方正小标宋简体。\n- 机关头下方红色分隔线。\n- 分隔线下方为发文字号，通常右对齐，如 `某字〔XXXX〕XX号`。\n- 文种标题在文号下方居中。\n- 正式标题通常包含发文机关行与事由行。\n- 主送机关以 `：` 结尾。\n- 正文简洁；复函/无意见函可用：“贵单位关于征求某事项意见的来函收悉。经研究，我单位无意见。特此函复。”\n- 署名/日期右对齐并留出适当右空；可加联系人行与披露说明，如 `（此件不公开）`。\n- 使用套印红头纸时，底部加红色结束线。\n\n## 请示 / 上行文\n\n正式请示/上行文应包含：\n\n- 红色“发文机关名称+文件”红头，如 `某单位文件`，方正小标宋简体。\n- 发文字号居左、签发人居右，同处一行；下方红色分隔线。\n- 标题通常分为发文机关行与事由行。\n- 主送机关以 `：` 结尾。\n- 正文以 `妥否，请批示。` 结尾，除非用户禁止或正文已含此句。\n- 署名与日期保持在一起。\n- 多页/上行文加页码。\n- 版记落偶数页：含印发机关与日期，并加分隔线。\n\n## 报告\n\n- 含标题、主送机关、正文、署名/日期。\n- 仅在补全结构且正文缺失时，以 `特此报告。` 结尾。\n- 上行报告可在日期下方加联系人行。\n\n## 附件\n\n- 正文之后空一行。\n- 单个附件：`附件：XXX`。\n- 多个附件：`附件：1．XXX`，换行后 ` 2．XXX`。\n- 附件名换行时与名称首字对齐。\n- 每个附件首页左上角以三号仿宋_GB2312 标注 `附件1` / `附件2`。\n\n## 署名 / 日期 / 版记\n\n- 署名/日期前空约三行。\n- 发文机关署名居中排版；成文日期右空四字（右对齐，右边距留约 2.26 厘米）。\n- 署名与日期保持在一起；不要用“此页无正文”。\n- 版记含抄送、印发机关、印发日期；抄送单位以 `。` 结尾。\n- 主送/抄送标点：同一系统用 `、`；不同系统用 `，`。\n\n## 文字规范\n\n- 使用规范标点：《》、嵌套〈〉、〔〕；不要用 `< >` 代替 `〈〉`。\n- 涉密文件：左上角三号黑体标注 `密级★保密期限`。\n\nFile v1.0.2:skill-card.md\n\n## Description:\n\n将纯文本或现有 Word 文档按党政机关公文格式规范生成或重排为 .docx，支持常见公文文种、红头、密级、附件、版记、页码和格式校验。\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[wing-art](https://clawhub.ai/user/wing-art)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, external users, and document-preparation agents use this skill to generate or reformat Chinese Party/government official Word documents. It helps preserve source content in format-only workflows while applying document layout, font, heading, recipient, attachment, pagination, and validation conventions.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The python-docx dependency is specified with an open lower-bound version, which can allow supply-chain or compatibility drift.\n\nMitigation: Install dependencies in a virtual environment and pin or lockfile-verify python-docx before use in sensitive environments.\n\nRisk: Generated documents may include user-provided confidential markings or sensitive document content and are written to the selected output path.\n\nMitigation: Review the output path and handle generated DOCX files according to the source document's confidentiality requirements.\n\nRisk: Format-only conversion does not preserve images, comments, tracked changes, text boxes, or complex headers.\n\nMitigation: Keep the original document and manually review the generated DOCX when those elements matter.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/wing-art/skills/format-official-docx)\n- [README](README.md)\n- [公文文种选择速查](references/document-types.md)\n- [党政机关公文格式规则](references/format-rules.md)\n\n## Skill Output:\n\n**Output Type(s):** [Files, Text, Shell commands, Guidance]\n\n**Output Format:** [DOCX files with optional plain-text or JSON validation output]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Writes generated documents to the selected output path; installed fonts can affect final Word rendering.]\n\n## Skill Version(s):\n\n1.0.2 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nFile v1.0.2:agents/openai.yaml\n\ninterface:\n display_name: \"党政公文格式化\"\n short_description: \"将文字或 Word 转为规范党政机关公文格式\"\n default_prompt: \"Use $format-official-docx to convert this text into a properly formatted official Word document.\"\n\nFile v1.0.2:requirements.txt\n\npython-docx>=1.2.0\n\nArchive v1.0.1: 11 files, 19074 bytes\n\nFiles: _meta.json (139b), agents/openai.yaml (246b), README.md (3467b), references/document-types.md (980b), references/format-rules.md (3261b), requirements.txt (19b), scripts/check_fonts.py (1840b), scripts/check_official_docx.py (6478b), scripts/generate_official_docx.py (21646b), skill-card.md (2410b), SKILL.md (4077b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: format-official-docx\ndescription: Convert pasted Chinese text or existing .docx into a Word document formatted as a PRC Party/government official document. Covers 函、请示、报告、通知、批复、意见、纪要、上行文. Features red headers, 发文字号/签发人, secret level (密级★期限), 主送机关 colon auto-fill, --date today, attachment notes plus 附件N markers, centered issuer / right-indented date, even-page 版记, page numbers, font-missing warnings, and format-only retypesetting that preserves tables. Includes a checker script.\n---\n\n# Format Official Docx\n\nProduce a formatted `.docx`; do not answer with advice only.\n\n## Fast Workflow\n\n1. Classify intent:\n - `format-only`: preserve paragraph text/order; change layout/styles only.\n - `generate`: create the official document shell and concise body.\n2. Choose 文种. If unclear, use `references/document-types.md`; otherwise do not load it.\n3. For formal layout details, use `references/format-rules.md`. Local rules override generic GB/T 9704 knowledge.\n4. Generate with `scripts/generate_official_docx.py`.\n5. Run `scripts/check_official_docx.py` for formal 请示/函/报告 when practical.\n6. Save final user files to `outputs/`.\n\nPrerequisite: `python-docx`; install with `pip install -r requirements.txt` if missing.\n\n## Core Rules\n\n- Preserve substantive wording unless the user asks for drafting/revision.\n- Do not invent missing metadata; ask or use placeholders like `XXXX`.\n- Use 方正小标宋简体 for title/red header, 仿宋_GB2312 for body, 黑体 for first-level headings, 楷体_GB2312 for second-level headings, Times New Roman for numbers/Latin text.\n- Strict format-only mode must not add closings, signatures, attachments, or metadata.\n- Existing `.docx` format-only reformatting preserves paragraph text and tables (restyled to the official body font); it does not preserve images/comments/tracked changes/text boxes/complex headers.\n\n## Common Commands\n\nGenerate 请示:\n\n```bash\npython scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type request --red-header \"某单位文件\" --outgoing-no \"某字〔XXXX〕XX号\" --signer \"XXX\" --title \"某单位\\n关于XXXX的请示\" --recipient \"某上级机关：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --add-closing\n```\n\nGenerate 函:\n\n```bash\npython scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type letter --letterhead \"某单位\" --outgoing-no \"某字〔XXXX〕XX号\" --title \"关于XXXX的函\" --recipient \"某单位：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --no-page-number\n```\n\nFormat only:\n\n```bash\npython scripts/generate_official_docx.py --input source.docx --output formatted.docx --doc-type generic --format-only --promote-first-paragraph-title\n```\n\nQuality checks:\n\n```bash\npython scripts/check_official_docx.py out.docx --doc-type request\npython scripts/check_fonts.py\n```\n\n## Key Options\n\n- `--doc-type`: `generic`, `request`, `report`, `letter`, `notice`\n- `--format-only`\n- `--red-header`: red `发文机关名称+文件` header for 请示/上行文\n- `--letterhead`: red agency header for 函\n- `--letter-special-margins`: use local 函 first-page margins 5.1/2.1 only when requested\n- `--outgoing-no`, `--signer`, `--title`, `--recipient`, `--issuer`, `--date`, `--contact`\n- `--attachment`, `--copy-to`, `--print-org`, `--print-date`, `--disclosure-note`\n- `--secret-level`: top-left 三号黑体 secret line, e.g. `秘密★1年`\n- `--add-closing`: adds standard 请示/报告 closing only if absent\n- `--date today`: auto-fill current date (also accepts `XXXX年XX月XX日`)\n- `--bold-headings`: bold level-1 (黑体) headings; off by default to match the 三号黑体 (no bold) convention\n\n## Final Inspection\n\nCheck title/red-header font, margins, line spacing, first-line indents, title issuing-agency line, 发文字号/签发人, right-aligned signature/date, contact/disclosure notes, page numbers, and 版记. Word may substitute fonts if 方正小标宋简体 or 仿宋_GB2312 is not installed.\n\nFile v1.0.1:README.md\n\n# format-official-docx（党政公文格式化）\n\n将纯文本或现有 Word 文档，按党政机关公文格式规范，生成/重排为规范的 `.docx`。\n支持 **请示、报告、函、通知、批复、意见、纪要** 等文种，以及密级标注、红头、附件、版记、页码等要素。\n\n> 本技能默认遵循「三号仿宋_GB2312 正文、方正小标宋简体标题、版记落偶数页」等常见规范；\n> 具体以你单位印发的格式细则为准。文中示例均使用 `某单位` 等占位名称，请按实际替换。\n\n## 特性\n\n- 生成（generate）与重排（format-only）两种工作流\n- 文种：请示 / 报告 / 函 / 通知，校验亦支持 批复 / 意见 / 纪要\n- 红头（发文机关+文件）、发文字号、签发人、密级（左上角 三号黑体 `密级★期限`）\n- 主送机关自动补全中文冒号；成文日期支持 `--date today` 自动填\n- 附件说明（首行缩进）+ 附件首页「附件N」标识\n- 发文机关署名居中、成文日期右空四字\n- 版记（抄送 / 印发机关 / 印发日期）强制落偶数页\n- 字体缺失时主动告警（避免 Word 静默替换导致排版漂移）\n- `--bold-headings` 可选：一级黑体标题加粗\n\n## 安装\n\n```bash\npip install -r requirements.txt\n```\n\n依赖：`python-docx>=1.2.0`。\n\n## 快速开始\n\n生成一份请示：\n\n```bash\npython scripts/generate_official_docx.py \\\n --input body.txt --output out.docx --doc-type request \\\n --red-header \"某单位文件\" --outgoing-no \"某字〔2026〕1号\" --signer \"XXX\" \\\n --title \"某单位\\n关于某事项的请示\" --recipient \"某上级机关\" \\\n --issuer \"某单位\" --date today --add-closing \\\n --attachment \"关于某事项的说明\" --copy-to \"某机关\" \\\n --print-org \"某办公室\" --print-date \"2026年7月9日\" \\\n --contact \"(联系人：XXX，联系方式：XXXXXXXX)\" --secret-level \"秘密★1年\"\n```\n\n将已有 `.docx` 重排为规范格式（**保留表格**）：\n\n```bash\npython scripts/generate_official_docx.py \\\n --input source.docx --output formatted.docx --doc-type generic \\\n --format-only --promote-first-paragraph-title\n```\n\n校验格式信号：\n\n```bash\npython scripts/check_official_docx.py out.docx --doc-type request\npython scripts/check_fonts.py\n```\n\n## 常用参数\n\n| 参数 | 说明 |\n|---|---|\n| `--doc-type` | `generic` / `request` / `report` / `letter` / `notice` |\n| `--format-only` | 仅改版式与字体，不新增结尾、署名、附件等要素 |\n| `--red-header` | 请示/上行文红头，如 `某单位文件` |\n| `--letterhead` | 函的红头机关名称 |\n| `--secret-level` | 左上角密级，如 `秘密★1年` |\n| `--attachment` | 可多次，附件名称 |\n| `--copy-to` | 抄送机关 |\n| `--print-org` / `--print-date` | 印发机关 / 印发日期 |\n| `--date today` | 自动填入当前日期 |\n| `--add-closing` | 请示/报告自动补结尾（仅在缺失时） |\n| `--bold-headings` | 一级黑体标题加粗（默认不加粗） |\n\n## 字体说明\n\n生成脚本写入的字体名为规范名称：`方正小标宋简体`、`仿宋_GB2312`、`楷体_GB2312`、\n`黑体`、`宋体`、`Times New Roman`。若本机未安装对应字体，Word 打开时会替换渲染，\n脚本会在生成时向 stderr 告警。装好字体即可获得与打印一致的规范排版。\n\n## 文种速查\n\n详见 `references/document-types.md`；版式细则见 `references/format-rules.md`。\n\n## License\n\nMIT-0\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn78ykfdjrjqt3k7qfhmj66ef585ekjt\",\n \"slug\": \"format-official-docx\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1783580114720\n}\n\nFile v1.0.1:references/document-types.md\n\n# 公文文种选择速查\n\nUse only when the user does not clearly name the 文种.\n\n- 请示: ask a superior for approval/instructions; one main request; close `妥否，请批示。`\n- 报告: report work/situation/results upward; no approval request; close `特此报告。` when completing structure.\n- 函: non-subordinate communication, consultation, assistance request, reply, or opinion feedback; no-opinion replies usually use 函.\n- 通知: arrange work, forward documents, announce matters, require implementation.\n- 批复: superior replies to a subordinate 请示.\n- 意见: guidance, implementation suggestions, policy/work recommendations.\n- 纪要: meeting record, agreed matters, participants, follow-ups.\n\nHeuristics:\n\n- If the user explicitly says 请示/函/报告, obey.\n- \"征求意见/无意见/函复\" -> usually 函.\n- \"请批准/请审定/提请研究\" -> 请示.\n- \"汇报/报送情况/说明进展\" -> 报告.\n- \"请各单位落实/转发\" -> 通知.\n\nFile v1.0.1:references/format-rules.md\n\n# 党政机关公文格式规则\n\nPublic package rules distilled from local official-document formatting references. If these rules conflict with generic GB/T 9704 knowledge, follow these rules.\n\n## Page\n\n- A4; standard margins: top 3.7 cm, bottom 3.5 cm, left 2.8 cm, right 2.6 cm.\n- Some local 函 templates use first-page top 5.1 cm and bottom 2.1 cm; use only when explicitly requested.\n- Fixed line spacing: 28.9 pt. Default text color: black.\n- 双面打印，左侧装订.\n\n## Fonts\n\n- Red header / main title: 方正小标宋简体.\n- Main title: 二号, centered.\n- Body: 三号仿宋_GB2312; numbers/Latin text: Times New Roman.\n- Level 1 headings `一、`: 三号黑体.\n- Level 2 headings `（一）`: 三号楷体_GB2312.\n- Level 3/4 headings `1．` / `（1）`: 三号仿宋_GB2312.\n- Page number: 四号宋体, `— 1 —`.\n- 版记: 四号仿宋_GB2312.\n\n## 函\n\nInclude when formal:\n\n- Red agency letterhead, e.g. `某单位`, in large red 方正小标宋简体.\n- Red separator line below letterhead.\n- 发文字号 below separator, usually right aligned, e.g. `某字〔XXXX〕XX号`.\n- Matter title centered below document number.\n- Formal title usually includes issuing agency line plus matter title line.\n- 主送机关 ending with `：`.\n- Concise body; for reply/no-opinion letters: `贵单位关于征求某事项意见的来函收悉。经研究，我单位无意见。特此函复。`\n- Issuer/date right aligned with appropriate right blank space; optional contact line and disclosure note such as `（此件不公开）`.\n- Red bottom line when using letterhead paper.\n\n## 请示 / 上行文\n\nInclude when formal:\n\n- Red `发文机关名称+文件` header, e.g. `某单位文件`, 方正小标宋简体.\n- 发文字号 left and 签发人 right on same line; red separator line below.\n- Title usually split into issuing agency line and matter line.\n- 主送机关 ending with `：`.\n- Body closes with `妥否，请批示。` unless user forbids or text already includes it.\n- Issuer/date kept together.\n- Page number for multi-page/upward documents.\n- 版记 on even page: printing office and date, with separator lines.\n\n## 报告\n\n- Title, 主送机关, body, issuer/date.\n- Close with `特此报告。` only when generating/completing structure and absent from body.\n- Upward reports may include contact line below date.\n\n## Attachments\n\n- After body, leave one blank line.\n- One attachment: `附件：XXX`.\n- Multiple: `附件：1．XXX`, then ` 2．XXX`.\n- Wrapped attachment names align with the first character of the name.\n- Each attachment starts with `附件1`/`附件2` at top-left in 三号仿宋_GB2312.\n\n## Signature / Date / Copy Block\n\n- Leave about three blank lines before issuer/date.\n- 发文机关署名居中排版；成文日期右空四字（右对齐，右边距留约 2.26 cm）。\n- Keep issuer and date together; do not use `此页无正文`.\n- 版记 includes 抄送, 印发机关, 印发日期; copy recipients end with `。`.\n- 主送/抄送 punctuation: same system use `、`; different systems use `，`.\n\n## Text Conventions\n\n- Use proper marks: `《》`, nested `〈〉`, `〔〕`; do not replace `〈〉` with `< >`.\n- Classified documents: upper-left 三号黑体, `密级★保密期限`.\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nConvert pasted Chinese text or existing .docx into a Word document formatted as a PRC Party/government official document.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[wing-art](https://clawhub.ai/user/wing-art)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nEmployees, external users, and developers use this skill to generate or reformat Chinese Party/government official Word documents such as requests, reports, letters, notices, approvals, opinions, and meeting minutes. It helps preserve user-provided wording while applying official document layout, fonts, headers, attachments, page numbers, and format checks.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: Installing dependencies from PyPI may be unsuitable in restricted environments.
\nMitigation: Install only where PyPI packages are acceptable, and pin python-docx or use a lockfile for repeatable installs.
\nRisk: Official or classified-looking documents may contain sensitive material.
\nMitigation: Avoid processing sensitive material on untrusted machines and review the final Word document manually before use.
\nRisk: Missing required Chinese official-document fonts can cause Word to substitute fonts and shift layout.
\nMitigation: Run the font checker and install the required fonts before relying on printed or final formatting.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/wing-art/skills/format-official-docx)
\n- [公文文种选择速查](artifact/references/document-types.md)
\n- [党政机关公文格式规则](artifact/references/format-rules.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [files, shell commands, guidance]
\n**Output Format:** [DOCX files with Markdown command guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Generated documents should be manually reviewed before use; font availability can affect final Word rendering.]
\n\n## Skill Version(s):
\n1.0.1 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nFile v1.0.1:agents/openai.yaml\n\ninterface:\n display_name: \"党政公文格式化\"\n short_description: \"将文字或 Word 转为规范党政机关公文格式\"\n default_prompt: \"Use $format-official-docx to convert this text into a properly formatted official Word document.\"\n\nFile v1.0.1:requirements.txt\n\npython-docx>=1.2.0\n\nArchive v1.0.0: 10 files, 14212 bytes\n\nFiles: agents/openai.yaml (246b), references/document-types.md (980b), references/format-rules.md (3150b), requirements.txt (19b), scripts/check_fonts.py (1840b), scripts/check_official_docx.py (5621b), scripts/generate_official_docx.py (16057b), skill-card.md (2358b), SKILL.md (3604b), _meta.json (139b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: format-official-docx\ndescription: Convert pasted Chinese text or existing .docx content into a Word document formatted as a PRC Party/government official document. Use for 公文 formatting/generation tasks involving 函、请示、报告、通知、批复、意见、纪要、上行文, including format-only DOCX retypesetting, red headers, official fonts, margins, signatures, attachments, page numbers, and copy/printing blocks.\n---\n\n# Format Official Docx\n\nProduce a formatted `.docx`; do not answer with advice only.\n\n## Fast Workflow\n\n1. Classify intent:\n - `format-only`: preserve paragraph text/order; change layout/styles only.\n - `generate`: create the official document shell and concise body.\n2. Choose 文种. If unclear, use `references/document-types.md`; otherwise do not load it.\n3. For formal layout details, use `references/format-rules.md`. Local rules override generic GB/T 9704 knowledge.\n4. Generate with `scripts/generate_official_docx.py`.\n5. Run `scripts/check_official_docx.py` for formal 请示/函/报告 when practical.\n6. Save final user files to `outputs/`.\n\nPrerequisite: `python-docx`; install with `pip install -r requirements.txt` if missing.\n\n## Core Rules\n\n- Preserve substantive wording unless the user asks for drafting/revision.\n- Do not invent missing metadata; ask or use placeholders like `XXXX`.\n- Use 方正小标宋简体 for title/red header, 仿宋_GB2312 for body, 黑体 for first-level headings, 楷体_GB2312 for second-level headings, Times New Roman for numbers/Latin text.\n- Strict format-only mode must not add closings, signatures, attachments, or metadata.\n- Existing `.docx` reformatting preserves paragraph text, not tables/images/comments/tracked changes/text boxes/complex headers.\n\n## Common Commands\n\nGenerate 请示:\n\n```bash\npython scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type request --red-header \"某单位文件\" --outgoing-no \"某字〔XXXX〕XX号\" --signer \"XXX\" --title \"某单位\\n关于XXXX的请示\" --recipient \"某上级机关：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --add-closing\n```\n\nGenerate 函:\n\n```bash\npython scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type letter --letterhead \"某单位\" --outgoing-no \"某字〔XXXX〕XX号\" --title \"关于XXXX的函\" --recipient \"某单位：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --no-page-number\n```\n\nFormat only:\n\n```bash\npython scripts/generate_official_docx.py --input source.docx --output formatted.docx --doc-type generic --format-only --promote-first-paragraph-title\n```\n\nQuality checks:\n\n```bash\npython scripts/check_official_docx.py out.docx --doc-type request\npython scripts/check_fonts.py\n```\n\n## Key Options\n\n- `--doc-type`: `generic`, `request`, `report`, `letter`, `notice`\n- `--format-only`\n- `--red-header`: red `发文机关名称+文件` header for 请示/上行文\n- `--letterhead`: red agency header for 函\n- `--letter-special-margins`: use local 函 first-page margins 5.1/2.1 only when requested\n- `--outgoing-no`, `--signer`, `--title`, `--recipient`, `--issuer`, `--date`, `--contact`\n- `--attachment`, `--copy-to`, `--print-org`, `--print-date`, `--disclosure-note`\n- `--add-closing`: adds standard 请示/报告 closing only if absent\n\n## Final Inspection\n\nCheck title/red-header font, margins, line spacing, first-line indents, title issuing-agency line, 发文字号/签发人, right-aligned signature/date, contact/disclosure notes, page numbers, and 版记. Word may substitute fonts if 方正小标宋简体 or 仿宋_GB2312 is not installed.\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn78ykfdjrjqt3k7qfhmj66ef585ekjt\",\n \"slug\": \"format-official-docx\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1783464364978\n}\n\nFile v1.0.0:references/document-types.md\n\n# 公文文种选择速查\n\nUse only when the user does not clearly name the 文种.\n\n- 请示: ask a superior for approval/instructions; one main request; close `妥否，请批示。`\n- 报告: report work/situation/results upward; no approval request; close `特此报告。` when completing structure.\n- 函: non-subordinate communication, consultation, assistance request, reply, or opinion feedback; no-opinion replies usually use 函.\n- 通知: arrange work, forward documents, announce matters, require implementation.\n- 批复: superior replies to a subordinate 请示.\n- 意见: guidance, implementation suggestions, policy/work recommendations.\n- 纪要: meeting record, agreed matters, participants, follow-ups.\n\nHeuristics:\n\n- If the user explicitly says 请示/函/报告, obey.\n- \"征求意见/无意见/函复\" -> usually 函.\n- \"请批准/请审定/提请研究\" -> 请示.\n- \"汇报/报送情况/说明进展\" -> 报告.\n- \"请各单位落实/转发\" -> 通知.\n\nFile v1.0.0:references/format-rules.md\n\n# 党政机关公文格式规则\n\nPublic package rules distilled from local official-document formatting references. If these rules conflict with generic GB/T 9704 knowledge, follow these rules.\n\n## Page\n\n- A4; standard margins: top 3.7 cm, bottom 3.5 cm, left 2.8 cm, right 2.6 cm.\n- Some local 函 templates use first-page top 5.1 cm and bottom 2.1 cm; use only when explicitly requested.\n- Fixed line spacing: 28.9 pt. Default text color: black.\n- 双面打印，左侧装订.\n\n## Fonts\n\n- Red header / main title: 方正小标宋简体.\n- Main title: 二号, centered.\n- Body: 三号仿宋_GB2312; numbers/Latin text: Times New Roman.\n- Level 1 headings `一、`: 三号黑体.\n- Level 2 headings `（一）`: 三号楷体_GB2312.\n- Level 3/4 headings `1．` / `（1）`: 三号仿宋_GB2312.\n- Page number: 四号宋体, `— 1 —`.\n- 版记: 四号仿宋_GB2312.\n\n## 函\n\nInclude when formal:\n\n- Red agency letterhead, e.g. `某单位`, in large red 方正小标宋简体.\n- Red separator line below letterhead.\n- 发文字号 below separator, usually right aligned, e.g. `某字〔XXXX〕XX号`.\n- Matter title centered below document number.\n- Formal title usually includes issuing agency line plus matter title line.\n- 主送机关 ending with `：`.\n- Concise body; for reply/no-opinion letters: `贵单位关于征求某事项意见的来函收悉。经研究，我单位无意见。特此函复。`\n- Issuer/date right aligned with appropriate right blank space; optional contact line and disclosure note such as `（此件不公开）`.\n- Red bottom line when using letterhead paper.\n\n## 请示 / 上行文\n\nInclude when formal:\n\n- Red `发文机关名称+文件` header, e.g. `某单位文件`, 方正小标宋简体.\n- 发文字号 left and 签发人 right on same line; red separator line below.\n- Title usually split into issuing agency line and matter line.\n- 主送机关 ending with `：`.\n- Body closes with `妥否，请批示。` unless user forbids or text already includes it.\n- Issuer/date kept together.\n- Page number for multi-page/upward documents.\n- 版记 on even page: printing office and date, with separator lines.\n\n## 报告\n\n- Title, 主送机关, body, issuer/date.\n- Close with `特此报告。` only when generating/completing structure and absent from body.\n- Upward reports may include contact line below date.\n\n## Attachments\n\n- After body, leave one blank line.\n- One attachment: `附件：XXX`.\n- Multiple: `附件：1．XXX`, then ` 2．XXX`.\n- Wrapped attachment names align with the first character of the name.\n- Each attachment starts with `附件1`/`附件2` at top-left in 三号黑体.\n\n## Signature / Date / Copy Block\n\n- Leave about three blank lines before issuer/date.\n- Keep issuer and date together; do not use `此页无正文`.\n- 版记 includes 抄送, 印发机关, 印发日期; copy recipients end with `。`.\n- 主送/抄送 punctuation: same system use `、`; different systems use `，`.\n\n## Text Conventions\n\n- Use proper marks: `《》`, nested `〈〉`, `〔〕`; do not replace `〈〉` with `< >`.\n- Classified documents: upper-left 三号黑体, `密级★保密期限`.\n\nFile v1.0.0:skill-card.md\n\n## Description:
\nConvert pasted Chinese text or existing .docx content into a Word document formatted as a PRC Party/government official document.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[wing-art](https://clawhub.ai/user/wing-art)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and document operators use this skill to generate or reformat Chinese PRC Party/government official Word documents, including official document shells, red headers, signatures, attachments, page numbers, and formatting checks.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill reads and writes local document content, which may include sensitive official text.
\nMitigation: Use it only with documents the agent is authorized to read and write, and review generated files before sharing.
\nRisk: The dependency requirement allows python-docx version drift.
\nMitigation: Pin python-docx to a reviewed version or use a lockfile for reproducible shared or production installs.
\nRisk: Chinese official-document fonts may be unavailable on the execution system, causing Word font substitution.
\nMitigation: Run the bundled font check and install the required fonts before relying on final layout fidelity.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/wing-art/skills/format-official-docx)
\n- [Public document type selection reference](references/document-types.md)
\n- [Official document formatting rules reference](references/format-rules.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with shell commands and generated .docx files]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Produces local Word documents in .docx format and may emit validation results from bundled check scripts.]
\n\n## Skill Version(s):
\n1.0.0 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nFile v1.0.0:agents/openai.yaml\n\ninterface:\n display_name: \"党政公文格式化\"\n short_description: \"将文字或 Word 转为规范党政机关公文格式\"\n default_prompt: \"Use $format-official-docx to convert this text into a properly formatted official Word document.\"\n\nFile v1.0.0:requirements.txt\n\npython-docx>=1.2.0","readmeExcerpt":"Skill: 党政公文格式化 Owner: wing-art Summary: 将文字或 Word 转为规范党政机关公文格式 Tags: latest:1.0.2 Version history: v1.0.2 | 2026-07-09T08:31:26.327Z | user - Removed the sample file skill-card.md. - No changes to features or behavior; documentation updated and streamlined in SKILL.md. - All functionality remains as previously described. v1.0.1 | 2026-07-09T06:55:14.720Z | user - Added skill documentation (README.md) and metadata fil","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"python scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type request --red-header \"某单位文件\" --outgoing-no \"某字〔XXXX〕XX号\" --signer \"XXX\" --title \"某单位\\n关于XXXX的请示\" --recipient \"某上级机关：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --add-closing"},{"language":"bash","snippet":"python scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type letter --letterhead \"某单位\" --outgoing-no \"某字〔XXXX〕XX号\" --title \"关于XXXX的函\" --recipient \"某单位：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --no-page-number"},{"language":"bash","snippet":"python scripts/generate_official_docx.py --input source.docx --output formatted.docx --doc-type generic --format-only --promote-first-paragraph-title"},{"language":"bash","snippet":"python scripts/check_official_docx.py out.docx --doc-type request\npython scripts/check_fonts.py"},{"language":"bash","snippet":"pip install -r requirements.txt"},{"language":"bash","snippet":"python scripts/generate_official_docx.py \\\n --input body.txt --output out.docx --doc-type request \\\n --red-header \"某单位文件\" --outgoing-no \"某字〔2026〕1号\" --signer \"XXX\" \\\n --title \"某单位\\n关于某事项的请示\" --recipient \"某上级机关\" \\\n --issuer \"某单位\" --date today --add-closing \\\n --attachment \"关于某事项的说明\" --copy-to \"某机关\" \\\n --print-org \"某办公室\" --print-date \"2026年7月9日\" \\\n --contact \"(联系人：XXX，联系方式：XXXXXXXX)\" --secret-level \"秘密★1年\""}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: format-official-docx\ndescription: 将粘贴的中文文本或现有 .docx 文档，转换为符合党政机关公文格式规范的 Word 文档。支持函、请示、报告、通知、批复、意见、纪要、上行文等文种。功能包括红头、发文字号/签发人、密级标注（密级★期限）、主送机关自动补全冒号、--date today 自动填日期、附件说明与附件首页“附件N”标识、发文机关署名居中且成文日期右空四字、版记落偶数页、页码、字体缺失告警，以及保留表格的重排（format-only）模式。附带格式校验脚本。\n---\n\n# 党政公文格式化\n\n生成规范的 .docx 文件；不要只给建议而不实际生成。\n\n## 快速流程\n\n1. 判断意图：\n - `format-only`（仅重排）：保留段落文字与顺序，只调整版式与样式。\n - `generate`（生成）：创建公文外壳并撰写简洁正文。\n2. 选择文种。若不明确，参考 `references/document-types.md`；否则不必加载。\n3. 版式细则参考 `references/format-rules.md`。本地细则优先于通用 GB/T 9704 知识。\n4. 用 `scripts/generate_official_docx.py` 生成。\n5. 正式公文（请示/函/报告）生成后，尽量运行 `scripts/check_official_docx.py` 做格式校验。\n6. 最终文件保存到 `outputs/`。\n\n前置依赖：`python-docx`；若缺失请用 `pip install -r requirements.txt` 安装。\n\n## 核心规则\n\n- 除非用户要求起草或修改，否则保留原文实质内容。\n- 不要臆造缺失的元数据；应询问用户，或使用 `XXXX` 等占位符。\n- 标题/红头使用方正小标宋简体，正文使用仿宋_GB2312，一级标题使用黑体，二级标题使用楷体_GB2312，数字及拉丁文字使用 Times New Roman。\n- 严格的 format-only 模式不得新增结尾、署名、附件或元数据。\n- 现有 .docx 的 format-only 重排会保留段落文字与表格（重新套用正文规范字体）；不保留图片、批注、修订痕迹、文本框、复杂页眉。\n\n## 常用命令\n\n生成请示：\n\n```bash\npython scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type request --red-header \"某单位文件\" --outgoing-no \"某字〔XXXX〕XX号\" --signer \"XXX\" --title \"某单位\\n关于XXXX的请示\" --recipient \"某上级机关：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --add-closing\n```\n\n生成函：\n\n```bash\npython scripts/generate_official_docx.py --input body.txt --output out.docx --doc-type letter --letterhead \"某单位\" --outgoing-no \"某字〔XXXX〕XX号\" --title \"关于XXXX的函\" --recipient \"某单位：\" --issuer \"某单位\" --date \"XXXX年XX月XX日\" --no-page-number\n```\n\n仅重排：\n\n```bash\npython scripts/generate_official_docx.py --input source.docx --output formatted.docx --doc-type generic --format-only --promote-first-paragraph-title\n```\n\n格式校验：\n\n```bash\npython scripts/check_official_docx.py out.docx --doc-type request\npython scripts/check_fonts.py\n```\n\n## 关键参数\n\n- `--doc-type`：文种，`generic` / `request` / `report` / `letter` / `notice`\n- `--format-only`：仅重排模式\n- `--red-header`：请示/上行文的红色“发文机关名称+文件”红头\n- `--letterhead`：函的红色机关头\n- `--letter-special-margins`：仅在明确要求时使用本地函首页页边距（上 5.1 / 下 2.1）\n- `--outgoing-no`、`--signer`、`--title`、`--recipient`、`--issuer`、`--date`、`--contact`\n- `--attachment`、`--copy-to`、`--print-org`、`--print-date`、`--disclosure-note`\n- `--secret-level`：左上角三号黑体密级行，如 `秘密★1年`\n- `--add-closing`：仅在缺失时补充标准请示/报告结尾\n- `--date today`：自动填入当前日期（也接受 `XXXX年XX月XX日`）\n- `--bold-headings`：一级（黑体）标题加粗；默认关闭，遵循三号黑体不加粗规范\n\n## 最终检查\n\n检查标题/红头字体、页边距、行距、首行缩进、标题发文机关行、发文字号/签发人、右对齐的署名与日期、联系人/披露说明、页码、版记。若本机未安装方正小标宋简体或仿宋_GB2312，Word 会替换字体。"},{"path":"README.md","content":"# format-official-docx（党政公文格式化）\n\n将纯文本或现有 Word 文档，按党政机关公文格式规范，生成/重排为规范的 `.docx`。\n支持 **请示、报告、函、通知、批复、意见、纪要** 等文种，以及密级标注、红头、附件、版记、页码等要素。\n\n> 本技能默认遵循「三号仿宋_GB2312 正文、方正小标宋简体标题、版记落偶数页」等常见规范；\n> 具体以你单位印发的格式细则为准。文中示例均使用 `某单位` 等占位名称，请按实际替换。\n\n## 特性\n\n- 生成（generate）与重排（format-only）两种工作流\n- 文种：请示 / 报告 / 函 / 通知，校验亦支持 批复 / 意见 / 纪要\n- 红头（发文机关+文件）、发文字号、签发人、密级（左上角 三号黑体 `密级★期限`）\n- 主送机关自动补全中文冒号；成文日期支持 `--date today` 自动填\n- 附件说明（首行缩进）+ 附件首页「附件N」标识\n- 发文机关署名居中、成文日期右空四字\n- 版记（抄送 / 印发机关 / 印发日期）强制落偶数页\n- 字体缺失时主动告警（避免 Word 静默替换导致排版漂移）\n- `--bold-headings` 可选：一级黑体标题加粗\n\n## 安装\n\n```bash\npip install -r requirements.txt\n```\n\n依赖：`python-docx>=1.2.0`。\n\n## 快速开始\n\n生成一份请示：\n\n```bash\npython scripts/generate_official_docx.py \\\n --input body.txt --output out.docx --doc-type request \\\n --red-header \"某单位文件\" --outgoing-no \"某字〔2026〕1号\" --signer \"XXX\" \\\n --title \"某单位\\n关于某事项的请示\" --recipient \"某上级机关\" \\\n --issuer \"某单位\" --date today --add-closing \\\n --attachment \"关于某事项的说明\" --copy-to \"某机关\" \\\n --print-org \"某办公室\" --print-date \"2026年7月9日\" \\\n --contact \"(联系人：XXX，联系方式：XXXXXXXX)\" --secret-level \"秘密★1年\"\n```\n\n将已有 `.docx` 重排为规范格式（**保留表格**）：\n\n```bash\npython scripts/generate_official_docx.py \\\n --input source.docx --output formatted.docx --doc-type generic \\\n --format-only --promote-first-paragraph-title\n```\n\n校验格式信号：\n\n```bash\npython scripts/check_official_docx.py out.docx --doc-type request\npython scripts/check_fonts.py\n```\n\n## 常用参数\n\n| 参数 | 说明 |\n|---|---|\n| `--doc-type` | `generic` / `request` / `report` / `letter` / `notice` |\n| `--format-only` | 仅改版式与字体，不新增结尾、署名、附件等要素 |\n| `--red-header` | 请示/上行文红头，如 `某单位文件` |\n| `--letterhead` | 函的红头机关名称 |\n| `--secret-level` | 左上角密级，如 `秘密★1年` |\n| `--attachment` | 可多次，附件名称 |\n| `--copy-to` | 抄送机关 |\n| `--print-org` / `--print-date` | 印发机关 / 印发日期 |\n| `--date today` | 自动填入当前日期 |\n| `--add-closing` | 请示/报告自动补结尾（仅在缺失时） |\n| `--bold-headings` | 一级黑体标题加粗（默认不加粗） |\n\n## 字体说明\n\n生成脚本写入的字体名为规范名称：`方正小标宋简体`、`仿宋_GB2312`、`楷体_GB2312`、\n`黑体`、`宋体`、`Times New Roman`。若本机未安装对应字体，Word 打开时会替换渲染，\n脚本会在生成时向 stderr 告警。装好字体即可获得与打印一致的规范排版。\n\n## 文种速查\n\n详见 `references/document-types.md`；版式细则见 `references/format-rules.md`。\n\n## License\n\nMIT-0"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn78ykfdjrjqt3k7qfhmj66ef585ekjt\",\n \"slug\": \"format-official-docx\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1783585886327\n}"},{"path":"references/document-types.md","content":"# 公文文种选择速查\n\n仅在用户未明确文种时使用。\n\n- 请示：向上级请求批准或指示；一事一请；结尾用 `妥否，请批示。`\n- 报告：向上级汇报工作、情况或结果；不提批准请求；补全结构时以 `特此报告。` 结尾。\n- 函：不相隶属机关之间商洽、询问、请求协助、答复或反馈意见；无意见答复通常用函。\n- 通知：布置工作、转发文件、公布事项、要求执行。\n- 批复：上级答复下级请示。\n- 意见：提出指导意见、实施办法、政策或工作建议。\n- 纪要：会议记录，含议定事项、参会单位、后续跟进。\n\n判断参考：\n\n- 用户明确说请示/函/报告，从其意。\n- “征求意见/无意见/函复” → 通常为函。\n- “请批准/请审定/提请研究” → 通常为请示。\n- “汇报/报送情况/说明进展” → 通常为报告。\n- “请各单位落实/转发” → 通常为通知。"},{"path":"references/format-rules.md","content":"# 党政机关公文格式规则\n\n本规则提炼自本地公文格式规范。若与通用 GB/T 9704 知识冲突，以本规则为准。\n\n## 页面\n\n- 用 A4 纸；标准页边距：上 3.7 厘米、下 3.5 厘米、左 2.8 厘米、右 2.6 厘米。\n- 部分本地函模板首页用上 5.1 厘米、下 2.1 厘米；仅在明确要求时使用。\n- 固定行距 28.9 磅。默认文字颜色为黑色。\n- 双面打印，左侧装订。\n\n## 字体\n\n- 红头 / 主标题：方正小标宋简体。\n- 主标题：二号，居中。\n- 正文：三号仿宋_GB2312；数字及拉丁文字用 Times New Roman。\n- 一级标题（一、）：三号黑体。\n- 二级标题（（一））：三号楷体_GB2312。\n- 三级/四级标题（1． / （1））：三号仿宋_GB2312。\n- 页码：四号宋体，格式为 — 1 —。\n- 版记：四号仿宋_GB2312。\n\n## 函\n\n正式函应包含：\n\n- 红色机关头，如 `某单位`，用大号红色方正小标宋简体。\n- 机关头下方红色分隔线。\n- 分隔线下方为发文字号，通常右对齐，如 `某字〔XXXX〕XX号`。\n- 文种标题在文号下方居中。\n- 正式标题通常包含发文机关行与事由行。\n- 主送机关以 `：` 结尾。\n- 正文简洁；复函/无意见函可用：“贵单位关于征求某事项意见的来函收悉。经研究，我单位无意见。特此函复。”\n- 署名/日期右对齐并留出适当右空；可加联系人行与披露说明，如 `（此件不公开）`。\n- 使用套印红头纸时，底部加红色结束线。\n\n## 请示 / 上行文\n\n正式请示/上行文应包含：\n\n- 红色“发文机关名称+文件”红头，如 `某单位文件`，方正小标宋简体。\n- 发文字号居左、签发人居右，同处一行；下方红色分隔线。\n- 标题通常分为发文机关行与事由行。\n- 主送机关以 `：` 结尾。\n- 正文以 `妥否，请批示。` 结尾，除非用户禁止或正文已含此句。\n- 署名与日期保持在一起。\n- 多页/上行文加页码。\n- 版记落偶数页：含印发机关与日期，并加分隔线。\n\n## 报告\n\n- 含标题、主送机关、正文、署名/日期。\n- 仅在补全结构且正文缺失时，以 `特此报告。` 结尾。\n- 上行报告可在日期下方加联系人行。\n\n## 附件\n\n- 正文之后空一行。\n- 单个附件：`附件：XXX`。\n- 多个附件：`附件：1．XXX`，换行后 ` 2．XXX`。\n- 附件名换行时与名称首字对齐。\n- 每个附件首页左上角以三号仿宋_GB2312 标注 `附件1` / `附件2`。\n\n## 署名 / 日期 / 版记\n\n- 署名/日期前空约三行。\n- 发文机关署名居中排版；成文日期右空四字（右对齐，右边距留约 2.26 厘米）。\n- 署名与日期保持在一起；不要用“此页无正文”。\n- 版记含抄送、印发机关、印发日期；抄送单位以 `。` 结尾。\n- 主送/抄送标点：同一系统用 `、`；不同系统用 `，`。\n\n## 文字规范\n\n- 使用规范标点：《》、嵌套〈〉、〔〕；不要用 `< >` 代替 `〈〉`。\n- 涉密文件：左上角三号黑体标注 `密级★保密期限`。"}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"将文字或 Word 转为规范党政机关公文格式 Skill: 党政公文格式化 Owner: wing-art Summary: 将文字或 Word 转为规范党政机关公文格式 Tags: latest:1.0.2 Version history: v1.0.2 | 2026-07-09T08:31:26.327Z | user - Removed the sample file skill-card.md. - No changes to features or behavior; documentation updated and streamlined in SKILL.md. - All functionality remains as previously described. v1.0.1 | 2026-07-09T06:55:14.720Z | user - Added skill documentation (README.md) and metadata fil","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":736,"uniquenessScore":60,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T09:44:28.436Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T09:44:28.436Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T14:14:53.531Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}