human-rewrite

Solid

The repair pass on text that already exists — an agent's own last output, a subagent's report, a supplied document, a research summary, a legal or medical paragraph — rewritten so a person can read it fast and act on it, without changing what it claims. Meaning-preserving by contract: uncertainty, scope conditions, numbers, sample sizes, attribution, absent results, and reversing caveats all survive. Works on any subject, not just software. Trigger phrases: "/human-rewrite", "translate that into human", "that was a wall of text", "I can't follow this", "say that again but readable", "shorten this without losing anything". Not /human-output (the writing contract, which this skill links to rather than restates) or /human-draw (builds a picture) — human-rewrite governs the transformation of text that already exists.

AI & Automation 0 stars 0 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 78/100

Stars 20%
0
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /human-rewrite **Repair, not authorship.** Something has already been written. It is correct and unusable. Make it usable while keeping it correct. This is translation. The source text and your text must be true of the same world. A reader who acts on your version and a reader who acts on the original must take the same action, hold the same doubts, and be surprised by the same things. > **The complete style layer lives in `human-output` when that skill is > installed.** Otherwise apply the portable style floor in > [`references/human-contract.md`](references/human-contract.md). This file > carries only what exists *because there is a source*: what may change, what > may not, and how to prove it. **If you finish a repair and only the words changed, you did the wrong pass.** Most broken text is already readable. It is unusable because it is ordered by how the work happened rather than by what the reader must decide. The sentences often survive nearly intact and the document is still rebuilt. ## The one failure this skill exists to prevent A rewrite that makes something sound **more certain than the original**. It happens without malice and almost always unnoticed, because every force in the rewrite pushes the same direction. Hedges are the first thing a brevity pass deletes; they look like filler. Short declarative sentences read as confident, so the style you are applying *is* the confidence-adding mechanism. Attribution ("the vendor's own testing showed") is long, a...

Details

Author
allemaar
Repository
allemaar/open-skills
Created
1 months ago
Last Updated
today
Language
JavaScript
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

humanizer

Remove signs of AI-generated writing from text, and write in a human voice when producing new text. Use when the user says "humanize", "make this sound human", "rewrite this so it doesn't sound like AI", "fix the AI writing", "clean up AI text", or anything similar. Also applies when editing or reviewing text to make it sound more natural and human-written. This is an always-on style skill: once activated in a conversation, apply it to everything written going forward — not just rewrites. Based on Wikipedia's comprehensive "Signs of AI writing" guide. Detects and fixes patterns including: inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, passive voice, negative parallelisms, filler phrases, and reflexive summary openers.

0 Updated 1 weeks ago
Hiirocchi18
Code & Development Listed

ce-humanize

Rewrite AI-generated, generic, or over-polished prose into natural, credible, human-sounding text while preserving meaning, facts, structure, and required terminology — for emails, PR descriptions, READMEs, docs, proposals, commit messages, and other prose. Ephemeral by default (returns the rewrite); edits a named file only on explicit consent, format preserved. Never claims human authorship, fabricates experience or data, or optimizes to defeat AI-detection. Triggers: humanize, naturalize, de-robot, de-AI, make less AI-like, make more conversational or authentic, polish or rewrite prose/copy/tone. For generating user-facing docs from a plan's verified behavior use /ce-ship-document; this rewrites the tone of prose that already exists.

0 Updated 3 days ago
relusion
Data & Documents Listed

humanizer

Audit, rewrite, or draft text so it carries zero AI-writing tells and makes only honest, sourced, self-consistent claims. Built from Wikipedia's "Signs of AI writing" (WikiProject AI Cleanup), open-source detector heuristics, and a writing-integrity contract. Use for ALL writing and editing tasks (blogs, LinkedIn, Quora, PR, case studies, emails, landing pages, executive ghostwriting) even when the user doesn't say "humanize". Also trigger when asked to detect AI patterns, de-AI a draft, audit claims, or check whether text would pass as human. Applies to everything except code and raw data.

0 Updated 1 weeks ago
Aparnabuilds