AGENT SKILL

humanize-english

Edit English drafts for clear, natural language while preserving facts, uncertainty, technical meaning, citations and genre. Use when: humanize this text, remove AI-style filler, improve English prose, or edit an English article before publication. Not an authorship detector or a promise to bypass one. For Russian use humanize-russian; for thesis/evidence and structure use article-structure-review.

License 许可
MIT
最近更新
2026-11-14
Stars
★ 1
Forks
0

01 前言 Front Matter

name
humanize-english
metadata
{ "version": "2.0.0", "reviewed": "2026-09-06" }
description
Edit English drafts for clear, natural language while preserving facts, uncertainty, technical meaning, citations and genre. Use when: humanize this text, remove AI-style filler, improve English prose, or edit an English article before publication. Not an authorship detector or a promise to bypass one. For Russian use humanize-russian; for thesis/evidence and structure use article-structure-review.

03 SKILL.md 正文

Clear, Natural English Editing

Improve the reader's understanding, not a detector score. A good reference can have repeated terminology, regular tables, definitions and no anecdote. Keep the user's intended voice and the destination's format.

Facts Are Not Style Material

  • Preserve supplied numbers, units, dates, versions, names, citations, negation, uncertainty and claim scope. Do not silently update a historical date.
  • Never invent a count, quote, interview, personal experience, experiment, failure, comparison or source to make prose more vivid.
  • Add specificity only when the supporting evidence supplies it. If no measurement exists, retain uncertainty or remove an unsupported claim. An unsupplied number is not an improvement over a vague quantity.
  • Label illustrative scenarios as hypothetical. Do not present them as a real case study or treat their invented values as proof of a product claim.
  • Preserve identifiers, executable code and technical obligations. Words such as may, must, can and will are not interchangeable style alternatives.
  • Reuse provided facts without asking the user to repeat them. Research a material factual gap when research is in scope; otherwise identify the gap without manufacturing an answer or blocking supported edits.

Match the Genre

Genre Useful editing Avoid forcing
technical reference exact terms, clear conditions, scannable structure slang, story openings, rhetorical questions, sales CTA
explanation/tutorial prerequisites and action/result sequence an untested command described as verified
analysis separate observation, inference and limits stronger causal claims than the evidence supports
personal narrative the author's supplied experiences and voice invented first-person testimony
marketing a supported benefit and relevant next action fabricated testimonials, percentages or guarantees

Contractions, fragments, humour, analogies and direct address are options, not quotas. Use them when they fit the audience and improve comprehension. Parallel lists and consistent terminology can be desirable in documentation.

Editing Procedure

  1. Identify the reader's task, genre, source material and protected facts from the existing request and draft. Do not add an unnecessary intake questionnaire.
  2. Remove empty intensifiers and duplicated ideas. Use direct verbs when meaning is preserved; keep connectors that express real causality or contrast.
  3. Clarify who acts, on what, under which conditions and with what result. Do not supply a result that the source does not establish.
  4. Fix awkward rhythm where it hinders reading. Do not maximize variation, enforce a paragraph pattern or replace terms to appear less predictable.
  5. Compare input and output for semantic changes. Check quantities with their units, denominator, time frame and uncertainty, not just the numeral.
  6. Return the edited text and any necessary factual caveat. Once the edit is sufficient, continue the remaining requested publication workflow rather than starting another stylistic pass automatically.

Examples: Same Facts, Clearer Prose

Supplied text Faithful edit
In order to load the file, the user must select Open. To load the file, select Open.
The tool may reduce processing time; no benchmark is available. The tool may save processing time, but no benchmark is available.
Some testers reported failures. The sample size was not recorded. Some testers reported failures; the sample size was not recorded.
On 2026-09-01, 12 of 40 runs failed with version 2.1. With version 2.1, 12 of 40 runs failed on 2026-09-01.

These are editing fixtures, not results from a deployed product. Unknown sample size stays unknown; a date, denominator and version do not disappear for fluency.

Verification

  • Every changed factual assertion still maps to the supplied material or a source actually checked for this task.
  • Conditions, uncertainty, negatives, numbers, units, dates, versions and code are preserved unless an evidence-backed factual correction was requested.
  • The result helps its intended reader without an unrequested genre change.
  • No invented testimony or detector-evasion claim was added.

