Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
Chinese-language style guide that keeps articles, scripts and product copy natural, readable and fact-grounded, with a lint script that flags tired phrasing.
SKILL.md written in Chinese; this summary is our English description.
Install Oil Tone Chinese Writing Style
$ npx skills add oil-oil/oil-tone --skill oil-tone -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install oil-oil/oil-tone oil-tone --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/oil-oil/oil-tone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/oil-tone .claude/skills/oil-tone && rm -rf skills-srcUse ~/.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/
Install the "oil-tone" agent skill from https://github.com/oil-oil/oil-tone/tree/main/skills/oil-tone into .claude/skills/oil-tone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oil-tone", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/oil-oil/oil-tone/tree/main/skills/oil-toneType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add oil-oil/oil-tone --skill oil-tone -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install oil-oil/oil-tone oil-tone --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oil-oil/oil-tone.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/oil-tone .agents/skills/oil-tone && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oil-tone" agent skill from https://github.com/oil-oil/oil-tone/tree/main/skills/oil-tone into .agents/skills/oil-tone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oil-tone", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add oil-oil/oil-tone --skill oil-tone -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install oil-oil/oil-tone oil-tone --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oil-oil/oil-tone.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/oil-tone .cursor/skills/oil-tone && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oil-tone" agent skill from https://github.com/oil-oil/oil-tone/tree/main/skills/oil-tone into .cursor/skills/oil-tone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oil-tone", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/oil-oil/oil-tone.git --path skills/oil-tone--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add oil-oil/oil-tone --skill oil-tone -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install oil-oil/oil-tone oil-tone --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oil-oil/oil-tone.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/oil-tone .gemini/skills/oil-tone && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oil-tone" agent skill from https://github.com/oil-oil/oil-tone/tree/main/skills/oil-tone into .gemini/skills/oil-tone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oil-tone", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install oil-oil/oil-tone oil-toneInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add oil-oil/oil-tone --skill oil-tone -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/oil-oil/oil-tone.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/oil-tone .github/skills/oil-tone && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oil-tone" agent skill from https://github.com/oil-oil/oil-tone/tree/main/skills/oil-tone into .github/skills/oil-tone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oil-tone", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add oil-oil/oil-tone --skill oil-tone -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install oil-oil/oil-tone oil-tone --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oil-oil/oil-tone.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/oil-tone .opencode/skills/oil-tone && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oil-tone" agent skill from https://github.com/oil-oil/oil-tone/tree/main/skills/oil-tone into .opencode/skills/oil-tone/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oil-tone", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
oil-tone- GitHub stars
- 229
- Token cost
- ~517 tokens
- SKILL.md length
- 47 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Chinese-language style guide that keeps articles, scripts and product copy natural, readable and fact-grounded, with a lint script that flags tired phrasing.
- Works in 4 steps: 自然、易读、通顺。… → 让读者跟得上。… → 把关系讲完整。… → …
- Drafting or rewriting a Chinese newsletter post, product page or speech
- SKILL.md covers 最重要的四件事, 写作与改写, 语气与句子 and 表达形式, plus 1 more section
- Runs Python scripts from its folder
What it does
Written in Chinese, the skill states that the first goal is text a reader can follow in natural word order, with facts as a hard limit that structure and cuts must serve rather than override for brevity or formality. Four rules lead: keep phrasing natural without mechanically stripping grammatical particles; order sentences by what the reader already knows, explaining a new term only the first time it appears; fill in a missing step between facts, causes, results and limits instead of papering over a jump with a transition word; and never invent experiences, feedback, numbers or results, keeping first-hand experience, official material, speculation and plans visibly separate.
Guidance for drafting and rewriting covers deciding what question a piece answers before organizing its paragraphs, introducing a new term only where it is first used, and placing a link beside the claim it supports rather than piling links at the end. Tone guidance covers a consistent first-person voice within a passage, concrete consequences instead of vague claims, and cutting padded filler and sloganeering. A closing check skims just the headings and topic sentences, reads the body straight through for gaps in reasoning, reads it aloud for awkward phrasing, and runs scripts/tone_lint.py, which only flags a short list of clichés for a human to judge in context.
When your agent uses it
- Drafting or rewriting a Chinese newsletter post, product page or speech
- Polishing an existing Chinese draft to read more naturally
- Checking a Chinese draft for invented numbers or user feedback
- Running the lint script to flag tired phrases in a finished draft
Example prompts
- “Make this Chinese product introduction read more naturally.”
- “Check this speech draft for any invented numbers or experiences.”
- “Run tone_lint.py on this draft and see what it flags.”
Requirements
- Python, to run scripts/tone_lint.py
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 自然、易读、通顺。 用符合语境的常用词和自然语序，保留完整、自然的表达节奏，不为压缩而写成生硬短句。中文里的“的”“了”等虚词只要承担语法、语气或关系作用，就应保留，不能默认当作赘词；是否留删，要结合意思和朗读效果判断，不机械增删。
- 让读者跟得上。 按读者此时已经知道的信息安排顺序。新对象让人跟不上时，只补理解它所缺的那一步；已经清楚的内容不重复解释。标题不能代替正文完成必要的交代。
- 把关系讲完整。 事实、操作、原因、结果和限制之间缺了一步时，先补这一步。一个句子通顺，不代表它能接上前一段；段落之间跳跃时，先调整信息顺序，不靠“接下来”“因此”等词掩盖。
- 事实有依据。 不编造经历、感受、用户反馈、数字和结果。把亲身体验、官方资料、推测和计划分开写；事实变化时核对当前材料。
What it can do on your machine
Read from SKILL.md and the folder at commit 39cbf92. 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
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Oil Tone Chinese Writing Style loads about 517 tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 47 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from oil-oil/oil-tone at commit 39cbf92, republished under its MIT licence (© oil-oil). 47 words, ~517 tokens.
Download SKILL.mdSave it as
.claude/skills/oil-tone/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- oil-tone
- description
- 为中文或英文文案提供自然、易读、通顺、清楚的写作规范。需要起草、改写或润色文章、口播、演讲稿、PPT 文案、网站与产品介绍、个人简介、公众号和社交帖子时使用；用户明确指定 oil-tone 时也使用。适用于文风处理，不用于单纯查资料或不涉及表达的事实、技术修改。
oil-tone
最重要的四件事
oil-tone 的首要目标是让文案自然、易读、通顺、清楚：读者能按自然语序读下去，轻松理解句子和段落的意思。事实有依据是不能突破的底线；结构、用词和删改都要服务于理解，不能为了短、正式或整齐而把话写得生硬。
- 自然、易读、通顺。 用符合语境的常用词和自然语序，保留完整、自然的表达节奏，不为压缩而写成生硬短句。中文里的“的”“了”等虚词只要承担语法、语气或关系作用，就应保留，不能默认当作赘词；是否留删，要结合意思和朗读效果判断，不机械增删。
- 让读者跟得上。 按读者此时已经知道的信息安排顺序。新对象让人跟不上时，只补理解它所缺的那一步；已经清楚的内容不重复解释。标题不能代替正文完成必要的交代。
- 把关系讲完整。 事实、操作、原因、结果和限制之间缺了一步时，先补这一步。一个句子通顺，不代表它能接上前一段；段落之间跳跃时，先调整信息顺序，不靠“接下来”“因此”等词掩盖。
- 事实有依据。 不编造经历、感受、用户反馈、数字和结果。把亲身体验、官方资料、推测和计划分开写；事实变化时核对当前材料。
写作与改写
- 先确认这篇内容要回答什么问题、材料支持哪些判断、读者需要先知道什么，再组织段落。每段承担一种主要作用，相邻段落应有读者能看出的关系。
- 读者需要先认识某个产品、功能、术语或指标，才能理解后文时，在第一次用到它的地方说明；读者已有上下文时直接往下讲。解释不要依赖另一个未经说明的词。
- 正文先讲到读者不打开链接也能理解。需要核对事实或进入产品、文档、仓库时，把链接放在对应说法旁边；链接不代替解释，也不集中堆在文末。
- 只要求润色时，保留原有事实、观点、数字、引用和必要格式。用户指出全文难懂或顺序不自然时，可以调整段落与章节，但不得借重排改变结论或补入无依据的细节。
- 标题说明真实对象、动作或判断；小标题直接标明该部分内容。标题中的所有权、时间、数量和结果都要有材料支持。
- 连续的解释和因果关系用自然段；并列项、步骤和查找信息可以用列表或表格。选择格式之前，先确认正文的理解顺序。
语气与句子
- 写自己的做法和判断时用“我”；带读者看一般流程时可用“我们”；直接称呼读者群体时可用“大家”。不虚构共同经历，同一段内不频繁切换称呼。
- 写工具和产品时，优先呈现自己实际做过的操作、看到的结果、据此形成的判断和使用限制。不把有依据的个人判断改成中性的功能介绍。
- 句子要让人看清谁做了什么、作用于什么、发生了什么变化。上下文清楚时可以省略主语；读者需要回读猜测时应补清。
- “看、说、删、写、查、改、做、用”等常用动词，意思准确就直接使用。“的”“了”以及“在”“就”等虚词，只要能让语法、语气或关系表达得更自然、准确，就保留下来；不要为了压短句子或增加书面感而删掉，也不要为了显得口语而机械添加。判断时要连着上下文朗读，比较删改前后的自然程度和意思。
- 说明影响时写具体后果，不停在“有影响”“得到提升”一类泛指上；具体后果必须有材料依据，不能为了生动虚构场景。
- 不用没有信息量的行业背景、模糊归因、宣传口号、模板化转场和拔高结尾。删掉后不影响事实与关系的句子，可以直接删；确有转折或限定作用的表达不机械禁用。
- 中文按自然语法和标点书写；英文使用常见、直接的词。口播与社交内容保留自然的口语节奏；文档可以正式，但不要为了书面感删掉必要的虚词或连接表达。成稿要清理重复起句和无意义的语气词。
表达形式
- 文档、说明和正式通知以准确、易查找为先；口播与社交内容可以更接近日常说话，但同样要讲清对象和关系。
- 已有成稿中的代码、专有名词、链接和引用来源按需保留；中文与英文、数字之间留一个半角空格。
完稿检查
- 只读标题和各段首句：能否顺着它们讲出全文？新对象是否突然出现？发现跳跃时先调整顺序或补足关系。
- 连续读正文：每个判断是否有依据，原因和结果是否连得上；不打开链接能否理解主要内容？
- 按自然语速朗读：有没有不符合日常表达习惯的拗口句子？删掉“的”“了”等虚词后，语气、语法关系或意思有没有变生硬、变模糊？指代、动作对象、条件和状态是否清楚？修改后句子是否仍然完整？
- 文件成稿可运行本 Skill 的
scripts/tone_lint.py查找值得复核的表达。脚本只提示少数套话和空泛说法，无法判断文字是否自然、易读、通顺；逐条结合语境决定是否修改，最终以全文连读为准。
© oil-oil, 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 2 other files (scripts) in skills/oil-tone of oil-oil/oil-tone.
- SKILL.md
- agents/openai.yaml
- scripts/tone_lint.py
Open the folder on GitHubat commit 39cbf92
Compare with similar skills
Oil Tone Chinese Writing Style 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Oil Tone Chinese Writing Style this skilloil-oil/oil-tone | 229 | — | ~517 | Automated safety check: Pass | MIT | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Defensive Writing Editorlennney/stop-that-shit | 2.5k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Chinese Technical Writingleter/zh-tech-writing | 352 | — | ~656 | Automated safety check: Pass | MIT | |
| ISO 24495-1 Plain LanguageGaZmagik/iso-24495 | 190 | — | ~2k | Automated safety check: Pass | MIT | |
| Declaudingoaustegard/claude-skills | 150 | — | ~5.2k | Automated safety check: Pass | MIT |
Similar skills
Defensive Writing Editor
lennney/stop-that-shit
Cuts defensive disclaimers, stacked hedging and self-protective narration from proposals and summaries, keeping only limits that affect the reader's decision.
Chinese Technical Writing
leter/zh-tech-writing
Sets writing rules for Chinese technical docs: short plain sentences, consistent typography and a checklist for removing AI-sounding filler.
ISO 24495-1 Plain Language
GaZmagik/iso-24495
Makes the agent write every user-facing reply by the four plain-language principles of ISO 24495-1:2023: relevant, findable, understandable and usable.
Declauding
oaustegard/claude-skills
Rewrites model-sounding prose into plain technical writing and checks that every claim survives, for PR text, docs, commit messages and similar drafts.
Simple English Rewriter
vinta/hal-9000
Rewrites docs, READMEs, issues, comments or UI text in plain Global English that translates well and still sounds native, keeping every fact intact.
Related
Categories
Questions about Oil Tone Chinese Writing Style
What does Oil Tone Chinese Writing Style do?
Chinese-language style guide that keeps articles, scripts and product copy natural, readable and fact-grounded, with a lint script that flags tired phrasing. Written in Chinese, the skill states that the first goal is text a reader can follow in natural word order, with facts as a hard limit that structure and cuts must serve rather than override for brevity or formality. Four rules lead: keep phrasing natural without mechanically stripping grammatical particles; order sentences by what the reader already knows, explaining a new term only the first time it appears; fill in a missing step between facts, causes, results and limits instead of papering over a jump with a transition word; and never invent experiences, feedback, numbers or results, keeping first-hand experience, official material, speculation and plans visibly separate.
When should I use Oil Tone Chinese Writing Style?
Oil Tone Chinese Writing Style fits situations like: drafting or rewriting a Chinese newsletter post, product page or speech; polishing an existing Chinese draft to read more naturally; checking a Chinese draft for invented numbers or user feedback; running the lint script to flag tired phrases in a finished draft.
How do I install Oil Tone Chinese Writing Style in Claude Code?
Run `npx skills add oil-oil/oil-tone --skill oil-tone -a claude-code`. Or copy the skill folder (skills/oil-tone in oil-oil/oil-tone) into .claude/skills/oil-tone in your project. Claude Code loads it when a task matches its description.
How do I install Oil Tone Chinese Writing Style in Codex?
Run `npx skills add oil-oil/oil-tone --skill oil-tone -a codex`. Or copy the skill folder (skills/oil-tone in oil-oil/oil-tone) into .agents/skills/oil-tone in your project. Codex loads it when a task matches its description.
Can I use Oil Tone Chinese Writing Style 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 oil-oil/oil-tone --skill oil-tone -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oil-tone, .gemini/skills/oil-tone, .github/skills/oil-tone and .opencode/skills/oil-tone in your project.
What does Oil Tone Chinese Writing Style need to run?
Going by SKILL.md and its folder, Oil Tone Chinese Writing Style needs Python for the scripts in its folder. Our summary lists: Python, to run scripts/tone_lint.py.
Does Oil Tone Chinese Writing Style access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Oil Tone Chinese Writing Style 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Oil Tone Chinese Writing Style use?
Oil Tone Chinese Writing Style 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 Oil Tone Chinese Writing Style use?
About 517 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Oil Tone Chinese Writing Style?
Skills that share tags, products or a category with Oil Tone Chinese Writing Style: Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars), Defensive Writing Editor (lennney/stop-that-shit, 2.5k stars), Chinese Technical Writing (leter/zh-tech-writing, 352 stars) and ISO 24495-1 Plain Language (GaZmagik/iso-24495, 190 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oil Tone Chinese Writing Style?
oil-oil (a GitHub user) maintains it in oil-oil/oil-tone, which has 229 GitHub stars. The repository was last updated on September 23, 2026.
Source: oil-oil/oil-tone on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.