Article Editing
Paste the following prompt into your AI chat to install this skill:
Please install @kunlungrowth/edit-article according to https://skillhub.cn/install/skillhub.md.
About this skill
The Problem
Technical drafts often have section jumps, long paragraphs, and missing prerequisites, forcing readers to re-read. When a draft already contains conclusions, mechanisms, and pitfalls, unclear ordering can hide dependencies. 文章润色 edits an existing draft by restructuring and tightening prose; it does not invent facts or rewrite the author's position.
How It Works
- Split the article by headings and confirm section boundaries.
- Treat information as a DAG: introduce prerequisites before mechanisms or conclusions.
- Rewrite each section for clarity, flow, and transitions.
- Keep paragraphs compact, roughly 80–120 Chinese characters, splitting or trimming when longer.
- The result is a reviewable, section-based rewrite rather than surface-level editing.
- Review the full piece for repetition, gaps, and dependency order.
Boundaries
Use it for polishing technical posts, design notes, or documentation. Avoid it for drafting from scratch, fact-checking, or materially changing the author's intent. If the draft lacks facts or sources, add them first. Pair it with publishing or layout steps after editing.
Use Cases
- Before publishing a technical blog draft, reorganize scattered sections into background, core mechanism, pitfalls, and summary so readers follow the dependency order.
- When writing an engineering design note, split overlong paragraphs into shorter sections and move prerequisite concepts before interface details clearly.
- When revising product documentation, ensure feature explanations introduce core concepts first, then usage examples, then troubleshooting notes for readers to follow.
- When preparing release notes, merge duplicate updates and order items by what readers need to know before upgrade details first.
Best For
- Engineering bloggers: reorganize drafts into background, mechanism, pitfalls, and compressed paragraphs.
- Product managers maintaining docs: keep feature notes conceptual before procedural without changing intent.
- Open-source maintainers: merge duplicate release notes and clarify the reading order.
- Consultants preparing solution notes: present rationale before implementation details for clients.
Related Skills
A Chinese financial writing editor that removes AI-ish research-report tone, template phrases, and vague claims, rewriting text into natural, concrete prose and exporting Word files on demand.
Generates a Markdown user scenario document from model designs and PRDs, covering overview, MVP, user stories, and non-functional requirements.
Continues user-provided story fragments while preserving worldbuilding, characters, and style, with options for genre, length, foreshadowing, and endings.
Generate ready-to-use Weibo hot-topic copy, reply plans, checklists, and risk notes for brand moments and public topics.