Agent skill

Writing

by 312362115 in 312362115/claude

通用写作技能:以"内容→组件→组合"的方式产出技术文档、产品文档、汇报材料. An agent skill from 312362115/claude.

MITAuto-check passedProduct & Project Management

Install Writing

skills CLI
$ npx skills add 312362115/claude --skill writing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 312362115/claude writing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/312362115/claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing .claude/skills/writing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
writing
GitHub stars
107
Token cost
~1.6k tokens
SKILL.md length
449 words
Files
11 (incl. references)
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

通用写作技能:以"内容→组件→组合"的方式产出技术文档、产品文档、汇报材料. An agent skill from 312362115/claude.

  • Works in 6 steps: 决定基调:浅色阅读型(report-template.html)还是深色路演型(t… → Read 对应的组件示例 HTML 文件(看可用类名) → 按 components.md 挑组件、按内容组装 → …
  • Tasks that involve PRD writing
  • SKILL.md covers 核心理念:组件驱动,不预设模板, 第一步:理解内容, 第二步:选组件 and 第三步:参考组合范式(可选), plus 6 more sections
  • Calls git

What it does

Writing is an agent skill from 312362115/claude. 通用写作技能:以"内容→组件→组合"的方式产出技术文档、产品文档、汇报材料。 覆盖 spec / plan / PRD / 用户手册 / 项目汇报 / 方案路演 / 调研报告 等所有结构化文档场景。 核心理念:组件驱动,不预设模板。先看内容形态,再挑能装这种形态的组件, 组合自然成文——不强制章节结构、不预设"必备模块"。 组件库(HTML / Markdown / 图示)见 references/components.md, 常见组合范式(spec / plan / PRD 等)见 references/templates/——但模板是参考不是规定。 触发词:写文档、写方案、写计划、写 PRD、写汇报、项目总结、写指南、帮我写、文档、方案设计。 即使用户没有明确说"写",只要意图是"产出一份结构化的文档/报告/材料",都应触发此技能。 本 skill 只负责"写",不负责"调研"(调研由 deep-research 承担)和"调度"(流程由 task-start 承担)。

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `references/components.md`, `references/templates/api-doc.md` and `references/templates/dev-guide.md`).

It sits in Product & Project Management, covering PRD writing and Deep research. The licence is MIT.

When your agent uses it

  • Tasks that involve PRD writing
  • Tasks that involve Deep research

Example prompts

  • “内容→组件→组合”
  • “,只要意图是”
  • “,都应触发此技能。 本 skill 只负责”
  • “/writing”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. 决定基调:浅色阅读型(report-template.html)还是深色路演型(templates/report-pitch.html)——也可以混合
  2. Read 对应的组件示例 HTML 文件(看可用类名)
  3. 按 components.md 挑组件、按内容组装
  4. 调 diagram skill 生成图表(评审场景图带标题,文档配图不带——见 diagram skill)
  5. Write 输出
  6. open 命令打开供 review

What it can do on your machine

Read from SKILL.md and the folder at commit 2d4fa49. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Writing loads about 1.6k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 113 tokens; SKILL.md has 449 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~113
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~15k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 312362115/claude at commit 2d4fa49, republished under its MIT licence (© 312362115). 449 words, ~1,601 tokens.

Download SKILL.mdSave it as .claude/skills/writing/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
writing
description
通用写作技能:以"内容→组件→组合"的方式产出技术文档、产品文档、汇报材料。 覆盖 spec / plan / PRD / 用户手册 / 项目汇报 / 方案路演 / 调研报告 等所有结构化文档场景。 核心理念:组件驱动,不预设模板。先看内容形态,再挑能装这种形态的组件, 组合自然成文——不强制章节结构、不预设"必备模块"。 组件库(HTML / Markdown / 图示)见 references/components.md, 常见组合范式(spec / plan / PRD 等)见 references/templates/——但模板是参考不是规定。 触发词:写文档、写方案、写计划、写 PRD、写汇报、项目总结、写指南、帮我写、文档、方案设计。 即使用户没有明确说"写",只要意图是"产出一份结构化的文档/报告/材料",都应触发此技能。 本 skill 只负责"写",不负责"调研"(调研由 deep-research 承担)和"调度"(流程由 task-start 承担)。
version
2.0.0
last_updated
2026-05-07
repository
https://github.com/312362115/claude

