Agent Skills
› NeverSight/learn-skills.dev
› write
write
GitHub去除AI写作痕迹，将英文文本重写为自然的人类口吻。严格遵循原意与结构，不增删内容，仅针对明确的编辑请求生效。
Trigger Scenarios
用户要求润色或重写英文文本
用户明确要求消除AI语气
Install
npx skills add NeverSight/learn-skills.dev --skill write -g -y
SKILL.md
Frontmatter
{
"name": "write",
"metadata": {
"version": "1.0.0"
},
"description": "Strips AI writing patterns and rewrites prose to sound natural in English. Only activates on explicit writing or editing requests. Not for code comments, commit messages, or inline docs.",
"when_to_use": "edit text, proofread, sound natural, polish, rewrite, make this better, remove AI tone, draft, write this"
}
Write: Cut the AI Tone
Prefix your first line with 🥷 inline, not as its own paragraph.
Strip AI patterns from prose and rewrite it to sound human. Do not improve vocabulary; remove the performance of improvement.
Pre-flight
- Text present? If the user gave only an instruction with no actual prose to edit, ask for the text in one sentence. Do not proceed.
- Audience locked? If the intended audience is unclear and cannot be inferred from the text (blog reader vs RFC vs email), ask before editing. Junior engineer and senior architect prose should read completely different.
- Load reference: Load
references/write-en.mdbefore editing.
Read the reference file. Then edit. No summary, no commentary, no explanation of changes unless explicitly asked.
Hard Rules
- Meaning first, style second. If removing an AI pattern would change the author's intended meaning, keep the original. A failed rewrite sounds better but says something different.
- Preserve unless told to cut. Keep every sentence and paragraph unless the user explicitly asks to remove or replace specific parts. Flag unnecessary sections; do not delete them silently.
- No silent restructuring. Do not reorganize headings, reorder paragraphs, or merge sections unless structural changes are explicitly requested. Edit in place.
- Match naming conventions. Before creating new content files, check existing patterns in the target directory and follow them.
- Never guess the target text. If the request refers to "the paragraph above" or "what you just said" without quoting it, ask which exact text to edit. Do not rewrite conversation history without explicit permission.
- Stop after output. Deliver the rewritten text. Then stop. Do not append a list of changes, a justification, or a "hope this helps" closer.
- No emoji in edited text. Remove any emoji from the output unless the user explicitly asks to keep them.
Release Note Template Mode
Activate when: "release", "changelog", "version", "release notes"
Generate from commit messages:
- Breaking Changes
- New Features
- Fixes & Improvements
- Deprecations
Format: Kata release style (numbered list, bold label, one sentence on user effect).
Output
Return only the edited prose. If the text was truncated or if multiple versions were possible, note that in one sentence after the body. Otherwise, no wrapper, no preamble, no postscript.
Version History
- e0220ca Current 2026-07-05 21:27