A no-change verdict is valid for an already clear passage. Do not add numbers, questions, opinions, deliberate errors or fake admissions to satisfy a score.

Gotchas

  • Detector score as evidence: it establishes neither authorship nor factual accuracy. Do not promise an undetectable edit.
  • Replacing every vague quantity: guessing a plausible percentage fabricates evidence when the sample size is unknown.
  • Forced informality: slang can make a reference harder to understand, particularly for readers using English as an additional language.
  • Synonym churn: repeating a technical term is safer than creating a false distinction through alternate names.
  • Example contamination: a skill example is not an event that happened to the user or author.

Troubleshooting

Symptom Check Correction
polished but unsupported claim source scope and conditions restore supported meaning or remove the claim
bureaucratic phrasing action and actor use a direct sentence without changing obligations
repetitive text repeated meaning versus necessary terms cut redundancy, keep precise terminology
reference sounds like an advertisement requested genre remove promotion and invented narrative
detector flags the passage actual writing and detector limitations repair evidenced defects, not a guessed authorship score

Sources and Maintenance

Reviewed 2026-09-06. Owner: the existing writing-skill maintainers. Change through canonical Git, focused before/after fixtures, independent review and the supported installer; retain the prior revision and installation backup for rollback. Refresh sources when guidance changes or a factual/genre regression is observed, not by automatically rewriting working prose on a schedule.

04 同仓库更多 Skills

hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

owner-voice

暂无简介

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

humanize-russian

Редактировать русский текст для ясности и естественного звучания, сохраняя факты, термины, источники и жанр. Использовать когда: убрать канцелярит, сделать текст живее, отредактировать русский черновик или статью перед публикацией. Не определяет авторство и не обещает обход детекторов. Для английского — humanize-english; для структуры и доказательств — article-structure-review.

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

caveman

Ultra-compressed reply mode. Cuts output tokens ~65-75% by answering in terse "caveman" style while keeping full technical accuracy, and shapes what survives: action first, state restated every turn, concrete time estimates, visible wins. Intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman", "talk like caveman", "use caveman", "less tokens", "be brief", or Russian "пещерный режим", "говори как пещерный", "кратко", "меньше токенов", "экономь токены" — or invokes /caveman. Preserves the user's language (Russian in → Russian caveman out). Off only: "stop caveman" / "normal mode" / "обычный режим". Do not use merely because a response should be concise, and do not use when the user requests normal prose, a polished document, or exact wording.

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

article-structure-review

Проверить структуру технической статьи после черновика: задача читателя, жанр, опора значимых утверждений на доказательства и честные ограничения. Use after the first draft, before publication. Исправлять структуру, когда это входит в запрос; не создавать обязательный конвейер из других навыков. Для локальной языковой редактуры — humanize-english или humanize-russian.

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

video-post-production

Video post-production rules: audio mastering, color, captions, platform export. Use when: 'add music', 'add voiceover', 'export for tiktok', 'add captions', 'color grade', 'audio levels', 'master audio', 'export settings', 'platform requirements'. Covers FFmpeg patterns, audio chain, subtitle standards, and platform-specific export configs. Do NOT use to generate or animate the video frames/scenes in code (use remotion-production-guide), to write the script (use video-narrative-arc), or to evaluate script quality (use script-evaluator); this is the finishing stage applied to an already-rendered video.

★ 1
hermes-jarvis-bot
hermes-jarvis-bot/hermes-agent-config-kit

video-narrative-arc

Proven narrative arc templates for product videos and ads. Use when: 'write script', 'video structure', 'narrative arc', 'scene plan', 'storyboard', '15 second video', '30 second video', '60 second video', 'how to structure the video', 'video script template'. Provides beat-by-beat templates with timing, emotional arc mapping, hook formulas, and pacing rules. Covers 10s-90s formats for social, product demos, launches, and pitches. Do NOT use to judge or score an already-written script (use script-evaluator), to derive the product insight/brief from scratch (use product-meaning-extractor), or to render the video in code (use remotion-production-guide); this stage only produces the structured script/beats.

★ 1