菜单
Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/edwinhu/workflows --skill writing-general命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use for feature development and engineering changes.
This skill should be used when the user asks to 'start data analysis', 'plan a data project', 'explore this dataset', 'what should I analyze', 'set up a new study', or needs the data-science workflow.
Use when the user asks to 'run a work workflow', 'do this properly', 'clarify, plan, and verify this', 'small structured task', or 'don't just wing it' for a bounded task too small for a specialized workflow.
正在显示 SKILL.md
基于 SOC 职业分类
| name | writing-general |
| description | Internal skill for Strunk & White writing rules. Loaded by /writing for quick edits or as base layer for domain skills. |
| user-invocable | false |
| disable-model-invocation | true |
Foundational style guide for clear, concise prose based on Strunk & White's Elements of Style.
Omit needless words.
Every word must earn its place. Vigorous writing is concise. A sentence should contain no unnecessary words, a paragraph no unnecessary sentences.
| Rule | Explanation |
|---|---|
| Write in prose | Avoid bullet points and lists unless explicitly requested |
| Use active voice | "The committee approved the plan" not "The plan was approved" |
| Be concrete | Specific details over vague abstractions |
| Put statements in positive form | Say what something is, not what it isn't |
| Use definite language | Avoid hedging, qualifiers, and weasel words |
If you catch yourself writing ANY of these, DELETE THE SENTENCE and START FRESH:
| Anti-Pattern | Restart Approach |
|---|---|
| "It is [adjective] that..." | Rewrite as direct assertion |
| "There are [X] reasons" | Replace with direct list or synthesis |
| "In order to" | Replace with "to" |
| Sentence > 40 words with nested clauses | Break into 2-3 sentences |
| Passive voice hiding the actor | Name the actor, use active voice |
After deleting, restart the sentence with THE POINT first, then evidence.
Skipping the deletion pass is NOT HELPFUL — the user publishes bloated prose that buries their argument. Identify violations and purge them.
| Weak | Strong |
|---|---|
| utilize | use |
| in order to | to |
| due to the fact that | because |
| at this point in time | now |
| in the event that | if |
| prior to | before |
| subsequent to | after |
| with regard to | about |
| a large number of | many |
| is able to | can |
For comprehensive guidance, consult:
references/elements-of-style.md - Complete Strunk & White guide covering:
Weak original:
It is important to note that there are a variety of different factors that contribute to the overall success of the project in question.
Strong revision:
Several factors determine project success.
Weak original:
The report was written by the team and was subsequently reviewed by management prior to being distributed to stakeholders.
Strong revision:
The team wrote the report, management reviewed it, and stakeholders received it.
After completing any writing task, invoke /ai-anti-patterns to check for AI writing indicators.