sero-humanize
Audit or edit Sero Markdown documentation and other product prose to remove AI-writing patterns while preserving technical meaning, product terminology, links, examples, and the repository voice. Use when the user asks to humanize, de-slop, tighten, simplify, rewrite, or audit Sero documentation, README text, UI copy, release notes, plans, or specifications for AI tells. Also use when prose needs ASD-STE100 Simplified Technical English. Do not use for code review or for creative and promotional writing.
sero-labs · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add sero-labs/sero --skill sero-humanize技能说明
name: sero-humanize description: | Audit or edit Sero Markdown documentation and other product prose to remove AI-writing patterns while preserving technical meaning, product terminology, links, examples, and the repository voice. Use when the user asks to humanize, de-slop, tighten, simplify, rewrite, or audit Sero documentation, README text, UI copy, release notes, plans, or specifications for AI tells. Also use when prose needs ASD-STE100 Simplified Technical English. Do not use for code review or for creative and promotional writing.
Sero Humanize
Make Sero prose direct, specific, and useful. Human writing in technical documentation does not need personality. It needs clear decisions, concrete facts, and respect for the reader's time.
Follow the requested mode
- For an audit or review, report the material patterns and do not edit files.
- For an edit, rewrite the named files in place.
- For a new document, apply these rules while drafting it.
- If the request does not specify a mode, infer it from the requested action. Do not turn a request to assess prose into permission to change it.
Establish the voice and preservation set
Before editing:
- Read every file in scope in full.
- Read the nearest repository instructions that apply to those files.
- Use adjacent, clearly human-edited Sero documentation as the voice sample when the named files do not establish a consistent voice.
- Record what must not change:
- technical meaning and product behaviour;
- product names, canonical terms, and exact UI labels;
- commands, code, file paths, numbers, limits, and factual claims;
- the documentation type, useful narrative flow, and balance between prose, lists, tables, examples, and callouts;
- frontmatter, anchors, link targets, image paths, and screenshot order;
- the purpose and placement of each image, diagram, and other media asset;
- quotations and user input examples, unless the user asks to edit them.
Identify the intended reader. Unless the page states otherwise, assume the reader knows neither Sero nor the feature. Do not assume that simpler grammar fixes an explanation that requires missing product knowledge.
Do not add a fact to make a sentence more vivid. Verify a doubtful claim from the repository or leave it unchanged and report the doubt.
Audit structure before wording
Look for clusters and repeated patterns. Do not treat one punctuation mark or one common word as proof of AI writing.
Prioritize these defects:
- Meta narration that announces the next explanation instead of giving it.
- Repeated tutorial staging such as "what you are about to learn" and "what you have learned."
- Fixed enumerations such as "three things are worth noticing" when a direct heading or short list is clearer.
- Several paragraphs that can change order without changing the argument.
- A heading followed by a sentence that only repeats the heading.
- A conclusion that repeats the introduction without adding an action or fact.
- Repeated summaries of the same screen, process, or result.
- Forced contrasts such as "not only X, but Y" or "not X; rather Y."
- Groups of three used for rhythm instead of meaning.
- Mechanical bold lead-ins, excessive inline bold, or lists that should be short prose.
- Promotional adjectives, vague importance claims, and unsupported praise.
- Vague actors, passive constructions, filler, stacked hedges, and abstract nouns where an action is available.
- Synonym cycling for one product concept. Repeat the canonical term.
- Long sentences that mix instructions, exceptions, and background.
- Em dashes used repeatedly to join thoughts that need separate sentences.
- Headings that narrate the demo or expose implementation language instead of naming the reader's task, such as "The finish" or "Answer the gate."
- Examples that depend on an unexplained demo domain and therefore do not help the reader understand the feature.
- Tutorials that start using the product before they give prerequisites, sample data, expected starting state, or required sign-ins.
- Result sections that recite one captured run instead of telling the reader what to inspect and verify.
Keep useful structure. A list, summary, warning, question heading, or em dash is not a defect by itself.
Do not normalize a page or site to one format. Humanize the defective passages, not every paragraph. If a page already explains a concept well in prose, keep it as prose.
Rewrite for Sero documentation
Apply ASD-STE100 Simplified Technical English where it fits the material:
- Put the action or answer first.
- Use active voice when the actor matters.
- Give one main instruction per sentence.
- Put a condition before the action when the reader must know it first.
- Prefer common, precise words over formal or promotional alternatives.
- Use the same term for the same thing.
- Keep paragraphs focused on one subject.
- Keep necessary limits, cautions, and exceptions close to the action.
- Use contractions only when the established local voice requires them.
- Keep exact UI text in bold when the documentation uses bold for controls.
- Keep code identifiers and paths in code formatting.
- Retain a summary only when it helps the reader decide or act.
Use lists only when the content is naturally a sequence, set of choices, checklist, or compact reference. Do not:
- convert explanatory prose into bullet points only to make it shorter;
- turn each sentence or paragraph into a list item;
- replace transitions and reasoning with disconnected bullets;
- use repeated lists where a short paragraph gives the reader necessary context; or
- make several pages share the same mechanical list structure.
After the sentence pass, read the page as a whole. If lists now dominate a page that previously used useful prose, restore the prose. Clear technical writing needs connected explanation as well as scannable reference material.
For an overview p
阅读完整来源 ↗