Claude Code Plugins

Community-maintained marketplace

Feedback

chinese-official-document-writing

@Bubu1117/chinese-official-document-writing-skill
0
25

Draft, revise, and review Chinese official documents, including notices, requests for instructions, reports, letters, meeting minutes, work plans, summaries, and implementation plans. Use when Codex needs to write formal Chinese public-sector, university, institute, company administration, or Party/government-style documents; convert rough notes into a compliant draft; polish tone and structure; choose the right document type; or check titles, headings, dates, attachments, addressees, and official-document wording.

Install Skill

Shared

Installs to .agents/skills, used by Codex, Amp, Warp, Cursor, OpenCode, and more.

CodexAmp
Warp
CursorOpenCode
Cline
Gemini CLI
GitHub Copilot
Personal

Available across projects.

$npx skills-installer add @Bubu1117/chinese-official-document-writing-skill/chinese-official-document-writing --client shared
Project

Writes to .agents/skills.

$npx skills-installer add @Bubu1117/chinese-official-document-writing-skill/chinese-official-document-writing -p --client shared
Note: Review the skill instructions before using it.

SKILL.md

name chinese-official-document-writing
description Draft, revise, and review Chinese official documents, including notices, requests for instructions, reports, letters, meeting minutes, work plans, summaries, and implementation plans. Use when Codex needs to write formal Chinese public-sector, university, institute, company administration, or Party/government-style documents; convert rough notes into a compliant draft; polish tone and structure; choose the right document type; or check titles, headings, dates, attachments, addressees, and official-document wording.

Chinese Official Document Writing

Core Workflow

Use this skill to turn scattered facts into a formal Chinese document that is accurate, restrained, and easy for a real office to revise.

  1. Identify the document type before drafting. If the user only says "写个材料", infer from purpose: announce work with a notice, request approval with a request for instructions, report completed work with a report, coordinate with another unit through a letter, and record decisions with meeting minutes.
  2. Collect the minimum facts: issuing unit, recipient, purpose, background, basis, tasks, deadlines, responsible parties, attachments, contact person, and desired date. If a fact is missing but drafting can continue, use 【待补充】 instead of inventing it.
  3. Draft in the common structure for the chosen document type. Keep the main point early, then arrange basis, matter, requirements, and closing.
  4. Polish for official tone. Prefer concise, accountable wording; remove slogans that do not add instructions; avoid exaggerated claims.
  5. Run the review checklist before final output. Flag any uncertainty, missing approval basis, or possible mismatch between document type and purpose.

Reference Loading

Load only the reference needed for the task.

  • Read references/document-types.md when choosing or explaining the document type.
  • Read references/style-and-format.md when checking title, hierarchy, addressee, dates, attachments, or official wording.
  • Read references/drafting-templates.md when drafting a common document from scratch.
  • Read references/review-checklist.md before returning a final version or a revision note.

Drafting Rules

  • Keep facts separable from phrasing. Never create policy basis, approval results, meeting decisions, names, dates, or statistics that the user did not provide.
  • Use placeholders such as 【发文单位】, 【日期】, and 【待补充】 for missing concrete information.
  • Prefer "请于...前完成" over vague wording such as "尽快落实"; prefer "现将有关事项通知如下" over decorative openings.
  • Use one document for one main matter. For a request for instructions, write one issue and one request; do not mix unrelated requests.
  • Do not put approval requests inside a report. If the text asks the superior unit to approve something, choose 请示.
  • For public-facing or formally issued documents, remind the user to verify the local format, document number, seal, distribution scope, and internal approval process.

Output Pattern

For a normal drafting task, return:

  1. 文种判断 with one short reason.
  2. 正文草稿 as a clean draft.
  3. 待确认事项 listing missing facts or risky assumptions, if any.

For a revision task, return:

  1. 主要修改 summarizing structural and wording changes.
  2. 修改稿 as the revised document.
  3. 校核提示 for unresolved facts or format details.

Templates

Use the Markdown templates in assets/templates/ when the user asks for a quick draft that can be filled in later. Keep placeholders visible instead of silently deleting missing fields.