Skip to content
Back to search

official-document-skill

Draft, revise, polish, humanize, and quality-check Chinese official documents and government-style practical writing (公文、党政机关公文、事务文书、申论应用文、人民日报风格政务表达), producing deliverable drafts with correct document type, format, restrained institutional tone, concrete facts, People's Daily-inspired expression discipline, humanizer-style AI-pattern cleanup, and reduced AI-flavored phrasing. Use when the user asks for 通知、通报、报告、请示、批复、函、纪要、决定、通告、议案、倡议书、工作方案、工作计划、工作总结、简报、讲话稿、发言稿、汇报材料、调研报告、宣传稿、公开信、感谢信、信访回复、理论评论、政策解读, or asks to 一键生成/润色/改写/降AI味/减少AI味/人味/自然表达/人民日报风格/检查格式/生成可交付公文.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked yesterday
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/liuxiangjian-ai--official-document-skill/badge.svg)](/listings/liuxiangjian-ai--official-document-skill)

HTML

<a href="/listings/liuxiangjian-ai--official-document-skill"><img src="/api/listings/liuxiangjian-ai--official-document-skill/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 551 lines
  1. ---
  2. name: official-document-skill
  3. description: Draft, revise, polish, humanize, and quality-check Chinese official documents and government-style practical writing (公文、党政机关公文、事务文书、申论应用文、人民日报风格政务表达), producing deliverable drafts with correct document type, format, restrained institutional tone, concrete facts, People's Daily-inspired expression discipline, humanizer-style AI-pattern cleanup, and reduced AI-flavored phrasing. Use when the user asks for 通知、通报、报告、请示、批复、函、纪要、决定、通告、议案、倡议书、工作方案、工作计划、工作总结、简报、讲话稿、发言稿、汇报材料、调研报告、宣传稿、公开信、感谢信、信访回复、理论评论、政策解读, or asks to 一键生成/润色/改写/降AI味/减少AI味/人味/自然表达/人民日报风格/检查格式/生成可交付公文.
  4. ---
  5. # 公文写作
  6. ## Purpose
  7. Generate or revise Chinese official documents that are structurally correct, usable as a deliverable, fact-grounded, restrained in tone, and low in AI-flavored boilerplate. Combine two source bases:
  8. - Formal public-document writing rules: document-type choice, official format, upward/downward/parallel writing, closing formulas, and common format errors.
  9. - People's Daily-style expression distillation: fact density, restrained judgment, functional paragraphs, natural progression, abstract-word control, and resistance to empty slogans.
  10. - Humanizer-style cleanup rules: significance inflation, fake depth, vague actors, rule-of-three packaging, synonym cycling, meta-commentary, formulaic conclusions, and over-polished cadence.
  11. ## Core Workflow
  12. 1. Identify the scenario: issuer, recipient, relationship (上行/下行/平行/面向公众), purpose, audience, urgency, required length, and whether a formal red-head shell is needed.
  13. 2. Choose the document type. If the user's requested type conflicts with purpose or relationship, quietly correct it in the draft or briefly flag the mismatch.
  14. 3. Extract facts before drafting: subject, object, action, mechanism, data, time, place, problem, result, responsibility, deadline, feedback path, and policy basis.
  15. 4. Build a document skeleton by type. Do not force every task into a publicity article, speech, or three-part slogan structure.
  16. 5. Draft with official restraint: facts and tasks first, then necessary judgment. Use long sentences for background, mechanisms, and compound facts; use short sentences for decisions, reminders, and closing.
  17. 6. Run the anti-AI pass: check fact density, judgment strength, sentence rhythm, abstract-word control, paragraph function, type fit, and grounded ending.
  18. 7. Run the humanizer pass: ask "What still makes this look AI-written?" Remove clustered tells such as meaning inflation, fake depth, meta signposting, rule-of-three packaging, synonym cycling, vague attribution, generic positive conclusions, and overly tidy cadence.
  19. 8. Score internally using the rubric below. If below 80, rewrite or compress hollow paragraphs before final output.
  20. 9. Deliver the final document first. Add a short "需补充信息" list only when placeholders remain or missing facts materially affect use.
  21. ## Output Defaults
  22. - Use Chinese unless the user requests another language.
  23. - Produce a complete usable draft, not only an outline, when enough facts exist.
  24. - If key facts are missing, use a small number of bracketed placeholders such as `〔发文机关〕` or `〔日期〕`.
  25. - For formal official drafts, include title, main recipient, body, issuing unit, and date when applicable. Include 发文字号、附件、抄送、版记 only if requested or supplied.
  26. - For exam/application-writing prompts, obey the word limit and omit formal elements only when the prompt says "不必考虑格式".
  27. - Never invent laws, documents, meetings, leader names, numbers, departments, budgets, dates, outcomes, or approvals.
  28. - Do not leave chatbot artifacts in the deliverable, such as `当然可以`, `下面是`, `希望这能帮到你`, `如需我继续`, or explanations of what the assistant is about to do.
  29. ## Document-Type Decision
  30. ### Formal Official Documents
  31. | 文种 | 适用场景 | Key Structure | Required Discipline |
  32. | --- | --- | --- | --- |
  33. | 通知 | 下行或平行告知办理、执行、周知事项 | 依据/背景 + 事项 + 要求 + 时限 | 明确对象、事项、责任;平行通知避免命令口吻 |
  34. | 通报 | 表彰先进、批评错误、传达重要情况 | 事实 + 评价/原因 + 决定/要求 | 事实准确,评价克制,避免情绪化 |
  35. | 报告 | 向上级汇报工作、反映情况、答复询问 | 情况 + 做法 + 成效 + 问题 + 下一步 | 不夹带请示事项;可用"特此报告" |
  36. | 请示 | 向上级请求指示、批准、批转 | 缘由 + 依据/困难 + 请求事项 + 请求语 | 一文一事,一般只送一个主送机关;"妥否,请批示/批复" |
  37. | 批复 | 答复下级请示 | 引述来文 + 批复意见 + 要求 | 明确同意/不同意及依据,不含糊 |
  38. | 函 | 不相隶属机关商洽、询问、答复、请求批准 | 来由 + 事项 + 希望/回复 | 语气平等、礼貌;"特此函告/函复""盼复" |
  39. | 纪要 | 记载会议主要情况和议定事项 | 会议概况 + 议定事项 + 落实要求 | 写"会议认为/指出/要求",不写流水账 |
  40. | 决定 | 对重要事项作出安排、奖惩或变更 | 依据/事实 + 决定事项 + 执行要求 | 权威、明确,适合较重大事项 |
  41. | 通告 | 在一定范围公布应遵守或周知事项 | 依据 + 通告事项 + 生效/执行要求 | 面向社会或特定范围,条款清楚 |
  42. | 公告 | 向国内外宣布重要事项或法定事项 | 事项 + 说明 | 级别和事项通常较高,慎用 |
  43. | 意见 | 对重要问题提出见解和处理办法 | 背景意义 + 总体要求 + 具体意见 | 政策性较强,可上行、下行、平行 |
  44. | 议案 | 政府向人大或人大常委会提请审议 | 案由 + 方案/依据 + 提请审议 | 注意法定主体和程序 |
  45. ### Practical Government Writing
  46. | 文体 | 适用场景 | Writing Focus |
  47. | --- | --- | --- |
  48. | 工作方案 | 安排专项行动、活动、治理任务 | 目标要求、重点任务、实施步骤、责任分工、保障措施 |
  49. | 工作计划 | 对未来阶段工作作安排 | 目标、重点任务、时间节点、保障措施;少写成绩,多写安排 |
  50. | 工作总结 | 回顾阶段工作 | 总体情况、主要做法、成效经验、问题不足、下步安排 |
  51. | 简报/信息稿 | 内部快速反映情况、经验、动态 | 导语、主要做法、阶段成效、经验启示;短、实、新 |
  52. | 讲话稿/发言稿 | 会议、活动、座谈发言 | 称谓、开场、形势认识、重点任务、落实要求、收束 |
  53. | 表态发言 | 表达态度和落实承诺 | 认识、态度、措施、承诺;每个表态接具体动作 |
  54. | 汇报材料 | 向领导或会议汇报 | 背景、进展、成效、问题、建议/下一步;突出可决策信息 |
  55. | 调研报告 | 反映调查研究结果 | 调研背景、现状、问题原因、对策建议;建议与问题对应 |
  56. | 倡议书 | 面向群体发起行动 | 背景意义、倡议事项、号召;热情但不空泛 |
  57. | 宣传稿 | 面向公众宣传政策、活动、典型 | 场景切入、典型事实、做法成效、适度升华 |
  58. | 公开信 | 面向特定群体公开沟通 | 称谓明确,先共情/说明,再提出事项,结尾表达期待 |
  59. | 感谢信 | 表达感谢和表扬 | 具体事迹、影响意义、感谢敬意;避免泛泛而谈 |
  60. | 信访回复 | 答复群众诉求 | 受理情况、调查核实、处理意见、救济渠道/联系方式 |
  61. | 理论评论 | 阐释观点、回应问题 | 问题、判断、论证、事实、价值收束;不要反套到普通公文 |
  62. | 政策解读 | 说明政策内容和执行口径 | 政策依据、核心变化、适用对象、办理流程、问答提示 |
  63. ### Easy Confusions
  64. - 请示 vs 报告: 有请求批准就是请示;只汇报情况就是报告。报告不得夹带"请予批准"。
  65. - 批复 vs 复函: 有隶属关系、答复下级请示用批复;不相隶属单位之间答复用函。
  66. - 通知 vs 通告: 内部或特定单位办理周知多用通知;面向社会公开遵守事项多用通告。
  67. - 纪要 vs 会议记录: 纪要提炼议定事项并可用于执行;会议记录是原始过程材料。
  68. - 方案 vs 计划: 方案重"如何组织实施专项任务";计划重"未来一段时间做什么"。
  69. ## Formal Format Rules
  70. ### Title
  71. - Common structure: `发文机关 + 关于 + 事由 + 的 + 文种`, such as `XX市人民政府关于开展安全生产专项整治的通知`.
  72. - Use `关于 + 事由 + 的 + 文种` when the issuer is unknown or a simplified draft is requested.
  73. - Avoid semantic repetition: do not write `关于请求批准……的请示`; do not write a 函 as a command.
  74. - The title should identify the matter and document type. Do not replace a document title with a slogan.
  75. ### Main Recipient
  76. - Write the main recipient flush left with a colon.
  77. - A 请示 generally has only one main recipient; use 抄送 for other necessary units.
  78. - Use 顿号 between same-level same-category organs; use 逗号 between different categories.
  79. - For public-facing practical writing, use audience labels such as `广大市民朋友们:`.
  80. ### Body
  81. - Opening: explain basis, background, purpose, problem, or incoming document. Do not start with unrelated grand meaning.
  82. - Main part: arrange matters in a list when execution is needed. Clarify object, task, standard, deadline, responsible unit, and feedback.
  83. - Closing by type: 请示 uses `妥否,请批示/批复`; 函 uses `特此函告/函复` or `盼复`; 通知 uses implementation requirements; 报告 may use `特此报告`.
  84. - Keep one document to one main matter, especially for 请示、函、批复.
  85. ### Attachments, Signature, Date
  86. - If attachments are mentioned, list them as `附件:1. XXX`; attachment names usually do not end with punctuation.
  87. - Issuing unit and date usually align to the right. A normal date may be `2026年6月10日`.
  88. - Formal documents may require unit-specific layout, seal rules, red-head page setup, and版记. Do not simulate unavailable seals or file numbers.
  89. - The date should match the signing/issuing logic; do not invent it.
  90. ### Writing Relationship
  91. - 上行文: 请示、报告. Be factual and respectful; do not decide for the superior.
  92. - 下行文: 通知、通报、决定、批复. Be clear about requirements, responsibility, and deadlines.
  93. - 平行文: 函. Use equal, consultative language; do not issue commands.
  94. ### Common Format Errors
  95. - A report includes a hidden request for approval.
  96. - A request has multiple main recipients or multiple matters.
  97. - The title document type conflicts with the body purpose.
  98. - The main recipient is missing or mismatched.
  99. - An attachment is mentioned but not listed.
  100. - Date, issuing unit, and title are inconsistent.
  101. - `相关部门` or `各单位` is used where a responsible subject must be clear.
  102. ## People's Daily-Inspired Expression Patterns
  103. Use these patterns as expression discipline, not as decorative imitation. Do not transfer commentary style into a routine notice or request.
  104. ### High-Frequency Structure Patterns
  105. - Background-introduction pattern: reality/policy background -> object explanation -> basic judgment -> facts -> lesson. Suitable for reports, summaries, research reports, speech openings. Risk: background too large and detached from the unit's work.
  106. - Problem-entry pattern: problem or shortcoming -> cause breakdown -> facts -> direction. Suitable for research reports,整改 reports, special reports. Risk: saying only "坚持问题导向" without a real problem.
  107. - Achievement-summary pattern: work foundation -> main practices -> stage results -> experience -> next steps. Suitable for summaries, reports, briefings. Risk: stronger judgment than evidence.
  108. - Policy-interpretation pattern: policy basis -> core requirements -> task breakdown -> implementation safeguards. Suitable for schemes, implementation opinions, notice attachments. Risk: rearranging policy words without turning them into local tasks.
  109. - Action-deployment pattern: situation judgment -> objectives -> key measures -> responsibility mechanism -> deadline. Suitable for方案、通知、会议部署. Risk: continuous `要……` with verbs that have no object.
  110. - Value-elevation pattern: typical fact -> value judgment -> broader significance -> outlook. Suitable for publicity articles and speech endings only in moderation. Risk: oversized ending in ordinary official writing.
  111. ### Logic Progression Rules
  112. - From background to problem: use changes in a real work scene, not vague "complex situation".
  113. - From problem to measure: write the problem manifestation first, then the matching action.
  114. - From achievement to experience: write what was completed before summarizing the practice formed.
  115. - From deployment to implementation: after the objective, write responsible subject, process node, deadline, and feedback.
  116. - From macro judgment to local work: every macro word must connect to this unit, field, or task.
  117. - From case to general rule: give the typical object, extract the mechanism, then state the boundary.
  118. - Prefer factual order and work-process progression over dense connectors such as `不仅……而且……` or `一方面……另一方面……`.
  119. ### Paragraph Function
  120. Every paragraph must have one primary function: background, problem, basis, measure, result, responsibility, deadline, safeguard, or closing. Do not stack several paragraphs that only explain significance.
  121. Useful paragraph roles:
  122. - Background paragraph: sets the boundary of the task.
  123. - Problem paragraph: identifies object, link, impact.
  124. - Measure paragraph: names the subject, action, method, and result.
  125. - Responsibility paragraph: names牵头单位、配合单位、反馈方式、检查节点.
  126. - Closing paragraph: returns to办理要求、执行提醒、报送节点、工作目标.
  127. ## Anti-AI Style Standard
  128. ### Fact Density
  129. Common AI problem: a paragraph has only meaning, attitude, and slogans, with no object, action, mechanism, or data.
  130. Rule: after deleting adjectives and four-character slogans, the paragraph should still answer: who does what, how, and to what extent.
  131. Prefer:
  132. - `我单位将办事材料由〔数量〕项压减至〔数量〕项,新增线上预审入口,减少群众现场补交材料次数。`
  133. Avoid:
  134. - `我单位持续优化服务能力,推动工作提质增效。`
  135. ### Judgment Strength
  136. Match the evaluation word to evidence strength:
  137. | Level | Expression | Use Condition |
  138. | --- | --- | --- |
  139. | 1 | 已启动、正在开展 | Only deployment or initial action exists |
  140. | 2 | 有序推进、稳步推进 | Planned steps exist, results limited |
  141. | 3 | 取得进展、初见成效 | Stage results or audience feedback exists |
  142. | 4 | 取得明显成效、形成机制 | Data,制度、流程, or stable operation exists |
  143. | 5 | 重大突破、历史性成就 | Authoritative recognition, key indicators, industry comparison, or historic node exists |
  144. When evidence is weak, downgrade the judgment. 宁可稳妥,不要拔高.
  145. ### Sentence Rhythm
  146. - Avoid continuous `要……要……要……`.
  147. - Avoid overusing `不仅……而且……`, `既是……也是……`, `一方面……另一方面……`.
  148. - Avoid every paragraph using the same pattern.
  149. - Use long sentences for facts, basis, processes, and compound conditions; use short sentences for decisions and reminders; use bullet/numbered lists for measures.
  150. ### Abstract-Word Control
  151. Abstract words are allowed only when followed by concrete content.
  152. | Term | Use When | Do Not Use When | Must Be Followed By |
  153. | --- | --- | --- | --- |
  154. | 高质量发展 | development goal, industrial upgrading, comprehensive results | single small task or routine notice | indicator, project, quality change |
  155. | 赋能 | technology/platform/finance actually supports something | no clear tool or object | object and method |
  156. | 聚力 | multiple parties invest in one target | one department's routine work | participating subjects and target |
  157. | 抓手 | explaining an implementation carrier | no project,制度, or platform | specific carrier name |
  158. | 体系 | multi-level institutional arrangement exists | only scattered measures | components |
  159. | 格局 | multi-subject or multi-region relation | ordinary work arrangement | participants and relation |
  160. | 机制 | workflow, responsibility, feedback exists | temporary action only | mechanism name and operation |
  161. | 动能 | economy, innovation, employment growth force | ordinary activity | source and manifestation |
  162. | 生态 | innovation/business/culture multi-party environment | single system | subject relation and environmental change |
  163. | 闭环 | discovery, handling, feedback, review exist | no feedback step | loop steps |
  164. | 协同 | cross-department/level/region coordination | one department alone | who coordinates with whom |
  165. | 提质增效 | quality and efficiency both evidenced | only routine推进 | quality and efficiency changes |
  166. | 走深走实 | learning/policy implementation has stages | generic expression | concrete deepening action |
  167. | 落地见效 | policy already executed and has result | just deployed | execution result |
  168. | 凝心聚力 | mobilization, meeting, team-building | technical/business document | common goal |
  169. | 久久为功 | long-term governance/ecology/style work | short-term task | long-term task and stage plan |
  170. | 开创新局面/谱写新篇章 | publicity or speech ending with evidence | routine notice, request,方案正文 | concrete content of the "new" situation |
  171. ### Negative List
  172. Watch for and rewrite:
  173. - 空泛套话: direction and attitude without work information. Replace with object and action.
  174. - 过度拔高: ordinary facts called "重大突破" or "历史性成就". Downgrade.
  175. - 机械排比: neat but empty `要……要……要……`. Convert to task list.
  176. - 四字词堆叠: `凝心聚力、提质增效、走深走实` in one sentence. Keep at most one necessary abstraction.
  177. - 万能结尾: `谱写新篇章、开创新局面` in any document. Return to task, deadline, responsibility.
  178. - 虚假具体: `相关部门、重点领域、关键环节` repeatedly used with no real boundary. Name the subject or use clear placeholders.
  179. - 宣传腔过重: routine documents written as praise reports. Keep facts, reduce emotion.
  180. - 理论腔过重: dense concepts with no implementation content. Attach each concept to a task.
  181. - 文种错位: notice written as speech; request written as summary.
  182. - 逻辑空转: from meaning to meaning, no new information.
  183. - 缺少事实支撑: judgment without data, case, mechanism, or feedback.
  184. - 动词无宾语: `扎实推进、全面加强` without what is being advanced or strengthened.
  185. - 抽象词连续堆叠: `赋能、生态、动能、协同` explaining each other.
  186. - 口号密度过高: more statements than facts.
  187. - AI连接句式过密: connectors replace actual cause, sequence, and responsibility.
  188. ## Humanizer Pass for Official Documents
  189. Use this after the normal公文 anti-AI pass. It is stricter about text that "looks polished" but still feels generated. Keep the official register; do not add blog-style personality, jokes, first-person opinions, or casual asides unless the requested文体 is a personal speech or public-facing article.
  190. ### Rewrite, Do Not Merely Delete
  191. When revising user text, preserve the original coverage and intent. If the input has five substantive points, the output should still cover five substantive points unless the user asks to compress. Replace AI patterns with concrete official wording, not with emptiness.
  192. ### Cluster-Based Detection
  193. Do not over-edit a phrase just because it is formal. Flag AI味 when several tells appear together: abstract praise + tidy three-part rhythm + vague subject + no facts + generic ending. A single common transition word or a polished sentence is not enough.
  194. ### Public-Document Humanizer Checklist
  195. | AI tell | 公文中的表现 | Rewrite rule |
  196. | --- | --- | --- |
  197. | Significance inflation | `具有重要意义、标志着、彰显了、充分体现了` used without evidence | State the actual task, result, or policy basis |
  198. | Fake depth with participles | `推动...、促进...、助力...、彰显...` chained after one sentence | Keep one main action and give object/process |
  199. | Promotional tone | `亮点纷呈、成效斐然、精彩纷呈、焕发活力` in routine work | Replace with measurable progress or observed change |
  200. | Vague attribution | `有关方面认为、群众普遍认为、社会反响良好` without source | Name the source, survey, feedback channel, or omit |
  201. | Formulaic challenge section | `虽然面临挑战,但前景广阔` | Name the actual difficulty and next handling step |
  202. | AI vocabulary clustering | `关键、赋能、生态、格局、体系、动能` stacked together | Keep the necessary term and attach concrete content |
  203. | Avoiding simple verbs | `发挥着重要作用、承载着重要使命、展现出强大动能` | Prefer `是、有、完成、建立、解决、减少、增加` when enough |
  204. | Rule of three packaging | Every paragraph has exactly three neat items | Use the natural number of tasks; split or merge based on substance |
  205. | Synonym cycling | `单位/部门/机关/主体` alternated to avoid repetition | Repeat the clearest term;公文允许必要 repetition |
  206. | False range | `从思想认识到行动落实、从机制建设到成效转化` without real scale | List the real links or remove the range |
  207. | Passive/subjectless fragments | `已完成整改、将持续推进` with no actor | Add the responsible unit when useful |
  208. | Meta signposting | `下面从三个方面展开、本文将进行阐述` in the deliverable | Start with the content |
  209. | Generic positive conclusion | `未来可期、再上新台阶、谱写新篇章` | End with deadline, responsibility, reporting, or next step |
  210. | Manufactured punchline | Several short dramatic sentences to sound forceful | Use normal official cadence; one short reminder is enough |
  211. | Aphorism formula | `安全是发展的底线、服务是治理的温度` used as filler | Keep only if it directly leads into a concrete task |
  212. ### Cadence Rules
  213. - Avoid perfectly symmetrical paragraph design when the material does not support it. Real公文 can have one short paragraph for background and longer paragraphs for measures.
  214. - Avoid making every item begin with the same verb (`强化、强化、强化`) or every heading the same length.
  215. - Repeat official nouns when precision requires it. Do not rotate synonyms just to sound varied.
  216. - Prefer simple verbs where possible: `是、有、建成、完成、发现、整改、报送、反馈、纳入、公开`.
  217. - In formal公文, neutral and plain is the human voice. Do not inject personality merely to sound human.
  218. ### Hard Cuts in Final Deliverables
  219. Before final output, remove:
  220. - Chatbot framing: `当然可以、以下是、我为你、希望有帮助、如需继续`.
  221. - Tutorial announcements: `下面我们来看、接下来从以下方面、让我们深入探讨`.
  222. - Knowledge-gap filler: `由于资料有限、根据现有信息推测、可能大概`.
  223. - Decoration: emojis, bolded inline labels, unnecessary English title case.
  224. - Over-dramatic punctuation and web-writing devices. In Chinese公文, prefer normal Chinese punctuation and paragraphing.
  225. ### Second-Pass Question
  226. Before final delivery, ask internally:
  227. `如果这篇公文被退回,最可能被批评哪里像 AI 写的?`
  228. Fix the answer before sending. Common fixes:
  229. - If the answer is "空": add facts, actors, mechanisms, deadlines.
  230. - If the answer is "飘": downgrade judgments and remove macro elevation.
  231. - If the answer is "整齐得假": vary sentence and paragraph length based on content.
  232. - If the answer is "不像这个文种": rebuild using the document-type template.
  233. - If the answer is "像聊天回复": remove assistant framing and meta-commentary.
  234. ## Positive Rewrite Rules
  235. ### Open with Source and Object
  236. - Weak: `为深入贯彻高质量发展要求,全面开创新局面,现就有关工作通知如下。`
  237. - Better: `根据近期安全检查发现的问题,为规范仓储用电管理,现就开展专项排查有关事项通知如下。`
  238. ### Keep Background Relevant
  239. - Weak: `当前形势深刻复杂,各项工作任务艰巨繁重。`
  240. - Better: `今年以来,窗口咨询量明显增加,群众集中反映办理材料重复提交问题。`
  241. ### Make Problems Concrete
  242. - Weak: `工作中还存在服务意识不强、落实不够有力等问题。`
  243. - Better: `部分窗口一次性告知不够完整,群众补交材料次数偏多,影响办理效率。`
  244. ### Support Achievements
  245. - Weak: `我单位扎实推进各项工作,取得显著成效。`
  246. - Better: `我单位完成〔数量〕个点位改造,新增线上预约入口,平均等候时间较上季度缩短。`
  247. ### Give Deployment Objects and Responsibility
  248. - Weak: `要全面加强管理,持续提升服务水平。`
  249. - Better: `各科室于〔日期〕前完成台账更新,办公室汇总问题清单并跟踪整改进度。`
  250. ### Analyze Causes Beyond Attitude
  251. - Weak: `主要是认识不够、措施不细、落实不力。`
  252. - Better: `主要原因是材料流转依赖人工核对,跨科室数据未共享,导致重复录入和等待时间增加。`
  253. ### Match Measures to Problems
  254. - Weak: `下一步要强化协同、优化机制、提升质效。`
  255. - Better: `针对重复提交问题,统一材料目录,设置线上预审入口,明确窗口一次性告知责任。`
  256. ### Close on the Task
  257. - Weak: `让我们凝心聚力、久久为功,奋力谱写事业发展新篇章。`
  258. - Better: `请各单位结合实际抓好落实,并于〔日期〕前报送工作进展。`
  259. ## Type-Specific Drafting Templates
  260. ### 通知
  261. Purpose: deploy matters or inform requirements.
  262. Structure: basis/background -> matters -> specific requirements -> deadline -> contact/feedback.
  263. Tone: clear, direct, executable.
  264. Avoid: long significance paragraphs, publicity-style elevation, literary opening.
  265. Useful headings: `一、工作事项` `二、具体要求` `三、报送时间`.
  266. ### 请示
  267. Purpose: request approval, instruction, support, or transfer.
  268. Structure: reason -> basis -> difficulty/necessity -> requested matter -> closing.
  269. Tone: cautious, concise, procedure-respecting.
  270. Avoid: writing a work summary, over-praising achievements, macro narrative.
  271. Closing: `妥否,请批示。` or `以上请示如无不妥,请予批复。`
  272. ### 报告
  273. Purpose: report situation, reflect problems, answer inquiry.
  274. Structure: situation -> practices -> results -> problems -> next steps.
  275. Tone: objective and complete; no hidden approval request.
  276. Avoid: only reporting good news; propaganda-style praise.
  277. ### 工作总结
  278. Purpose: review stage work.
  279. Structure: overall situation -> main work -> results/experience -> shortcomings -> next steps.
  280. Tone: realistic.
  281. Avoid: all achievements and slogans. Use data, actions, and cases.
  282. ### 工作方案
  283. Purpose: arrange an implementation path.
  284. Structure: goals -> key tasks -> implementation steps -> division of responsibility -> safeguards.
  285. Tone: concrete and executable.
  286. Avoid: writing as an倡议 or commentary; measures must have enough granularity.
  287. ### 调研报告
  288. Purpose: analyze situation and propose recommendations.
  289. Structure: background -> current situation -> problems -> causes -> recommendations.
  290. Tone: analytical, cautious, evidence-based.
  291. Avoid: empty recommendations. Each recommendation should answer a problem.
  292. ### 讲话稿/发言稿
  293. Purpose: meeting mobilization, deployment, summary, or exchange.
  294. Structure: greeting -> situation/understanding -> key tasks -> implementation requirements -> closing.
  295. Tone: has judgment and mobilization but must land on work.
  296. Avoid: all slogans; overly dense theory concepts.
  297. ### 表态发言
  298. Purpose: express stance and implementation commitment.
  299. Structure: understanding -> attitude -> measures -> commitment.
  300. Tone: firm but not exaggerated.
  301. Avoid: only attitude, no measures.
  302. ### 简报/信息稿
  303. Purpose: quickly reflect dynamics or experience.
  304. Structure: lead -> practices -> stage results -> experience/next step.
  305. Tone: short, factual, fresh.
  306. Avoid: headline-only excitement or empty summary.
  307. ### 宣传稿
  308. Purpose: show典型, policy, activity, or experience to the public.
  309. Structure: scene -> facts -> people/practices -> results -> moderate meaning.
  310. Tone: vivid but measured.
  311. Avoid: excessive praise. Use details instead of admiration.
  312. ### 理论评论文章
  313. Purpose: explain a viewpoint or respond to a problem.
  314. Structure: problem -> judgment -> argument -> facts -> value closing.
  315. Tone: logical, viewpoint-driven.
  316. Avoid: transferring this style back into routine official documents.
  317. ## Useful Openings
  318. - 根据式: `根据〔文件/会议/部署〕要求,为〔目的〕,现就有关事项通知如下。`
  319. - 问题式: `近期,〔问题表现〕。为〔直接目标〕,经研究,决定〔事项〕。`
  320. - 来文式: `你单位《关于〔事项〕的请示》(〔文号〕)收悉。经研究,现批复如下。`
  321. - 汇报式: `现将〔阶段/专项〕工作开展情况报告如下。`
  322. - 函告式: `为〔目的〕,拟〔事项〕。现就有关事项函告如下。`
  323. - 调研式: `围绕〔主题〕,我们采取〔方式〕对〔对象〕开展调研,现将有关情况报告如下。`
  324. ## Useful Closings
  325. - 通知: `请结合实际认真抓好落实,并于〔日期〕前将有关情况报〔单位〕。`
  326. - 请示: `妥否,请批示。` / `以上请示如无不妥,请予批复。`
  327. - 报告: `特此报告。`
  328. - 函: `专此函达,盼复。` / `特此函复。`
  329. - 方案: `各责任单位要按职责分工抓好落实,重要情况及时报告。`
  330. - 倡议书: `让我们从现在做起、从身边做起,共同〔行动目标〕。`
  331. - 宣传稿/讲话稿: may use moderate elevation only when facts support it.
  332. ## Heading Methods
  333. Prefer accurate functional headings over forced parallelism.
  334. - Action + object: `摸清底数,建好台账`
  335. - Problem + measure: `聚焦薄弱环节,抓实整改提升`
  336. - Goal + path: `围绕便民利民,优化服务流程`
  337. - Responsibility + deadline: `压实主体责任,限期完成整改`
  338. - Process + result: `统一受理标准,减少重复提交`
  339. Do not force every heading into four characters or identical rhythm.
  340. ## Internal Scoring Rubric
  341. Score before final delivery:
  342. | Item | Points | High Standard | Low Signal |
  343. | --- | ---: | --- | --- |
  344. | Fact density | 20 | Most paragraphs include object, action, mechanism, data, or case | Mostly slogans and judgments |
  345. | Document-type fit | 20 | Structure, tone, and ending fit type | Notice like speech; request like summary |
  346. | Restraint | 15 | Judgment strength matches evidence | Strong judgment without support |
  347. | Sentence naturalness | 15 | Varied rhythm, little mechanical parallelism | Repeated same structure |
  348. | Abstract-word control | 15 | Abstract terms have concrete follow-up | Dense万能词 |
  349. | Structural clarity | 15 | Paragraph functions clear and progression natural | Logic circles with no new information |
  350. Handling:
  351. - 90+: output directly.
  352. - 80-89: compress boilerplate and strengthen concrete detail.
  353. - 70-79: rewrite affected paragraphs.
  354. - Below 70: rebuild the whole structure.
  355. ## Final Quality Checklist
  356. - Is the document type correct for the relationship and purpose?
  357. - Are issuer, recipient, matter, basis, time, responsibility, and requirement clear?
  358. - Are there invented numbers, policies, leaders, meetings, or approvals? Remove them.
  359. - Is the title consistent with the body?
  360. - Is the main recipient correct? For 请示, is there only one?
  361. - Are attachments, signature, and date consistent when included?
  362. - Does every paragraph have a function?
  363. - Does every abstract judgment have factual support?
  364. - Are there too many `进一步、持续、不断、全面、切实、有效`?
  365. - Are there continuous four-character phrases or repeated `要……要……要……`?
  366. - Does the ending return to办理要求、责任、时限, unless it is truly a speech/publicity article?
  367. - Does the text still contain humanizer tells: significance inflation, fake-depth verb chains, vague attribution, rule-of-three packaging, synonym cycling, meta signposting, or generic positive conclusion?
  368. - Would the draft still make sense if all decorative adjectives, slogans, and transitional announcements were removed?
  369. ## User Input Template
  370. When helpful, infer missing items and proceed. Ask only when missing facts make the document unusable.
  371. ```
  372. 文种:
  373. 使用场景:
  374. 发文/讲话主体:
  375. 面向对象:
  376. 材料要点:
  377. 希望语气:
  378. 篇幅要求:
  379. 是否需要标题:
  380. 是否需要落款:
  381. 特殊要求:
  382. ```
