Agent skill
write
Invoke only when explicitly asked to write, edit, or polish prose in Chinese or English. Strips AI writing patterns and rewrites to sound natural. Not for code comments, commit messages, or inline docs.
Install this agent skill to your Project
npx add-skill https://github.com/tw93/Waza/tree/main/skills/write
Metadata
Additional technical details for this skill
- version
- 3.8.0
SKILL.md
写作风格 / Writing Style
Prefix your first line with 🥷 inline, not as its own paragraph.
检测被编辑文本(不是用户的指令)的语言:
- 含中文字符 → 加载
references/write-zh.md - 否则(英文、混合、不确定)→ load
references/write-en.md
如果受众不明确(博客读者?RFC?邮件?),先问清楚再编辑。同一内容写给初级工程师和写给高级架构师,读起来应该完全不同。
执行顺序: 读取对应规则文件,严格按规则处理,输出修改后的内容。
输出修改后的内容后,停止。除非用户主动询问,否则不解释改动。
Hard Rules
- Meaning first, style second. If removing AI patterns or making prose more natural would change the author's intended meaning, keep the original. A failed rewrite is one that sounds better but says something different.
- Preserve unless told to cut. Keep every existing sentence and paragraph unless the user explicitly asks to remove or replace specific parts. If a section feels unnecessary, flag it; do not delete.
- Match naming conventions. Before creating new content files, check existing patterns in the directory. Follow the convention already in use.
- No silent restructuring. Do not reorganize headings, reorder paragraphs, or merge sections unless the user asks for structural changes. Edit content in place.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
design
Invoke when building any UI, component, page, or visual interface. Produces distinctive design with a committed aesthetic, not generic defaults. Not for backend logic or data pipelines.
think
Invoke before writing any code for a new feature, design, or architecture decision. Turns rough ideas into approved plans with validated structure. Not for bug fixes or small edits.
check
Invoke after any implementation task completes or before merging. Reviews the diff, auto-fixes safe issues, runs specialist security and architecture reviewers on large diffs. Not for exploring ideas or debugging.
learn
Invoke when diving deep into an unfamiliar domain, preparing a research article, or turning collected sources into publishable output. Runs a six-phase workflow: collect, digest, outline, fill in, refine, publish. Not for quick lookups or single-file reads.
read
Invoke when given any URL, web page link, or PDF to read. Fetches the content as clean Markdown via proxy cascade and saves to Downloads. Not for local files already in the repo.
hunt
Invoke when debugging any error, crash, unexpected behavior, or failing test. Finds root cause before applying any fix. Not for code review or new features.
Didn't find tool you were looking for?