通用写作(Writing)

知道了什么,和让别人也知道,是两种完全不同的能力。 本 skill 是后者——把已有的知识、决策、进展,变成不同读者能看懂、愿意看的文档。


核心理念:组件驱动,不预设模板

写作不是"按模板填空",而是"把内容装进合适的组件、组合成文档"。

传统模板派:先选模板(spec / PRD / 汇报)→ 模板说必备 X 章节 → 内容硬塞进去
本 skill:先看内容形态 → 挑能装这种形态的组件 → 自然组合

为什么不再用"模式 → 模板"?

  • 真实内容很少正好匹配某个模板(比如同一份汇报里既有数据又有架构方案)
  • 模板的"必备章节"会让简单内容膨胀、复杂内容装不下
  • 写作的核心判断是"这段内容长什么样、用什么组件能讲清楚",模板分类只是干扰

核心资源:

  • references/components.md — 写作组件库(HTML / Markdown / 图示组件)。这是本 skill 最重要的索引文件
  • references/templates/*.md — 常见组合范式(spec / plan / PRD 等)。是参考,不是规定
  • references/report-template.html — 浅色阅读型 HTML 报告组件示例集
  • references/templates/report-pitch.html — 深色路演型 HTML 报告组件示例集

第一步:理解内容

收到写作请求后,先理解内容长什么样——不是先选"写哪种文档"。

1.1 内容形态分析

问自己以下问题(已知的跳过,模糊的追问用户):

问题影响
要表达的核心是什么?决定主线(决策?过程?数据?说明?)
读者是谁?决定用词深度和可视化程度(开发者 / 产品 / 用户 / 评审人 / 上级)
读者读完要做什么?理解?决策?执行?检查?追责?
内容含哪些"形态"?决策?数字?流程?对比?时间线?架构?API 接口? — 决定调哪些组件
篇幅预期?简短摘要?完整报告?投屏材料?
存放位置?docs/ 哪个子目录?(按 CLAUDE.md 规范)
1.2 输出格式判断
内容/读者特征推荐格式
开发者读、能跑能用Markdown
内部协作、需要 git 跟踪Markdown
需要投屏 / 路演 / 对外宣讲HTML(深色路演型)
季度复盘 / 数据汇报HTML(浅色阅读型)
内含大量统计图 / 富视觉HTML
用户帮助文档 / 用户手册Markdown 或 HTML(看用户偏好)

HTML 不再硬分"汇报型 vs 路演型"——同一份 HTML 可以混合 Hero(路演风)+ Metric-Card(数据)+ Figure(架构图)。看内容选组件,不看"汇报子模式"。

1.3 与用户对齐(仅当模糊时)

把你的理解告诉用户,让用户确认或修正:

我的理解:
- 内容核心:xxx
- 读者:xxx
- 形态识别:含决策(3-4 项)/ 架构图(2 张)/ 风险点(5 个)
- 推荐格式:HTML(路演风格 + 数据指标混合)
- 存放:docs/reviews/

确认开始?

简单明确的需求("帮我写个 spec 改造 session 模块")跳过对齐,直接进下一步。


第二步:选组件

根据 1.1 识别出的内容形态,到 references/components.md 查找对应组件。

速查表(完整版见 components.md 的"H. 组合速查"):

内容形态推荐组件
一屏建立全局认知Hero + Pill + TOC
章节扫读section-head + summary
一张图说清楚Figure
并列同质项Card-Grid
A vs B 二选一VS-Block
结构化对照表格
时间维度 / 阶段Timeline
已选/待观察/风险Decision-Card 三色
关键数字Metric-Card
0-100% 进度Progress-Bar
维度评分Score-Bar
重要提示打断Callout
行内状态标注Badge
嵌入统计图Chart-Container
≤ 10 节点的轻量流程```flow 代码块
CLI 命令演示```terminal 代码块

组件选择原则:

  • 同样的内容能用更轻的组件就用更轻的(能用列表别用 grid,能用 grid 别用 vs-block)
  • 组件存在是为了表达内容,不是为了视觉好看——没有对应内容就别用对应组件
  • 单一文档内组件不要堆叠超过 8-10 种,会变成"组件展示馆"

第三步:参考组合范式(可选)

references/templates/*.md 下有几份常见组合范式——某些类型的文档历史上常用什么章节顺序。这是参考不是规定:

文件何时参考
spec.md写技术方案——需要"背景 → 调研 → 决策 → 技术方案"骨架时
plan.md写开发计划——需要"关联方案 + 子任务 checklist"骨架时
api-doc.md写 API 文档——需要"概览 / 认证 / 接口列表 / 错误码"骨架时
dev-guide.md写开发指南——需要"前置条件 / 环境搭建 / 操作步骤 / 常见问题"骨架时
prd.md写 PRD——需要"用户场景 / 功能描述 / 验收标准"骨架时
operation-plan.md写运营方案——需要"目标 / 策略 / 执行 / 评估"骨架时
user-guide.md写用户手册——需要"快速开始 / 核心功能 / 操作步骤"骨架时

借鉴方式:

  • 内容跟范式贴合 → 借鉴章节顺序
  • 内容只覆盖部分 → 删掉用不到的章节,不要硬写
  • 内容超出范式 → 自由加章节
  • 章节存在的理由必须是"内容需要它",不是"模板要求它"

不参考也行——内容形态清晰时直接进第四步。


第四步:素材就位

动笔前确认素材是否充足:

素材来源获取方式
代码 / 配置Read / Grep 读取项目文件
Git 历史git log 查看变更记录
已有文档读取 docs/ 下相关文档
项目数据用户提供或从 BI/监控获取
调研结论引用 deep-research 的输出
复盘记录读取 docs/decisions/

素材不足时:主动告知用户缺少什么信息,不要编造。如果需要调研,引导用户使用 deep-research skill。


第五步:撰写

按"组件 + 内容"组合输出。遵循以下通用准则:

5.1 通用写作准则
  • 中文为主:正文中文,代码 / 命令 / 专有名词保留英文
  • 措辞精确:避免"大概""好像""可能"等模糊用语
  • 数据优先:能用数据说明的不用形容词
  • 结构服务内容:表格 / 列表 / 卡片是为了表达更清楚,不是为了好看
  • 篇幅自适应:根据内容复杂度自然决定篇幅,不人为压缩也不注水
  • 图表有效:需要图表调 diagram skill 生成;简单流程用 ```flow 代码块;调用关系超过 5 个节点才考虑流程图
Show full SKILL.md (178 more words)Show less
5.2 按读者类型微调
读者关键点
开发者准确 > 优美;可执行 > 可读;命令 / 代码 / API 路径精确到版本
产品 / 运营用户语言 > 技术语言;场景驱动;不遗漏边界(空状态、错误状态)
用户 / 客户零术语;步骤可照做;常见问题按频率排序
评审人 / 上级结论先行;图为主、文字为注脚;风险前置;行动明确
5.3 HTML 报告写作流程
  1. 决定基调:浅色阅读型(report-template.html)还是深色路演型(templates/report-pitch.html)——也可以混合
  2. Read 对应的组件示例 HTML 文件(看可用类名)
  3. 按 components.md 挑组件、按内容组装
  4. 调 diagram skill 生成图表(评审场景图带标题,文档配图不带——见 diagram skill)
  5. Write 输出
  6. open 命令打开供 review
5.4 Markdown 文档写作流程
  1. 按 1.1 识别内容形态 → 选组件(多数 MD 组件 = 表格 / 列表 / 标题 / 代码块)
  2. (可选)参考 references/templates/*.md 找组合范式
  3. 直接写
  4. 调 preview-md skill 在浏览器预览

第六步:质量自检

写完后自动执行以下检查:

#检查项说明
1内容覆盖1.1 识别出的所有形态都有对应组件承载?没有"忘记装的内容"?
2组件适配用的组件是否真适合内容(不是为了好看硬塞)?
3读者适配用词和深度匹配目标读者?技术文档不废话,产品文档不用术语
4信息准确引用的文件路径、版本号、数据是否和当前代码 / 事实一致?
5可操作性技术文档中的步骤能否直接执行?汇报中的行动项是否明确?
6格式规范文件命名、存放位置是否符合 CLAUDE.md 文档规范?
7组件克制是否堆叠了过多组件让文档变成"展示馆"?该删的删

自检发现问题直接修复,不需要告知用户。


第七步:交付

内容类型输出路径交付方式
技术方案 / 计划 / 指南docs/specs/ docs/plans/ docs/guides/写完后调 preview-md 预览
产品文档docs/prds/ docs/guides/写完后调 preview-md 预览
汇报 / 路演 / 评审 HTML用户指定或 docs/reports/ docs/reviews/同级建 assets/ 存图,写完后 open 打开 HTML

与其他 skill 的关系

deep-research → 调研结论 → writing(把调研写成文档)
tech-evaluation → 选型结论 → writing(把选型写成方案)
task-start → 对焦结论 → writing(写 spec / plan)
task-finish → 复盘结论 → writing(写 decisions / 汇报)

writing 调用:
  ← diagram skill(生成图表嵌入文档)
  ← preview-md skill(Markdown 文档预览)

边界划分:

  • writing vs deep-research:deep-research 负责"搞清楚"(调研过程),writing 负责"写清楚"(文档产出)。deep-research 内部的报告撰写是调研流程的一部分,writing 不接管
  • writing vs task-start:task-start 负责"什么时候需要写 spec/plan"(流程调度),writing 负责"怎么写好"(写作质量)

反模式

  • ❌ 先选"写哪种文档"再填模板——应该先看内容形态再选组件
  • ❌ 因为模板说"必备章节"就硬写——章节存在的理由是内容需要它
  • ❌ 因为有 hero 组件就给所有 HTML 加 hero——内部 spec 不需要 hero
  • ❌ 因为有 decision-card 三色就把普通结论包成 decision——decision 是为"已决/未决/风险"三态信号化设计的
  • ❌ 因为有 metric-card 就编数字凑指标——没数字就别用
  • ❌ 单一文档堆叠 ≥ 10 种组件——变成"组件展示馆"
  • ❌ 把"组合范式"误读为"必备模板"——templates/*.md 是参考不是规定

© 312362115, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in skills/writing of 312362115/claude.

  • SKILL.md
  • references/components.md
  • references/report-template.html
  • references/templates/api-doc.md
  • references/templates/dev-guide.md
  • references/templates/operation-plan.md
  • references/templates/plan.md
  • references/templates/prd.md
  • references/templates/report-pitch.html
  • references/templates/spec.md
  • references/templates/user-guide.md

Open the folder on GitHubat commit 2d4fa49

Compare with similar skills

Writing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Writing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Writing this skill312362115/claude107—~1.6kAutomated safety check: PassMIT
Tdoctornado-doc/tdoc103—~18kAutomated safety check: NotesAGPL-3.0
Expand Tasksanombyte93/prd-taskmaster605—~2kAutomated safety check: NotesMIT
Idea Ossickn33/agentic-awesome-skills47k1 repos~1.5kAutomated safety check: PassMIT
Product Managerstaruhub/ClaudeSkills727—~2.1kAutomated safety check: PassMIT
Greenfieldwednesday-solutions/ai-agent-skills170—~914Automated safety check: PassMIT

Similar skills

  • Tdoc

    tornado-doc/tdoc

    Use tdoc by default to create, edit, publish, or share any document, even when tdoc is not mentioned.

    103 GitHub stars~18k tokensUpdated yesterday
    Product & Project ManagementAuto-check: notes
  • Expand Tasks

    anombyte93/prd-taskmaster

    Expand all TaskMaster tasks with deep research before coding begins.

    605 GitHub stars~2k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check: notes
  • Idea Os

    sickn33/agentic-awesome-skills

    Five-phase pipeline (triage → clarify → research → PRD → plan) that turns a raw idea into four linked files: clarifying questions, deep research, a PRD with non-goals and metrics, and a phased…

    47k GitHub starsUsed in 1 repo~1.5k tokens
    Product & Project ManagementAuto-check passed
  • Product Manager

    staruhub/ClaudeSkills

    资深产品经理助手,提供 PRD/MRD/BRD 创作与评审、产品策略、留存增长、竞品分析、功能优先级,以及 grill-me-to-doc 逐轮访谈。用户要求“逐个问我”“先把需求问清楚”“grill me”“把想法变成产品文档”时进入 grill-me-to-doc:先读仓库证据,每轮只问一个决策,给推荐答案与理由,记录决策和未决项,支持 resume,产出结构化…

    727 GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Greenfield

    wednesday-solutions/ai-agent-skills

    Parallel persona planning for new projects. An agent skill from wednesday-solutions/ai-agent-skills.

    170 GitHub stars~914 tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed
  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

More from 312362115/claude

All 20 skills in this repo
  • Diagram

    312362115/claude

    专业图表生成技能:根据需求自动选择合适的图表类型,生成符合设计规范的 PNG 图表. An agent skill from 312362115/claude.

    107 GitHub stars~2.7k tokensUpdated 4 mo ago
    Auto-check passed
  • Deep Research

    312362115/claude

    深度调研技能:对任意命题进行系统性调研并输出专业研究报告. An agent skill from 312362115/claude.

    107 GitHub stars~6.6k tokensUpdated 4 mo ago
    Auto-check passed
  • Preview Md

    312362115/claude

    MD 文件浏览器预览:GitHub 风格渲染 + 左侧自动目录. An agent skill from 312362115/claude.

    107 GitHub stars~636 tokensUpdated 4 mo ago
    Auto-check passed
  • Code Walkthrough

    312362115/claude

    代码导读技能:帮助快速理解不熟悉的项目或模块,建立心智模型. An agent skill from 312362115/claude.

    107 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check: notes
  • DB Review

    312362115/claude

    数据库代码审查 + Migration 安全检查. An agent skill from 312362115/claude.

    107 GitHub stars~1.8k tokensUpdated 4 mo ago
    Auto-check passed
  • Dependency Map

    312362115/claude

    依赖关系分析技能:回答"改这里会影响哪里". An agent skill from 312362115/claude.

    107 GitHub stars~888 tokensUpdated 4 mo ago
    Auto-check passed

Questions about Writing

What does Writing do?

通用写作技能:以"内容→组件→组合"的方式产出技术文档、产品文档、汇报材料. An agent skill from 312362115/claude. Writing is an agent skill from 312362115/claude.

When should I use Writing?

Writing fits situations like: tasks that involve PRD writing; tasks that involve Deep research.

How do I install Writing in Claude Code?

Run `npx skills add 312362115/claude --skill writing -a claude-code`. Or copy the skill folder (skills/writing in 312362115/claude) into .claude/skills/writing in your project. Claude Code loads it when a task matches its description.

How do I install Writing in Codex?

Run `npx skills add 312362115/claude --skill writing -a codex`. Or copy the skill folder (skills/writing in 312362115/claude) into .agents/skills/writing in your project. Codex loads it when a task matches its description.

Can I use Writing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 312362115/claude --skill writing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing, .gemini/skills/writing, .github/skills/writing and .opencode/skills/writing in your project.

What does Writing need to run?

Going by SKILL.md and its folder, Writing needs the command-line tools its instructions call (git).

Does Writing access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Writing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Writing use?

Writing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Writing use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 13k tokens, read only when the agent opens those files.

What are the alternatives to Writing?

Skills that share tags, products or a category with Writing: Tdoc (tornado-doc/tdoc, 103 stars), Expand Tasks (anombyte93/prd-taskmaster, 605 stars), Idea Os (sickn33/agentic-awesome-skills, 47k stars) and Product Manager (staruhub/ClaudeSkills, 727 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Writing?

312362115 (a GitHub user) maintains it in 312362115/claude, which has 107 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on May 14, 2026.

Source: 312362115/claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.