mcpbeat Sign in

Personal Chinese Writing Style Agent Skill

Apply the user's Chinese writing style when writing, translating, editing, proofreading, polishing, or publishing Chinese content, including blog posts, articles, subtitles, captions, tweets/X posts, threads, newsletters, and social posts. Enforce punctuation rules, especially Chinese curved quotes, halfwidth dash " - ", ASCII ellipsis "......", and no leftover fullwidth/English punctuation in Chinese body text.

6k tokens
context cost
the whole folder, loaded on every use
5
files
instructions only
0
copies elsewhere
how many repositories repackaged it
130
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/sugarforever/01coder-agent-skills --skill personal-chinese-writing-style

What comes with it

21 368 bytes besides the instruction
references/article-structure.md
references/punctuation.md
references/social-media-style.md
references/voice-and-phrasing.md

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

5 sections, as written by the author

Personal Chinese Writing Style

Use this skill for Chinese content. The goal is not to explain the style back to the user; the goal is to apply it and verify the final text.

Operating Workflow

  • Identify the content type: article/blog, translation/edit, subtitle/caption, or social post/thread.
  • Load only the needed reference:
  • references/punctuation.md - always read for Chinese output.
  • references/article-structure.md - read for blog posts, newsletters, long articles, and technical writeups.
  • references/voice-and-phrasing.md - read for translation, editing, and long-form Chinese prose.
  • references/social-media-style.md - read for X/Twitter, threads, short social posts, and launch notes.
  • Write or edit the content.
  • Run the final punctuation pass before delivering or saving.
  • Fix every real violation in Chinese body text, then reread the affected sentence for meaning.

Non-Negotiable Punctuation

These are output requirements, not suggestions.

Use this exact punctuation in Chinese body text:

  • Quotes: use and . Do not use " around Chinese prose.
  • Dash: use - with one space on both sides. Do not use --, ——, or .
  • Ellipsis: use ....... Do not use ……; do not use ... as a Chinese ellipsis.
  • Chinese sentence punctuation: use . Do not leave , . : ; ? ! between Chinese characters.

Allowed exceptions: YAML frontmatter, code blocks, inline code, JSON/config, URLs, file paths, shell commands, exact source quotes, and English-only sentences.

Final Checklist

Before returning Chinese content, check:

  • No " remains around Chinese body text.
  • No --, ——, or remains as a dash in Chinese prose.
  • No …… remains; ellipsis is .......
  • Chinese sentences use Chinese punctuation, not ASCII comma/period/colon/question/exclamation marks.
  • Article prose has no duplicate body # H1 when frontmatter already has title.
  • Long-form article endings stay light: no ## 总结, ## 最后, ## 结语, or repeated link dump unless the user explicitly asks.
  • Social posts do not end with an empty self-summary such as “这是 X 的标志性时刻”.

Voice Defaults

  • Prefer natural Chinese technology prose over literal English translation.
  • Avoid business cliches unless they are the precise industry term: 闭环、抓手、颗粒度、对齐、赋能、赛道、弯道超车、心智.
  • Delete trust-me lines: “最干净的实现”, “每一步都是真实代码”, “最完整教程”.
  • Let facts carry the point; do not over-explain the author’s conclusion in short posts.

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

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.

4k tokens
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Writing Plans
by ZhanlinCui
×4

Use when you have a spec or requirements for a multi-step task, before touching code

816 tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts
Crafting Effective Readmes
by softaworks
×3

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

15k tokens
Humanizer
by softaworks
×3

| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

6k tokens
Opentrons Integration
by christophacham
×3

Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.

9k tokens scripts

How to use it

Copy the folder

Take sugarforever/personal-chinese-writing-style from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.