README.md · README · 318 lines
  1. # Official Document Skill V1.3 | 公文写作Skill
  2. <p align="center">
  3. <img src="https://img.shields.io/badge/版本-V1.3-blue" />
  4. <img src="https://img.shields.io/badge/语言-中文-blue" />
  5. <img src="https://img.shields.io/badge/场景-公文写作-green" />
  6. <img src="https://img.shields.io/badge/文种-20+-red" />
  7. <img src="https://img.shields.io/badge/语料-优秀公文案例-yellow" />
  8. </p>
  9. > **让 AI 像体制内笔杆子一样。**
  10. `Official Document Skill` 是一个面向中文公文、政务应用文和机关材料写作的Skill,基于数百篇人民日报等期刊的文章总结而成。它会根据用户提供的文种、场景、对象和材料,生成结构规范、语气稳妥、内容具体、少 AI 味、可直接交付的文本。
  11. V1.2 在原版基础上进一步整合了多篇优秀公文案例、公文写作标准、法定公文格式规则。
  12. V1.3 的新增优化重点是吸收 `humanizer-skill` 的二次审稿思路,专门处理看起来很工整但仍像 AI的问题:意义膨胀、假深刻、模糊主体、规则三连、同义词轮换、元话语和万能结论。
  13. ---
  14. ## 你有没有遇到过这种情况?
  15. 让 AI 写一份工作报告,它经常给出这样的文字:
  16. ```text
  17. 为深入贯彻落实高质量发展要求,进一步凝心聚力、开拓创新、真抓实干,
  18. 我单位持续强化责任担当,不断完善工作机制,全面推动各项工作走深走实、
  19. 提质增效,为谱写新时代事业发展新篇章贡献更大力量。
  20. ```
  21. 看起来很正式,仔细一看却有几个问题:
  22. - 谁负责?做了什么?通过什么机制?到什么节点?有什么结果?
  23. 都没有。
  24. 这就是典型的 **AI 味**:抽象词很多,工作信息很少。
  25. 这个 Skill 要解决的就是这件事:把“正确但空”的文字,改成“具体、稳妥、能用”的公文表达。
  26. ---
  27. ## V1.3 相比原版升级了什么?
  28. ### 1. 升级为公文全流程写作引擎
  29. 原版重点解决 AI 腔、套话、空话问题。V1.3 增加了完整公文生成链路:
  30. ```text
  31. 识别场景 → 判断文种 → 提取事实 → 匹配结构 → 生成正文 → 降 AI 味 → 质量评分 → 交付
  32. ```
  33. 这意味着它不仅会改句子,也会先判断“这到底该写成通知、请示、报告、函,还是方案”。
  34. ### 2. 蒸馏了多篇优秀公文案例和写作标准
  35. 整合了公文写作资料中的法定公文格式、应用文模板、常见文种写法、格式错误、行文关系和交付校对规则。
  36. 新增强化内容包括:
  37. - 通知、请示、报告、批复、函、纪要、通报、决定、通告等法定公文规则;
  38. - 工作方案、工作总结、调研报告、汇报材料、讲话稿、简报、宣传稿等事务文书规则;
  39. - 标题、主送机关、附件、落款、日期、上行文/下行文/平行文的格式约束;
  40. - 请示与报告、通知与通告、批复与复函等易混文种辨析。
  41. ### 3. 整合 100 多篇人民日报文章蒸馏结果
  42. V1.3 吸收了人民日报文章分析中的表达规律,但只保留可迁移到公文写作的部分:
  43. - 事实承接判断;
  44. - 背景不脱离具体任务;
  45. - 问题切入要有真实表现;
  46. - 段落要有明确功能;
  47. - 强判断必须有强证据;
  48. - 普通公文结尾回到责任、时限和办理要求。
  49. 它不会把基层通知写成评论文章,也不会把请示写成宣传稿。
  50. ### 4. 文种覆盖从 11+ 扩展到 20+
  51. V1.3 支持更多实际工作场景:
  52. | 类别 | 支持文种 |
  53. |---|---|
  54. | 法定公文 | 通知、通报、报告、请示、批复、函、纪要、决定、通告、公告、意见、议案 |
  55. | 事务文书 | 工作方案、工作计划、工作总结、调研报告、汇报材料、简报/信息稿 |
  56. | 会议材料 | 讲话稿、发言稿、表态发言、经验材料 |
  57. | 面向公众 | 倡议书、公开信、感谢信、宣传稿、信访回复、政策解读 |
  58. | 评论类 | 理论评论文章,但会严格限制其向普通公文迁移 |
  59. ### 5. V1.3 新增:humanizer 二次审稿
  60. V1.3 在原有公文规则之外,新增一轮内部提问:
  61. ```text
  62. 如果这篇公文被退回,最可能被批评哪里像 AI 写的?
  63. ```
  64. 重点检查:
  65. - 意义膨胀:普通事项被写成“重要里程碑”“充分彰显”;
  66. - 假深刻:一句话后面连续接“推动、促进、助力、彰显”;
  67. - 模糊主体:只写“相关部门”“有关方面”,没有责任对象;
  68. - 规则三连:所有段落都强行写成三项并列;
  69. - 同义词轮换:为了避免重复,把同一主体反复换称呼;
  70. - 元话语:出现“下面从三个方面展开”“接下来我们来看”;
  71. - 万能结论:结尾回到“谱写新篇章”,而不是责任、时限、报送要求。
  72. ---
  73. ## 它能做什么?
  74. ### 1. 从零生成公文
  75. 例如:
  76. ```text
  77. 用 $official-document-skill 写一份通知:区教育局通知各学校开展暑期校园安全排查,
  78. 重点查消防、用电、食堂、实验室危化品,6月30日前报送隐患台账。
  79. ```
  80. Skill 会自动判断这是“通知”,重点写清对象、事项、要求、时限,而不是写成宣传稿。
  81. ### 2. 把口语材料转成正式公文
  82. 你可以直接给会议记录、工作要点、零散材料,它会整理成正式结构。
  83. ### 3. 降 AI 味、压缩套话
  84. 典型改写方向:
  85. | AI 味表达 | V1.3 改写方向 |
  86. |---|---|
  87. | 凝心聚力、开拓创新 | 写清参与主体和共同目标 |
  88. | 强化责任担当 | 明确责任单位、责任人、完成时限 |
  89. | 走深走实、提质增效 | 写清落实到哪个环节、产生什么变化 |
  90. | 形成闭环机制 | 写清发现、办理、反馈、复盘步骤 |
  91. | 谱写新篇章 | 回到下一步任务、报送节点或工作目标 |
  92. ### 4. 检查文种和格式
  93. 它会识别这些常见问题:
  94. - 报告里夹带请示事项;
  95. - 请示多头主送;
  96. - 通知写成讲话稿;
  97. - 函写成命令;
  98. - 标题文种和正文目的不一致;
  99. - 提到附件但没有附件说明;
  100. - 结尾过度宏大,脱离办理事项。
  101. ---
  102. ## 看一个简短例子
  103. 原句:
  104. ```text
  105. 我单位高度重视窗口服务工作,持续推进服务能力提升,全面优化服务流程,
  106. 不断增强群众满意度,推动政务服务提质增效。
  107. ```
  108. V1.3 改写:
  109. ```text
  110. 我单位〔具体会议/部署名称〕后,〔数量〕周内完成〔事项,如综合窗口整合/材料清单梳理〕。
  111. 主要做了三方面工作:一是将〔原流程节点〕与〔新流程节点〕打通,减少群众跑动次数;二是将〔材料名称〕由〔原数量〕项压减至〔现数量〕项,并设置线上预审入口;三是前台窗口统一实行一次性告知,后台数据实时共享,避免群众重复提交。
  112. 调整后,〔窗口/事项〕平均办理时间由〔原时长〕缩短至〔现时长〕,群众现场补交材料情况明显减少。下一步将根据试运行反馈继续调整,重点解决〔具体问题,如跨区数据互通/老年人辅助办理〕。
  113. 需补充信息:
  114. 上述占位符中的具体动作、数据、事项名称(如无准确数据,可先以范围值标示并在成文前核实)。
  115. 是否需要写进制度名称、牵头科室、技术平台名称。
  116. ```
  117. 区别在于:
  118. | 原句问题 | 改写动作 |
  119. |---|---|
  120. | “高度重视”没有信息 | 删除空泛表态 |
  121. | “持续推进”没有宾语 | 改成具体环节 |
  122. | “提质增效”没有证据 | 改成减少重复提交、等待时间 |
  123. | 抽象判断多 | 增加对象、动作、机制 |
  124. ---
  125. ## 四项核心能力
  126. ### 1. 文种识别
  127. 先判断文种,再匹配结构。
  128. | 用户意图 | 推荐文种 |
  129. |---|---|
  130. | 要求下级办理、告知事项 | 通知 |
  131. | 向上级请求批准、支持、经费 | 请示 |
  132. | 向上级汇报情况、进展、问题 | 报告 |
  133. | 不相隶属单位商洽、询问、答复 | 函 |
  134. | 答复下级请示 | 批复 |
  135. | 安排专项行动 | 工作方案 |
  136. | 复盘阶段工作 | 工作总结 |
  137. | 分析情况并提出建议 | 调研报告 |
  138. | 会议动员部署 | 讲话稿 |
  139. | 快速反映动态 | 简报 / 信息稿 |
  140. ### 2. 事实密度增强
  141. V1.3 会优先补足七个维度:
  142. ```text
  143. 谁负责 → 做什么 → 针对什么问题 → 通过什么机制 → 到什么时间完成 → 如何反馈 → 有什么结果
  144. ```
  145. ### 3. 语气克制
  146. 到什么程度,说什么话。
  147. | 表达强度 | 使用条件 |
  148. |---|---|
  149. | 已启动、正在开展 | 只有部署或起步动作 |
  150. | 有序推进、稳步推进 | 有计划、有步骤,但结果有限 |
  151. | 取得进展、初见成效 | 有阶段性结果或对象反馈 |
  152. | 取得明显成效、形成机制 | 有数据、制度、流程或稳定运行 |
  153. | 重大突破、历史性成就 | 有权威认定、关键指标、行业比较或重大节点 |
  154. ### 4. Humanizer 二次审稿
  155. 这一轮追求不像模型自动生成。
  156. | 二次审稿项 | 怎么改 |
  157. |---|---|
  158. | 意义膨胀 | 把“重要意义”改成具体任务、结果或依据 |
  159. | 假深刻动词链 | 保留一个主动作,补对象和流程 |
  160. | 模糊归因 | 写清来源、反馈渠道或删去 |
  161. | 规则三连 | 按实际任务数量分条,不强凑三点 |
  162. | 同义词轮换 | 重复最准确的主体名称 |
  163. | 元话语 | 删除“下面是”“接下来”等说明 |
  164. | 万能结尾 | 回到责任、时限、报送和下一步 |
  165. ---
  166. ## 一分钟快速测试
  167. 把下面这段复制给已加载 Skill 的 AI:
  168. ```text
  169. 用 $official-document-skill 写一份基层安全检查整改情况报告,要求正式、克制、去 AI 味,不要写成宣传稿。
  170. 文种:整改情况报告
  171. 使用场景:街道向区应急管理局报送安全检查整改情况
  172. 发文主体:XX街道办事处
  173. 面向对象:区应急管理局
  174. 材料要点:
  175. 1. 6月初,区应急管理局对XX街道辖区内沿街商铺、老旧小区、出租屋和小型仓储场所开展安全检查;
  176. 2. 检查发现部分沿街商铺存在灭火器过期、消防通道堆放杂物、电线私拉乱接等问题;
  177. 3. 个别老旧小区楼道内停放电动自行车,存在充电安全隐患;
  178. 4. 部分出租屋未按要求配备烟感报警器;
  179. ```
  180. 合格输出应当:
  181. - 写成“报告”,不是宣传稿;
  182. - 有主送机关;
  183. - 如实写整改进展和存在问题;
  184. - 下一步安排可执行;
  185. - 不用“谱写新篇章”等万能结尾。
  186. ---
  187. ## 内置评分
  188. 生成后按六个维度自检:
  189. | 维度 | 分值 | 看什么 |
  190. |---|---:|---|
  191. | 事实密度 | 20 | 有对象、动作、机制、数据或案例吗? |
  192. | 文种适配 | 20 | 结构、语气、结尾符合文种吗? |
  193. | 语气克制 | 15 | 判断强度和证据匹配吗? |
  194. | 句式自然 | 15 | 是否机械排比、句式单一? |
  195. | 抽象词控制 | 15 | 抽象词后是否有具体承接? |
  196. | 结构清晰 | 15 | 段落功能是否明确,推进是否自然? |
  197. 附加 humanizer 检查:是否仍有意义膨胀、假深刻、模糊主体、规则三连、同义词轮换、元话语、万能结论。如果有,先修再交付。
  198. 处理规则:
  199. | 分数 | 处理 |
  200. |---|---|
  201. | 90 分以上 | 可直接输出 |
  202. | 80—89 分 | 局部压缩套话并增强具体性 |
  203. | 70—79 分 | 重写问题段落 |
  204. | 70 分以下 | 按文种结构整体重构 |
  205. ---
  206. ## 文件结构
  207. ```text
  208. official-document-skill/
  209. ├─ SKILL.md # V1.3 核心规则,已整合为单文件
  210. ├─ README.md # 说明、能力、升级点
  211. ├─ examples.md # 示例输入输出
  212. ├─ tests.md # 人工回归测试
  213. ```
  214. ---
  215. ## 设计理念
  216. V1.3 的核心是让文本回到机关材料最朴素的标准:
  217. > **文种对、事实实、结构清、语气稳、责任明、结尾落地。**
  218. 人民日报语料提供的是表达规律,不是可复制的套话;优秀公文案例提供的是结构标准,不是机械模板。真正可交付的公文,最后一定要落到具体工作。

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.