doc-type-routing
A decision framework for selecting the correct Chinese formal document type before drafting.
Install
mkdir -p .claude/skills/doc-type-routing && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16368" && unzip -o skill.zip -d .claude/skills/doc-type-routing && rm skill.zipInstalls to .claude/skills/doc-type-routing
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
在起草前判定「该用哪个文种、什么行文方向」。Use when 不确定该写通知/报告/请示/函/通报/意见/决定…，或需要判断上行/下行/平行/公开、要不要对方回复。按「行文方向＋目的＋是否需回应」三维收敛到正确文种，再交给「公文写作」起草。是流程第一步的判定脚手架，不生成正文。Key capabilities
- →Determine the correct document type (e.g., notice, report, request)
- →Identify the appropriate writing direction (upward, downward, parallel, public)
- →Assess whether a response is required from the recipient
- →Route to the correct document type based on direction, purpose, and response need
- →Differentiate between easily confused document types like reports vs. requests
How it works
It uses a three-dimensional method (writing direction, purpose, response requirement) to converge on the correct document type, acting as a routing scaffold before drafting begins.
Inputs & outputs
When to use doc-type-routing
- →Identify if a draft should be a report or a request
- →Determine if a document requires a response
- →Route a request to the correct formal writing agent
About this skill
文种与行文方向判定
公文写作最易错、又最该先定的第一步：选错文种，后面写得再好也白搭（报告写成请示、函写成通知、决定与决议混用）。本 skill 把这一步结构化，判定后再交给根 SKILL.md（公文写作）起草。
文件索引
prompts/core/workflow.md # 判断流程与文种路由规则（主源）
prompts/core/drafting-thinking.md # 易混文种三维辨析、行文方向与谋篇对应（主源）
docs/references/document-types.md # 各文种适用场景与边界说明（读者文档）
三维判定法
- 行文方向：上行（向上级）／下行（向下级）／平行或不相隶属／对外公开。
- 目的：请求批准、汇报情况、部署执行、答复、告知、商洽、记载、提请审议、公布。
- 是否需对方回应：需批复（请示）、需审议（议案）、本身即回应（批复／复函）、不强制（报告／通知／通报）。
三者一旦确定，文种基本唯一收敛。
快速路由
- 请求上级批准 → 请示（一文一事、只主送一个上级，结尾「妥否，请批示」）
- 答复下级请示 → 批复（先引来文标题与文号）
- 向上级汇报、不要求回复 → 报告（不夹带请批事项）
- 部署/传达执行、批转转发 → 通知
- 提原则与办法 → 意见；重大决断/奖惩 → 决定；会议表决通过 → 决议
- 不相隶属或平行机关商洽/询问/答复/请批准 → 函
- 对外宣布重要或法定事项 → 公告；一定范围须遵守事项 → 通告
- 会议议定事项 → 纪要；政府向同级人大提请审议 → 议案
- 整理新闻动态/专题情况（非法定公文）→ 简报／情况专报／汇报材料
高频易错辨析
- 报告 vs 请示：报告汇报、不要回复、可综合；请示请批准、必须等批复、一文一事。报告内不得夹带请批事项。
- 决定 vs 决议：决定可机关直接作出；决议必经会议表决、以会议名义发布。
- 通报 vs 通告：通报对内（表彰/批评/告知）；通告对外（公布须遵守事项、带强制）。
- 公告 vs 通告：公告对国内外宣布重要/法定事项、机关层级较高；通告面向一定范围。
- 函 vs 通知/请示：不相隶属或平行机关一律用函，不因事项重要升格。
无 agent 环境（网页/离线）
- 本 skill 是纯判定、不联网，其判据全部来自
prompts/core/workflow.md与prompts/core/drafting-thinking.md，而这两份已整体内联进离线系统提示词。 - 因此无 agent/skill 环境时无需额外操作：粘贴 dist/offline/default/system_prompt.md即已包含文种与行文方向判定指引，可直接让模型先判文种再起草。
边界
- 只做文种与方向判定，不生成正文；判定后交「公文写作」按对应
spec.md起草。 - 判据一律以
prompts/core/workflow.md、prompts/core/drafting-thinking.md主源为准，本 skill 不复制规则。 - 成稿后若要核对文种、结尾用语、章节是否齐全，转
document-qa（src/scripts/check_sections.py）。
When not to use it
- →When generating the main body of the document
- →When the document type and writing direction are already clear
- →When checking the completeness of a drafted document
Limitations
- →Only performs document type and direction determination
- →Does not generate the main body of the document
- →Does not check for completeness of a drafted document
How it compares
This skill systematically determines the precise document type and writing direction based on specific criteria, preventing common errors in formal writing by establishing the correct framework before any content is generated.
Compared to similar skills
doc-type-routing side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| doc-type-routing (this skill) | 0 | 1mo | No flags | Beginner |
| docs-write | 22 | 6mo | No flags | Beginner |
| content-research-writer | 15 | 10mo | No flags | Beginner |
| doc-coauthoring | 16 | 8mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
docs-write
metabase
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
content-research-writer
ComposioHQ
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
doc-coauthoring
anthropics
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
research-grants
davila7
Write competitive research proposals for NSF, NIH, DOE, and DARPA. Agency-specific formatting, review criteria, budget preparation, broader impacts, significance statements, innovation narratives, and compliance with submission requirements.
teams-channel-post-writer
daymade
Creates educational Teams channel posts for internal knowledge sharing about Claude Code features, tools, and best practices. Applies when writing posts, announcements, or documentation to teach colleagues effective Claude Code usage, announce new features, share productivity tips, or document lessons learned. Provides templates, writing guidelines, and structured approaches emphasizing concrete examples, underlying principles, and connections to best practices like context engineering. Activates for content involving Teams posts, channel announcements, feature documentation, or tip sharing.
write-docs
tldraw
Writing SDK documentation for tldraw. Use when creating new documentation articles, updating existing docs, or when documentation writing guidance is needed. Applies to docs in apps/docs/content/.