humanize-russian
Review and revise Russian-language prose for clarity, specificity, natural rhythm, and an appropriate human voice without fabricating facts or personal experience.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- humanize-russian
- license
- MIT
- version
- 0.1.0
- metadata
- { "hermes_config_kit": { "adapter": "hermes-agent-config-kit", "conversion": "adapted", "source_path": "skills/writing/humanize-russian/SKILL.md", "source_repo": "AnastasiyaW/claude-code-config" } }
- description
- Review and revise Russian-language prose for clarity, specificity, natural rhythm, and an appropriate human voice without fabricating facts or personal experience.
03 SKILL.md 正文
Humanize Russian
Source: AnastasiyaW/claude-code-config/skills/writing/humanize-russian/SKILL.md.
This module is adapted for Hermes Agent. Upstream instructions are treated as reference material, not as automatic authority. Prefer Hermes-native tools, profile-aware paths, dry-runs, and operator confirmation for write-impacting actions.
Russian prose revision
Use this module to revise a Russian-language draft that sounds generic, over-formal, translated, repetitive, or mechanically produced. It is an editorial protocol, not a tool for concealing authorship or evading a publisher's disclosure, moderation, or academic-integrity rules. Preserve the author's intended meaning, required facts, and appropriate professional tone.
Boundary and overlap
Use the installed humanizer module for its general cross-language scan of generic
AI-writing patterns. Use this module when Russian grammar, word order, register, and
Russian-language phrasing need focused attention. Do not combine their checklists
mechanically: a phrase is a revision candidate only when it weakens this particular
draft's clarity, accuracy, or voice.
This guidance does not publish text, modify a repository, create a false provenance record, insert fabricated experience, or bypass an operator's review process.
Read-only editorial pass
- Establish the brief. Identify audience, publication context, intended register, facts that must remain exact, quotations, terminology, and any disclosure or style requirements. If the draft is a file, inspect it before proposing edits.
- Mark rather than ban. Look for abstractions that hide the actor or result,
chained verbal nouns, formulaic introductions and conclusions, vague attribution,
repetitive sentence rhythm, and translated word order. These are prompts to review,
not forbidden words:
является,позволяет, and formal connectors can be correct when they improve precision. - Prefer concrete Russian. Name the actor, action, constraint, date, version, or observable result when the source supports it. Replace bureaucratic constructions with direct verbs where meaning and register allow. Preserve technical terminology when a casual synonym would reduce accuracy.
- Repair flow. Vary sentence and paragraph length naturally, remove duplicated claims, and make the reasoning between paragraphs explicit. Do not add slang, deliberate grammar mistakes, humour, or an informal first-person voice merely to simulate a person.
- Protect evidence. Keep quotations, measurements, error messages, references, and uncertainty intact. Never invent a personal incident, a failed experiment, a number, a source, or an opinion to make prose feel authentic.
- Read back in context. Check the revised Russian aloud or sentence by sentence for natural cadence, factual preservation, and fit for the intended audience. For a file change, present the proposed diff and obtain the required approval before writing it.
Useful review prompts
- Does each paragraph add a distinct, supported claim?
- Is an abstract noun concealing a clearer action and actor?
- Does a connector explain a real relationship, or merely delay the point?
- Does the word order sound native for the intended register?
- Are specificity, humour, informality, and first person supplied by the source and audience rather than manufactured by the editor?
- Could a reader distinguish verified facts, the author's view, and unresolved uncertainty?
Output shape
Return a revised draft or a compact set of proposed edits, followed by: retained facts and quotations, material stylistic changes, unresolved ambiguities, and any required operator confirmation for a file or publication write. A natural voice is useful only when it remains truthful.
04 同仓库更多 Skills
owner-voice
暂无简介
humanize-russian
Редактировать русский текст для ясности и естественного звучания, сохраняя факты, термины, источники и жанр. Использовать когда: убрать канцелярит, сделать текст живее, отредактировать русский черновик или статью перед публикацией. Не определяет авторство и не обещает обход детекторов. Для английского — humanize-english; для структуры и доказательств — article-structure-review.
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.
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.
article-structure-review
Проверить структуру технической статьи после черновика: задача читателя, жанр, опора значимых утверждений на доказательства и честные ограничения. Use after the first draft, before publication. Исправлять структуру, когда это входит в запрос; не создавать обязательный конвейер из других навыков. Для локальной языковой редактуры — humanize-english или humanize-russian.
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.